Workflow to bump major version #6
Open
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
Keeps a 'vMajor' ref (branch) in sync with the latest tag for that major version. This way consumers can pin to the major version and receive minor/patch updates.
|
I should probably add a bit of documentation about how to release before this gets merged. |
|
@jasonkarns still worth getting this across the finish line? |
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.
Type of PR (feature, enhancement, bug fix, etc.)
workflow enhancement
Description
Keeps a 'vMajor' ref (branch) in sync with the latest tag for that major version. This way consumers can pin to the major version and receive minor/patch updates.
modeled after: https://github.com/nodenv/.github/blob/main/.github/workflows/tag-major.yml
example runs: https://github.com/nodenv/.github/actions/workflows/tag-major.yml
Why should this be added
Allow the action to be released by tagging (git tag) with full semver-style version. But at the same time still allow consumers to pin only to a major version.
Checklist