Repository navigation
CI's tag trigger matches the unprefixed release tags - #37
Merged
Merged
Conversation
…parated numbers, the unprefixed form every release since 0.6.0 has carried, where v* matched only the five tags before it
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.
Releases since 0.6.0 are unprefixed (
0.13.0), made withgh release createon the merge commit, but the workflow's push trigger listened forv*, so no release tag has run CI sincev0.5.0. The pattern is now[0-9]+.[0-9]+.[0-9]+(GitHub's filter syntax:+repeats the class), which matches every release tag made since and the ones to come;v*is dropped, its five tags being history.No consumer-visible change, so no CHANGELOG entry. The next release's tag push will run the full workflow on the tagged commit, as a tag run was meant to.