Repository navigation
ci(security): enforce the Python release scan - #2
Merged
Merged
Conversation
- Return a failing status for HIGH/CRITICAL Trivy findings so the existing release dependency blocks publication. Refresh affected locked dependencies, including compatible Python 3.10 variants, and add Actions/uv dependency update PRs.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Apply the HIGH/CRITICAL severity filter explicitly in SARIF mode and return a failing status for matching Trivy findings so the existing release dependency blocks publication. Refresh affected locked dependencies, including compatible Python 3.10 variants, and add Actions/uv dependency update PRs. Add a manual scan trigger; the repository Trivy workflow was disabled due to inactivity and has been re-enabled.
Verification
Check out
ci/maintenance-checksand run commands from the repository root. Use the repository runtime version files and installed Make/actionlint. Go checks used Go 1.26.10; link checks used Lychee 0.24.2; Python checks used uv with Python 3.10 and 3.12. Install Helm, OpenTofu, Docker or Trivy only where the commands below require them.actionlint .github/workflows/*.ymlgit diff --check main...HEADuv sync --all-extras --python 3.12 && make lint typecheck testuv sync --all-extras --python 3.10 && make lint typecheck testtrivy fs --severity CRITICAL,HIGH --exit-code 1 --format sarif --output /tmp/signet-python.sarif .Each validation command should return zero. Lint/test failures must stop the job. External link availability can fail independently of source changes; inspect the reported URL rather than ignoring all failures. GitHub job execution is verified after opening this PR. Production publication/deployment is Not run: this PR does not publish releases, push images or apply infrastructure. Dependency update PR scheduling is Not run locally; GitHub enables the configuration after merge.
Security gate inspection Passed: HIGH/CRITICAL findings return exit 1; publication remains downstream of scan success and SARIF uploads remain available where configured. Docker scans retain the existing ignore-unfixed policy. The Python baseline scan actually failed before dependency remediation and passed afterward.
Flow
AI authorship and review
.github/dependabot.yml,.github/workflows/trivy.yml,uv.lockScope, risk and rollback
Implements the requested repository maintenance review. No issue identifier was supplied. Review failure propagation, dependency coverage and the changed workflow steps. No secrets or unrelated local changes are included. Stricter checks can intentionally block a future change; investigate findings before release. Revert this commit to roll back.