fix: Use fetch-level: 1 to check out trivy-repo in the release workflow [backport: release/v0.67]
#9638
Conversation
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
owenrumney
approved these changes
Oct 10, 2025
6 tasks
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.
Backport
This will backport the following commits from
maintorelease/v0.67:fetch-level: 1to check out trivy-repo in the release workflow #9636Why we don't use backport action:
The default
GITHUB_TOKENdoes not have permission to modify files under .github/workflows/ (see https://github.com/aquasecurity/trivy/actions/runs/18404387268/job/52440814372?pr=9636#step:5:28).So I created the backport PR manually by reproducing the steps from
misc/backport/backport.sh.Therefore, Backport PR check error for this PR can safely be ignored.