Repository navigation
ci: point the pnpm/setup pin comment at v3.0.0 - #251
Merged
Merged
Conversation
|
Note The title starts with
|
Contributor
There was a problem hiding this comment.
✅ No new issues found.
Reviewed changes — the full diff of the single commit, plus a check of the pinned SHA against the upstream tag.
- Pin comments —
# v3becomes# v3.0.0on all 7pnpm/setupuses (autofix.yml×1,ci.yml×5,pkg-pr-new.yml×1). A grep confirms no otherpnpm/setupreference under.githubis left on the old comment. - SHA unchanged — the annotated
v3.0.0tag inpnpm/setupdereferences tofbda4c85fc2e1e08721cd8763afea8f48d60f024, the SHA already pinned, so workflow behavior is identical. - Changeset — an empty changeset, which fits a CI-only change.
claude-sonnet-5-5 | 𝕏
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.

🔗 Linked issue
No linked issue. Fixes the failing
Security analysis(zizmor) check seen on the Renovate PRs #239 and #240.🧭 Context
zizmor's
ref-version-mismatchaudit fails on thepnpm/setuppin: the comment says# v3, but the movingv3tag now points to a newer commit than the pinned SHA. The pinned SHA is the one taggedv3.0.0.📚 Description
Changes the version comment of the
pnpm/setuppin to# v3.0.0inautofix.yml,ci.ymlandpkg-pr-new.yml. I checked that the annotatedv3.0.0tag resolves tofbda4c85fc2e1e08721cd8763afea8f48d60f024, the SHA that is already pinned. The SHA is unchanged, so behaviour does not change.The other finding in those runs (
documentation.yml,# mainagainst a stale digest) is resolved by the open Renovate PR #239.Key changes
.github/workflows/autofix.yml,ci.yml,pkg-pr-new.yml# v3-># v3.0.0on thepnpm/setuppin (7 places).changeset/ci-pnpm-setup-pin-comment.mdType of Change
Pre-flight Checklist
pnpm changeset(orpnpm changeset add --emptyif no release is needed). See .changeset/README.md.