Update example workflow to reference v1 as release version
#38
Conversation
This file contains hidden or 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
Instead of the specific release. We will be re-tagging v1 from the latest 1.X.Y release going forward. Signed-off-by: Matthew Weier O'Phinney <[email protected]>
michalbundyra
approved these changes
Aug 10, 2020
The actions-tagger action runs on release, and if a semantic version is
detected, it will:
- Pull all tag versions for the major release indicated.
- Compare the version released against the latest in the major release series.
- Repoint the v{MAJOR} tag at the new version if it is indeed the newest
in that series.
Essentially, if 1.1.2 is released, and it is the most recent release in
the v1 series, this will point the v1 tag at 1.1.2.
Signed-off-by: Matthew Weier O'Phinney <[email protected]>
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.
When a new release is published, if it is the most recent version in the current major version series, we should point a tag
v{MAJOR}at the new release.This patch:
v1release.update-major-release.yml, that makes use of the action "actions-tagger", which compares the current release against other releases in the current major version, and repoints thev{MAJOR}tag if so.Fixes #34