Introduce new release flow #2140
Closed
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
varadarajan-tw
force-pushed
the
new-prod-release-workflow
branch
4 times, most recently
from
cacc349
to
a286e61
Compare
varadarajan-tw
force-pushed
the
new-prod-release-workflow
branch
from
a286e61
to
7e9a31a
Compare
varadarajan-tw
force-pushed
the
new-prod-release-workflow
branch
from
3b38d0a
to
eb3cbe9
Compare
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.
With recent changes to github organization rules, we cannot use the old workflow which allowed segment engineers push directly to main branch.
This PR adds an event_dispatch workflow called
version packagesthat 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 PR to main kicks off the
publishworkflow that useslerna publish from-packageinstead oflerna publish from-git. Thefrom-packagecommand reads packages versions from package.json of all packages and publishes them if the version has changed.from-gitrelies on tags to publish new version. Since we'll lose the tags in from-package workflow, new steps have been added to thereleaseworkflow to autogenerate package tags and push to main.Testing
Tested the reelase 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.