Fix the unresolved nested Trivy action dependency - #21
Merged
Conversation
amasen02
marked this pull request as ready for review
September 12, 2026 17:57
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.
The previous Trivy v0.28.0 action resolves, but its nested setup-trivy@v0.2.1 dependency does not. Pin the supported v0.36.0 action to its verified official commit; its reachable action dependencies also resolve to immutable commits.
Validation: recursive official action-reference verification, actionlint and diff checks passed. Scan severity, exit-code, permissions and image-push conditions are unchanged. Container execution will run on the normal master workflow after merge.