Repository navigation
bump trivy-py-ecc to 0.76.0.1 - #110
Merged
Merged
Conversation
The constraint was ^0.73.0.1, which Poetry caps at <0.74.0, so neither 0.74.0.1 nor the 0.76.0.1 release published today was reachable by a generated project. Verified against a rendered plugin case built from the dirty worktree (task check:generate:case renders --vcs-ref HEAD and would have ignored the edit): poetry resolves trivy-py-ecc 0.76.0.1, the binary reports 0.76.0, the flag set in src/Taskfile.yaml is unchanged in 0.76 and check:trivy exits 0 with no findings against the generated lock, so the newer vulnerability database does not turn existing projects red. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_013pwym1cFV5jEhi7LdzKmEY
Coverage Report
|
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
1 participant
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.
trivy-py-eccwas constrained to^0.73.0.1, which Poetry caps at<0.74.0, so a generated project could reach neither 0.74.0.1 nor the 0.76.0.1 release published today. The constraint is now^0.76.0.1.Verified against a
plugincase rendered from the dirty worktree —task check:generate:caserenders--vcs-ref HEADand would have ignored the edit, so the template was copied without.gitand rendered from there:poetry updateresolvestrivy-py-ecc (0.76.0.1), the binary reportsVersion: 0.76.0src/Taskfile.yaml(--include-dev-deps --scanners vuln --skip-files … --exit-code 1) is unchanged in 0.76task check:trivyexits 0 with 0 vulnerabilities against the generatedpoetry.lock, so the newer vulnerability DB does not turn existing projects red🤖 Generated with Claude Code
https://claude.ai/code/session_013pwym1cFV5jEhi7LdzKmEY