Keep GitHub releases independent of registry publishing - #6
Merged
Conversation
hbashton
added a commit
that referenced
this pull request
Jul 31, 2026
Keep GitHub releases independent of registry publishing
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
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.
What changed
NUGET_USERis unavailable.Why
The
v0.0.6release workflow completed linting and all builds, but an emptyNUGET_USERcausedNuGet/loginto fail beforesoftprops/action-gh-releaseran. That prevented the GitHub release and binaries from being published even though all release artifacts were ready.Impact
GitHub releases and downloadable binaries are now the mandatory release path. Optional package registry outages or missing credentials cannot block them.
Validation
actionlint .github/workflows/release.ymlgit diff --check