Repository navigation
chore(js): upgrade Changesets publishing #15718
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
Merged
+220
−414
Merged
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.
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 pinned SHA does not exist in
changesets/action, so this step will fail to resolve.8488615a623b1b9c987934bb89eae8af6a946ac1is not a commit inchangesets/action(or anywhere on GitHub):The actual
v2.1.1release commit isd7669c894a691cf0908002c33cdd57df54a1ef3b— the merge commit of changesets/action#722 ("Version Packages", body:## @changesets/action@2.1.1), merged 2026-08-19. That SHA does resolve, confirming the search index is current and the empty result above is a genuine miss rather than an indexing gap.uses:with an unresolvable SHA fails immediately withUnable to resolve action changesets/action@8488615…. This workflow ison: push: branches: [main], so nothing in PR CI exercises it — the first symptom would be a broken JS package release after merge.phoenix/.github/workflows/typescript-packages-publish.yml
Lines 50 to 52 in 72d5a8e
For what it's worth, the rest of the migration checks out: the renamed inputs (
version-script,publish-script,commit-message,pr-title,create-github-releases), the move of the token fromGITHUB_TOKENenv to thegithub-tokeninput, and the relativecwd: jsare all correct for v2 — and the@changesets/cliv3 bump is in fact required by v2'svalidateChangesetsCliVersioncheck.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.
This is a false positive —
8488615a623b1b9c987934bb89eae8af6a946ac1is exactly whatchangesets/action@v2.1.1resolves to.v2.1.1is an annotated tag, so the ref points at a tag object, not directly at the commit:The empty
gh search commits --hashresult is a search-index miss, not proof of absence — the commits API resolves the SHA fine.The suggested
d7669c894a691cf0908002c33cdd57df54a1ef3bisVersion Packages (#722)from2026-08-19T05:29:59Z, roughly an hour before the commit the tag actually points at. Taking the suggestion would pin a commit thatv2.1.1does not reference, so the# v2.1.1comment would become inaccurate. Leaving the pin as-is.