Repository navigation
Publish releases for multi-digit version numbers (release-4.3) - #1091
Merged
Merged
Conversation
…so tags such as 5.2.10 or 10.0.0 published nothing. The stable tag check was unanchored and unescaped, so a pre-release tag ending in three numbers, such as 1.0.0-alpha.1.2.3, would have been published to NuGet.org as stable. (#1088) Publish releases for multi-digit version numbers (cherry picked from commit 48b62df)
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.
Backports #1088 to
release-4.3, cherry-picked with-x. Tag builds use the workflow at the tagged commit, so tags onrelease-4.3need the fixed tag filters and stable tag check.