chore(repo): add release workflow action #51
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.
Releasing new versions
Versioning requires triggering the Nx Cloud Workflow Release workflow with comma separated commits to cherry pick and the version to release as.
Note
Only the version number is needed if a new release is needed. The workflow will automatically create the branch and tag from the HEAD of
main
if the new version is a major. Or it will use the latest HEAD on the relative major branch based on the version number. (This allows us to place commits in release branches, and tag them when needed)The workflow will do the following:
releases/v*
branchv*
tag pointing to the HEAD of the branch. If minor/patch releases are needed multiple tags will be created for it.v4
andv4.1
created at the HEAD of the release branch.v4
andv4.2
created at the HEAD of the release branch. Previous tags (v4.1
in this case) will remain unchangedv4
,v4.2
andv4.2.1
created at the HEAD.v4
and get all minor and patches automaticallyv4.1
and get all patches automaticallyImportant
Tags should not be created directly on
main
, and will always be created off release branches. This allows us to iterate onmain
without causing too many disruptions for users.