chore(release): adopt Changesets for automated publishing - #28
Merged
Merged
Conversation
Replace the manual GitHub-Release-triggers-publish flow with Changesets: merging a version PR to main now drives the release instead of a human cutting a Release and picking a dist-tag by hand. @devicekit/devices and @devicekit/frame stay fixed together since they've always shipped as one version. Retires npm-dist-tag.mjs and its test (dist-tag resolution is now changesets' job) and the merge-base guard in publish.yml (push-to-main triggers can't point at an arbitrary branch the way a Release could), while keeping the main-branch restriction under a renamed release-guard.test.mjs.
The prior commit renamed publish-guard.test.mjs to release-guard.test.mjs but the git mv happened before the content rewrite got staged, so it was committed with its old publish.yml-parsing content under the new filename.
Gate the release job behind the npm-release GitHub environment and drop the NPM_TOKEN/provenance env vars now that both packages have npm trusted publisher entries configured for release.yml. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
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.
Summary
publish.ymlwithrelease.yml, driven by Changesets: contributors add changeset files, a bot PR aggregates them, merging it runschangeset version+changeset publishautomatically.@devicekit/devicesand@devicekit/frameversion-locked via afixedgroup, matching current practice.id-token: write+environment: npm-release), dropping the storedNPM_TOKEN.CONTRIBUTING.mdandCHANGELOG.mdto describe the new flow.Test plan
node --test scripts/release-guard.test.mjspassespnpm testpassespackage.json, sochangeset publishwill find nothing to do)alphatag) publish, to confirm OIDC trusted publishing actually works — planned as a follow-up after this merges🤖 Generated with Claude Code