Repository navigation
fix(ci): restore release tags with Changesets Action v2 - #550
Merged
Merged
Conversation
|
✅ Deploy Preview for stacks-editor ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
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.
Summary
Use Changesets Action v2 with the repository's Changesets CLI v3 so future npm publishes also push their Git tags and create GitHub releases. The 1.1.0 publish succeeded, but Action v1 did not recognize CLI v3's changed output and silently skipped both steps.
Changes
changesets/action@v2.1.2, which reads CLI v3's structured publish output instead of matchingNew tag:in stdout.github-token; configure npm authentication withsetup-node's registry URL andNODE_AUTH_TOKENusing the existing npm secret. No secret or permission changes are required.v1.1.0tag or GitHub release; those need a separate recovery action at commitb1d88c76d6b492985d880a9a51292c0acdea067f.How to test
lts/*) and runnpm ci.npm run test:release-config. All 9 tests passed locally. They guard action compatibility, npm/GitHub authentication wiring, tag pushes, and the release-PR output reference. Separate local mutation checks also rejected the previous workflow and broken action, registry, token, and output configurations.npm run test:unit -- --runInBand,npm run lint, andnpx tsc --noEmit. Locally, all 50 unit suites passed (1,100 tests passed; 10 skipped; 20 todo), lint passed with two existing assertion warnings, and type-check passed. Workflow YAML parsing andgit diff --checkalso passed. Tested on macOS with Node.js 26.5.0 and npm 11.17.0; no browser behavior changes.main, so a live publish was not exercised locally or on this PR. Merging this fix alone will not repair the already-published 1.1.0 release metadata.