-
Notifications
You must be signed in to change notification settings - Fork 262
chore(deps): bump the github-actions group across 1 directory with 4 updates #1643
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-actions-8cb3c991c1
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
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.
🟡 On line 49 of
.github/workflows/ci.yml, theactions/cacheSHA was bumped to27d5ce7f107fe9357f9df03efb73ab90386fccae(which is v5.0.5), but the trailing version comment still reads# v5.0.4. Dependabot normally rewrites these comments — this one was missed, so the SHA→version mapping that humans read to audit pinned actions is misleading. Comment-only nit, no runtime impact; please update the comment to# v5.0.5to match the rest of the diff.Extended reasoning...
What the bug is. In
.github/workflows/ci.ymlline 49, theactions/cachestep is updated from SHA668228422ae6a00e4ad889ee87cd7109ec5666a7to27d5ce7f107fe9357f9df03efb73ab90386fccae, but the trailing comment is left unchanged at# v5.0.4. The PR description's actions/cache section explicitly bumps that action from v5.0.4 → v5.0.5, and the actions/cache release notes show27d5ce7f107fe9357f9df03efb73ab90386fccaeas the v5.0.5 release commit ("Merge pull request #1747 from actions/yacaovsnc/update-dependency — Update ts-http-runtime dependency"). So the SHA on line 49 is v5.0.5 but the inline annotation still says v5.0.4.\n\nWhy this is a real (if cosmetic) issue. This repo pins every GitHub Action to an immutable SHA with a trailing# vX.Y.Zcomment so reviewers can audit pinned versions at a glance — that is the only reason the comments exist. When Dependabot bumps actions, it rewrites those comments together with the SHA. In this same PR every other action comment was updated correctly:astral-sh/setup-uvv8.0.0 → v8.1.0,github/codeql-actionv4.35.1 → v4.35.2, anddependabot/fetch-metadatav3.0.0 → v3.1.0 all have matching SHA + comment changes. Line 49 is the lone outlier where the SHA moved but the comment did not, which is a clear Dependabot oversight rather than intentional pinning.\n\nImpact. No runtime impact — GitHub Actions resolves the SHA, and27d5ce7f...will correctly run v5.0.5 ofactions/cacheregardless of what the comment says. The cost is purely auditability: a future reviewer readingactions/cache@27d5ce7f107fe9357f9df03efb73ab90386fccae # v5.0.4will believe the pin is at v5.0.4 and may waste time tracing the discrepancy, or fail to notice that v5.0.5 is actually deployed when triaging behavior changes (e.g. the v5.0.5 ts-http-runtime bump).\n\nFix. Change# v5.0.4to# v5.0.5on line 49 of.github/workflows/ci.yml. No other change needed.\n\nStep-by-step proof.\n1. Open the diff for.github/workflows/ci.ymlline 49: it reads- uses: actions/cache@27d5ce7f107fe9357f9df03efb73ab90386fccae # v5.0.4 # zizmor: ignore[cache-poisoning]. The@SHAwas changed (was668228422ae6...); the# v5.0.4comment was not.\n2. Confirm the new SHA's release. The PR description quotes the actions/cache v5.0.5 release notes, which list a single commit:27d5ce7— "Merge pull request #1747 from actions/yacaovsnc/update-dependency". That is the commit being pinned.\n3. Confirm the PR's intent. The PR description's header for this action reads "Updatesactions/cachefrom 5.0.4 to 5.0.5", so the target version is unambiguously v5.0.5.\n4. Cross-check against sibling bumps in the same diff: every other action comment matches its SHA's release tag. Only line 49 is mismatched.\n5. Therefore the comment# v5.0.4on line 49 is stale and should read# v5.0.5.\n\nAll four independent verifiers confirmed this with nit severity. Filing as nit (cosmetic, comment-only).