chore: adopt changesets for versioning and releases#20
Merged
Conversation
Replace the manual tag-based publish with the changesets flow: PRs add a changeset, a push to main opens a 'Version packages' PR (bumping the version + writing CHANGELOG), and merging that PR publishes to npm. Add config, scripts, and the release workflow, plus a changeset for the seamless verify conformance harness (queues a 0.3.0 release).
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.
Adopts the Changesets release flow used across the other packages, and queues the first
release that includes the
seamless verifyconformance harness.What changes
.changeset/config.json(public access,mainbase),@changesets/clidev dependency, and
changeset/version-packages/release:stablescripts.release.yml): replaces the manualv*.*.*tag publish with the standardchangesets/actionflow.seamless verify(minor) so the next release publishes it.How releases work now
npm run changesetand commit a changeset describing the change.mainopens (or updates) a "chore: version packages" PR that bumps the versionand updates
CHANGELOG.md.To cut the release
Merging this PR triggers the workflow, which opens the version PR bumping 0.2.0 -> 0.3.0.
Merge that version PR to publish
seamless-cli@0.3.0. Thennpx seamless@latest(ornpx create-seamless) runs the new version end to end.Note: requires the existing
NPM_TOKENrepo secret (already used by the old publish workflow).