Introduce new release flow - Part 1 #2143
Merged
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 is the first PR in an attempt to introduce new release workflow for our deploys after the recent org level github permission changes.
This PR adds an event_dispatch workflow called
version packages
that can be triggered via GH CLI or API. The version packages workflow runs lerna version, commits the package version changes to branch and creates a release PR. Here is an example PR created.Merging the version PR to main kicks off the
publish
workflow that useslerna publish from-package
instead oflerna publish from-git
. Thefrom-package
command reads packages versions from package.json of all packages and publishes them if the version has changed.from-git
relies on tags to publish new version. Since we'll lose the tags in from-package workflow, new steps have been added to therelease
workflow to autogenerate package tags and push to main.Testing
Tested the relase workflow on this branch.
Example PR created - #2139
For further testing and improvements to our deploy workflow, I would like to merge this to main.