-
Notifications
You must be signed in to change notification settings - Fork 303
chore(deps): bump the github-actions group across 1 directory with 3 updates #1638
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
Closed
dependabot
wants to merge
1
commit into
main
from
dependabot/github_actions/github-actions-6134e99a4c
Closed
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
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
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.
🟡 The actions/cache SHA on line 49 of
.github/workflows/ci.ymlwas bumped to27d5ce7f107fe9357f9df03efb73ab90386fccae(which is v5.0.5 per the PR description and upstream compare link), but the trailing pin comment still reads# v5.0.4. This is purely cosmetic (the SHA is authoritative, so CI still runs v5.0.5), but it leaves the pin comment out-of-sync with the actual commit and contradicts the convention established in commit d5ce2d2 ("chore(ci): pin action version comments to immutable patch tags"). Fix by changing the comment to# v5.0.5.Extended reasoning...
What's wrong
On line 49 of
.github/workflows/ci.yml, this diff updates the pinned SHA foractions/cachebut leaves the human-readable version comment stale:The new SHA
27d5ce7f107fe9357f9df03efb73ab90386fccaeis the head of the v5.0.5 tag, not v5.0.4.Proof / step-by-step
actions/cachefrom 5.0.4 to 5.0.5".actions/cache/compare/668228422ae6a00e4ad889ee87cd7109ec5666a7...27d5ce7f107fe9357f9df03efb73ab90386fccae— i.e., the diff between v5.0.4 (old SHA) and the new SHA is the v5.0.4→v5.0.5 release.27d5ce7"Merge pull request #1747 from actions/yacaovsnc/update-dependency", which matches the single item in the v5.0.5 release notes ("Update ts-http-runtime dependency ... Update ts-http-runtime dependency actions/cache#1747").# v5.0.4comment still refers to the old version.Why it matters
The repo recently landed commit d5ce2d2 ("chore(ci): pin action version comments to immutable patch tags") specifically to make these pin comments accurate — the explicit convention is that the
# vX.Y.Zannotation must match the SHA so that anyone auditing supply-chain pins can verify without resolving the SHA manually. Leaving the comment as# v5.0.4while the SHA points at v5.0.5 erodes that guarantee.Why existing process didn't catch it
This is a known rough edge of dependabot's group-update diff generation: when the previous pin's comment matches the previous tag, dependabot rewrites the SHA but does not always refresh the neighboring comment. The other five
uses:lines in this PR (fourastral-sh/setup-uvbumps and twogithub/codeql-actionbumps) did get their comments updated correctly, so this appears to be an isolated dependabot oversight on this single line.Impact
No functional impact — GitHub Actions resolves the SHA, so the workflow still runs actions/cache v5.0.5 as intended. This is cosmetic / documentation only, hence nit severity. Still worth fixing before merge to keep supply-chain pin comments trustworthy.
Fix
Change line 49 from:
to: