Repository navigation
ci: release with changesets - #11
Merged
Merged
Conversation
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.
Replaces the GitHub-release-triggered
publish.ymlwith the changesets flow the other seamless-* repos use (modelled onseamless-auth-server).How it works
npx changeset).release.ymlopens or updates achore: version packagesPR that bumps versions and writes per-package changelogs.npm run release:verify(lint, format, typecheck, tests), thenchangeset publishpublishes new versions to npm with provenance, tags each package, and creates the GitHub releases.The three packages are a
fixedgroup, so they always share one version, andupdateInternalDependencieskeeps the transports on^<same version>of@seamless-auth/messaging. That is the invariant the old workflow checked by hand. Thepublish:*scripts are removed so there is one way to publish. The README's Publishing section is rewritten.On merge
0.2.0 is already on npm for all three packages, and
changeset publishskips published versions, so merging this publishes nothing.Verified
npm run release:verifypasses. A simulated patch changeset on core bumped all three packages to 0.2.1, set the transports' core range to^0.2.1, and wrote the three changelogs (discarded afterwards).Needs
The
NPM_TOKENsecret, as before. It is not a repository secret, so it must come from the org. I could not confirm that from here.