ci: skip dotnet publish for rc tags#7433
Closed
Xuanwo wants to merge 1 commit into
Closed
Conversation
dosubot
Bot
added
size:XS
tisonkun
requested changes
Apr 27, 2026
Member
|
Closed as #7422 merged. |
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
2 participants
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.
Which issue does this PR close?
N/A.
Rationale for this change
The v0.56.0-rc.4 tag build showed that the .NET release workflow still tries to publish to NuGet for RC tags. RC tag builds should validate and package artifacts, but publishing to NuGet should only happen for final release tags or explicit manual publish runs.
What changes are included in this PR?
This PR gates the .NET publish job so prerelease tags such as
v0.56.0-rc.4skip NuGet publishing while finalv*tags andworkflow_dispatchpublish runs keep the existing publish path.Are there any user-facing changes?
No.
AI Usage Statement
Assisted.