Nuget Tag Name Fix #913
Merged
Nuget Tag Name Fix #913
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
COM8
added a commit
that referenced
this pull request
May 18, 2023
* Only triggering NuGet CI por push * Properly getting the latest tag * Disabled publish for testing * Windows like tag extraction * Testing input fields for workflow_dispatch * Fixed workflow_dispatch input type * Enabled publishing again * Option for disabling publishing NuGet
COM8
added a commit
that referenced
this pull request
May 18, 2023
* Only triggering NuGet CI por push * Properly getting the latest tag * Disabled publish for testing * Windows like tag extraction * Testing input fields for workflow_dispatch * Fixed workflow_dispatch input type * Enabled publishing again * Option for disabling publishing NuGet
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Let's say we are releasing a hotfix version for 1.9.x but there exists already a version 1.10.x. Then the NuGet CI will create a new NuGet package for 1.10.x instead of 1.9.x.
This PR resolves that.