-
-
Notifications
You must be signed in to change notification settings - Fork 6
chore(deps): bump github/codeql-action from 4.32.6 to 4.35.1 #314
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
dependabot
wants to merge
1
commit into
main
Choose a base branch
from
dependabot/github_actions/github/codeql-action-4.35.1
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🟣 Pre-existing issue: All three
actions/checkoutsteps (lines 28, 51, 69) are pinned to commitde0fac2e4500dabe0009e67214ff5f5447ce83ddwith the comment# v6, butactions/checkouthas never released a v6 — the latest major version is v4. The incorrect comment undermines the auditability purpose of commit-pinned actions; to fix, update the comment to reflect the actual release tag (e.g.,# v4.1.x) that corresponds to the pinned commit.Extended reasoning...
What the bug is and how it manifests
All three
actions/checkoutsteps in.github/workflows/security.yml(lines 28, 51, and 69) reference the action asactions/checkout@de0fac2e4500dabe0009e67214ff5f5447ce83dd # v6. The comment# v6is factually incorrect —actions/checkouthas only released up to major version v4 (the latest as of early 2026 is in the v4.x line). There is no v6 tag or release in theactions/checkoutrepository.The specific code path that triggers it
Every job in this workflow (
codeql,dependency-review,scorecard) checks out code using this step. The SHA pin itself may be valid for the v4.x line, but the comment annotation misleads anyone trying to audit the pin by claiming it corresponds to a non-existent v6 release.Why existing code doesn't prevent it
GitHub Actions does not validate that commit-pinning comments are accurate — they are purely informational annotations. There is no lint or CI check enforcing that the comment matches the actual tag associated with the pinned SHA.
Impact
The primary purpose of commit-SHA pinning in security workflows is auditability: reviewers and automated tools should be able to cross-reference the hash against a known release tag. With an incorrect version comment (
# v6), an auditor searching foractions/checkout v6will find no such release, casting doubt on the legitimacy of the pin and undermining the supply-chain security posture this workflow is designed to enforce.How to fix it
Determine which v4.x release corresponds to the pinned commit
de0fac2e4500dabe0009e67214ff5f5447ce83ddand update the comment accordingly (e.g.,# v4.1.x). Alternatively, update all three checkout steps to the latest v4 release with its correct commit hash and comment.Step-by-step proof
uses: actions/checkout@de0fac2e4500dabe0009e67214ff5f5447ce83dd # v6actions/checkoutreleases: tags go up tov4.x.x— there is nov5orv6release.actions/checkout v6, find nothing, and be unable to confirm the hash is a legitimate official release.dependency-reviewandscorecardjobs respectively.github/codeql-actionversion pins — theactions/checkoutlines are unchanged context, confirming this is entirely pre-existing.