chore(ci): pin the shared workflows to @v1 - #842
Closed
unional wants to merge 1 commit into
Closed
Conversation
repobuddy/.github is now tagged. Pinning @main meant every change there reached this repo the instant it merged — which is how an auto-merged changesets/action v1 -> v2 bump (repobuddy/.github#42) broke this repo's release path without anyone touching it. Two lines exist there, because changesets/action and @changesets/cli are a matched pair the action validates at runtime: v1 -> changesets/action@v1 -> @changesets/cli v2 v2 -> changesets/action@v2 -> @changesets/cli v3 This repo is on @changesets/cli ^2.29.8, so it belongs on @v1. Move to @v2 only together with a CLI v3 upgrade here. Pins the composite action refs too, so the pin actually isolates this repo instead of leaking back to @main through setup-playwright. Refs: repobuddy/.github#43 Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
|
Contributor
Author
|
Superseded by #844, which upgrades |
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
1 participant
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.
This repo's release path is broken right now, and this fixes it.
repobuddy/.githubpinned at@mainmeant an auto-merged Renovate bump there reached this repo instantly. That happened on 2026-08-12: repobuddy/.github#42 movedpnpm-release-changeset.ymltochangesets/action@v2, which validates the consumer's@changesets/climajor and aborts on v2:Nothing failed visibly here only because this repo has not released since. The next release would have.
repobuddy/.githubis now tagged with two parallel lines:@v1changesets/action@v1@v2changesets/action@v2This repo is on
@changesets/cli ^2.29.8→@v1. Move to@v2only alongside a CLI v3 upgrade here; they are a matched pair.Composite action refs are pinned too — a tagged workflow ref that still pulls a floating
setup-playwright@mainis only half a pin.There is also a new secretless
pnpm-release-changeset-oidc.ymlon both lines (built-inGITHUB_TOKEN+ npm trusted publishing instead ofCI_GITHUB_TOKEN+NPM_TOKEN). Not adopted here — that needs a trusted publisher registered per package first.