fix(ci): upgrade setuptools for security audit - #4
Conversation
|
Caution The consumer version of Gemini Code Assist on GitHub has been sunset. All code review activity has officially ceased. |
There was a problem hiding this comment.
Pull request overview
This PR updates the project’s packaging and CI security-scanning environment to ensure a sufficiently new setuptools is present for security auditing, and makes the Trivy SARIF upload step conditional on the SARIF file actually being produced.
Changes:
- Raised the
build-systemminimumsetuptoolsrequirement to>=83.0.0. - Updated the security workflow to install
setuptools>=83.0.0alongside thepipupgrade. - Prevented the Trivy SARIF upload step from running when
trivy-results.sarifis missing.
Reviewed changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.
| File | Description |
|---|---|
pyproject.toml |
Raises the build-system setuptools floor to match the security/audit requirement. |
.github/workflows/security.yml |
Ensures CI installs a secure setuptools before audits and skips SARIF upload if the file isn’t generated. |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
Welcome to Codecov 🎉Once you merge this PR into your default branch, you're all set! Codecov will compare coverage reports and display results in all future pull requests. ℹ️ You can also turn on project coverage checks and project coverage reporting on Pull Request comment Thanks for integrating Codecov - We've got you covered ☂️ |
Updates the GitHub Actions security environment to install setuptools 83.0.0 or newer before pip-audit, and raises the build-system floor. Also avoids uploading a missing Trivy SARIF file when an earlier step fails.