Repository navigation
Conversation
rgarcia
force-pushed
the
hypeship/actions-lockfile
branch
from
November 13, 2026 21:28
5a10de9 to
a660d97
Compare
rgarcia
force-pushed
the
hypeship/actions-lockfile
branch
from
November 13, 2026 21:30
a660d97 to
d49ecb8
Compare
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes using default effort and found 1 potential issue.
❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.
Reviewed by Cursor Bugbot for commit d49ecb8. Configure here.
|
|
||
| - name: Set up pnpm | ||
| uses: pnpm/action-setup@f40ffcd9367d9f12939873eb1018b921a783ffaa # v4 | ||
| uses: pnpm/action-setup@b906affcce14559ad1aafd4ab0e942779e9f58b1 # v4.3.0 |
There was a problem hiding this comment.
Rewritten action pin will not persist
Medium Severity
The lockfile onboards release-please.yml after rewriting pnpm/action-setup from the annotated v4 tag object to commit b906aff. The generator still emits that tag-object SHA, so the next regeneration restores a uses ref the lockfile does not cover and verification fails.
Additional Locations (1)
Reviewed by Cursor Bugbot for commit d49ecb8. Configure here.
Contributor
Author
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
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.


Adds GitHub's workflow dependency lockfile.
.github/workflows/actions.lockrecords the commit behind every action the workflows use (including actions those actions use), so the code that runs can't change underneath them..github/workflows/actions.lock, generated with gh actions-lock--no-narrow. The lockfile keys are the generator's existing SHA pins, each recorded with its release tag (e.g.actions/checkout@de0fac2…→v6.0.2), so regenerated workflows keep matching it.gh actions-lock --verifypasses (all 6 workflows valid).release-please.ymlpinnedpnpm/action-setup@f40ffcd…, which is the SHA of the annotatedv4tag object rather than a commit. A lockfile entry keyed by a SHA must record that same commit, so that ref can't be locked. It now pinsb906aff…(v4.3.0), the commit the tag peels to, so the code that runs is unchanged. The generator template needs the same change so later promotions match.uses:line is unchanged.pypa/gh-action-pypi-publishusesactions/setup-pythoninternally; that is locked transitively. It also runs a Docker action it writes into the workspace at run time, which the lockfile can't follow (warning only).gh actions-lock --no-narrow; a default run rewrites the SHA pins to tags and diverges from the generator output.No reusable workflow calls in this repo.