ci: replace lerna into changesets for versioning and publishing
#424
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
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
tonyfromundefined
approved these changes
Nov 28, 2023
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.
This PR replaces
lernaintochangesetsas versioning and publishing tools.New feature:
yarn changesetcan create the changesets of the packages that need to be bumped.Those changesets can be added as a commit along with the actual code changes.
When the commit(s) containing changesets is(are) pushed into
mainbranch (by merge or raw push), release workflow will be run and changesets action may version or create PR for publishing the corresponding packages.Replaced scripts:
lerna:publish->releasefor local publishinglerna:publish:canary->release:canaryfor pre-release