-
Notifications
You must be signed in to change notification settings - Fork 202
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Introduce changesets for versioning and publishing #565
Merged
Conversation
This file contains 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
Normally the output from Socket is less intense btw 😅 |
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.
Versioning and releasing is tedious manual work currently and can only be done by someone with npm access.
This PR
changesets
, which manages changelogs, versioning, and (optionally) publishing.changeset-bot
which reminds you to add a changeset.yarn changeset
. You choose the semverness and description.release
which can be triggered manually in the "Actions" tab or locally withyarn release
(requiresgh
CLI to be installed by yourself globally). This opens a PR with the new versions and changelogs. When merged, it publishes the packages to npm. The access token lives in GH so you don't need direct access and publishing is always transparent (anyone can see the PR).Warning
I haven't tested the release flow yet as I can't test this action locally. We just have to try and see.