Point the nuget-org environment at the real nuget.org profile - #569
Merged
ChrisonSimtian merged 1 commit intoJul 26, 2026
Conversation
The environment URL read https://www.nuget.org/profiles/Fallout, which is not the publishing account — the packages live under the Fallout.build profile. It is the link a maintainer clicks from the deployment entry after approving a nuget.org push, so it sent them somewhere unrelated. Confirmed on the v10.4.0-rc.4 publish, which logged "Evaluated environment url: https://www.nuget.org/profiles/Fallout". Display-only: the URL never affected which packages were pushed or where. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
ChrisonSimtian
marked this pull request as ready for review
July 26, 2026 13:41
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.
The
nuget-orgenvironment URL pointed athttps://www.nuget.org/profiles/Fallout, which isn't the publishing account — the packages live underFallout.build(22 packages).That URL is the link a maintainer clicks from the deployment entry after approving a nuget.org push, so it sent them somewhere unrelated. Confirmed on the
v10.4.0-rc.4publish, which logged:Display-only — the URL never affected which packages were pushed or where. The
v10.4.0-rc.4publish itself was correct: all 19Fallout.*packages are live on nuget.org.Same fix is included for
mainin #567; this one lands it on the branch that actually publishes, so the link is right on the next approval rather than waiting for a promotion.