Restore previous tagging behavior for container workflow #77
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
… major, major.minor and major.minor.patch Signed-off-by: Aleksei Khudiakov <[email protected]>
Ocramius
approved these changes
Jan 26, 2022
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.
Description
I missed in #76 that previous workflow would tag
major,major.minorandmajor.minor.patchfor the release. Restoring that behavior.I should point out that tagging like this is somewhat naive and latest build will take over the more generic tag. Eg
1.18.0followed by1.17.1would end up in@1pointing to1.17.1instead of latest1.18.0It is not really a concern with the way we tag releases in this package.