Repository navigation
fix(strategy): keep release tags by default - #49
Merged
Merged
Conversation
Without tag_pattern, the tag strategies take only v1.2.3 and 1.2.3.
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
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
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.
Without
tag_pattern, and forgithub-tagalso withouttag_version_regex,github-tag,gitlab-tagandgitea-tagkeep only the tags of the formv1.2.3or1.2.3. Before,sort -Vput a tag namedlatestorv2.1.0-rc1above every release, and the package stopped updating. When no tag has that form, the check fails with a message that names the fields to set.release_tagsinscripts/lib.shholds the filter.docs/WORKFLOW.md,docs/SUPPORTED-PACKAGES.mdandpackages/example.yml.sampledescribe the default. The examples userelease-*instead ofv*, which lets pre-release tags through.