Repository navigation
ci: upgrade changesets/action to v2 for changesets cli v3 - #177
Merged
Merged
Conversation
Contributor
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Contributor
|
Thank you for following the naming conventions! 🙏 |
This branch was successfully deployed
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.
🔗 Linked issue
None.
📚 Description
Since 11 September, the release workflow has published to npm but has not created git tags or GitHub releases. The last ones are
@github-tools/sdk@1.16.0and@github-tools/eve-extension@0.7.0.#142 moved
@changesets/clifrom 2.31.1 to 3.0.2.release.ymlstill usedchangesets/actionv1.9.0, which detects published packages by parsing the CLI'sNew tag:lines. CLI v3 no longer prints them, sopublishedstayedfalse. As a result, the action skipped creating GitHub releases, and thePush tagsandRewrite release notessteps never ran. The changesets maintainers document action v1 as the match for CLI v2, and action v2 for CLI v3 (changesets/action#694).Changes to
.github/workflows/release.yml:changesets/actionv1.9.0 → v2.1.2, pinned by SHA.pr-title,commit-message,version-script,publish-script,create-github-releases.commitMode: github-apiand theGITHUB_TOKENenv removed. v2 pushes through the GitHub API by default and uses the workflow token.outputs.published-packages.The git identity and
Push tagssteps are unchanged.Missing tags and releases for
sdk1.16.1–1.18.0 andeve-extension0.7.1–0.8.1 need a one-off backfill, since those versions are already on npm and the workflow will not publish them again.📝 Checklist