C#: pass --skip-duplicate to dotnet nuget push#7544
Merged
jkschneider merged 1 commit intomainfrom May 2, 2026
Merged
Conversation
NuGet versions are immutable, so the daily scheduled publish failed whenever no new commit had landed since the previous run (the snapshot version is derived from the latest commit timestamp). `--skip-duplicate` turns the duplicate response into a logged warning instead of an error.
1 task
timtebeek
added a commit
that referenced
this pull request
May 3, 2026
npm has no `--skip-duplicate`, so the daily scheduled publish failed with a 403 whenever no new commit had landed since the previous run (the snapshot version is derived from the latest commit timestamp). Mirrors the intent of #7544 for NuGet.
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.
The scheduled daily CI run fails on the NuGet publish step whenever no new commit has landed since the previous run. The C# snapshot version is derived from the latest commit timestamp, so the
.nupkgfilename is identical to yesterday's; NuGet versions are immutable, sodotnet nuget pushexits non-zero and turns the whole publish step red (e.g. https://github.com/openrewrite/rewrite/actions/runs/25222223491).Adding
--skip-duplicatemakes NuGet treat an already-uploaded version as a logged warning instead of an error, matching how Maven-SNAPSHOTre-uploads behave.Test plan
ci.ymlviaworkflow_dispatchtwice without an intervening commit; second run succeeds with a "package already exists, skipped" log line.publish.ymlstill pushes a fresh release version successfully.