chore(release): publish to nuget.org as primary feed#58
Merged
Conversation
Switches the release pipeline from publishing to GitHub Packages (the pre-rename stopgap) to publishing Fallout.* packages to nuget.org. This enables the prefix reservation flow tracked in #33. Changes: - build/Build.cs: IPublish.NuGetSource is now api.nuget.org; drop the GitHub-Packages-owner construction logic and stale comment. - build/Build.cs: DeletePackages glob fixed nuke.* → fallout.* (latent bug — the regex-based string-reference audit in #52 missed it because literal "nuke.*" with lowercase didn't match the \bNuke\. pattern). - .github/workflows/release.yml: NuGetApiKey now sourced from secrets.NUGET_API_KEY instead of GITHUB_TOKEN; drop packages:write permission (no longer pushing to GitHub Packages). - CLAUDE.md: refresh the "publishes to GitHub Packages" / "why not nuget.org?" paragraph — the gating rename has landed. Refs #33. Issue stays open until the prefix reservation is approved by Microsoft (manual form submission after first nuget.org publish). ## Manual steps required before merging 1. nuget.org → API keys → create key scoped to "Push" for glob pattern `Fallout.*` (use the existing org account). 2. Repo Settings → Secrets and variables → Actions → add `NUGET_API_KEY` with that value. Merging without (1) and (2) will cause the next release run to fail loudly at the Publish step. That's the intended fail-mode. ## After merge Next push to main will publish all Fallout.* packages to nuget.org. After that succeeds, submit the prefix reservation form: https://learn.microsoft.com/en-us/nuget/nuget-org/id-prefix-reservation Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
ChrisonSimtian
added a commit
that referenced
this pull request
May 22, 2026
CLAUDE.md no longer claimed the Nuke.* → Fallout.* structural rename was pending — that landed in #54, #60, #65, #66 ages ago. Updates the rebrand-status paragraph, the src/tests layout table, the production project groupings (now including Fallout.Migrate and the vendored Fallout.VisualStudio.SolutionPersistence), the tool-wrapper paths, and fixes the CI-revival roadmap link from #7 (which is the CodeQL ticket) to #8 (the actual CI-revival tracker). README.md said releases publish to GitHub Packages — nuget.org has been the primary feed since #58. Build-status table also had three URLs hardcoded to ChrisonSimtian/nuke (the pre-rename slug). Also notes the new docs-only paths-ignore on the release workflow. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
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.
Summary
Fallout.*packages to nuget.org.DeletePackagesglob inBuild.cswas stillnuke.*(the chore(rebrand): audit and update string references to nuke.build, nuke-build/nuke (#30) #52 string-reference audit's\bNuke\.regex didn't catch lowercase literals).Refs #33 — issue stays open until Microsoft approves the prefix reservation (manual form after first publish).
This PR will fail at the
Publishstep on the next push tomainif these aren't done first:Fallout.*(against your existing org account).NUGET_API_KEYwith that value.That's it for pre-merge. The CI will then attempt the first nuget.org publish on the next push to
main.After merge
Next push to
mainpublishes allFallout.*packages to nuget.org. Once at least one is up, submit the prefix reservation:Once approved, you can close #33.
What's NOT in this PR
Nuke.*packages already published to GitHub Packages on the fork. Those stay as historical artifacts of the pre-rename period. No churn until a consumer asks.mainpush after this lands).Test plan
dotnet build build/_build.csproj -c Debugpasses locally (verified — 0 errors, 14 pre-existing warnings)NUGET_API_KEYsecret added to repo settings before merging.github/workflows/release.ymlrun and confirm packages appear under https://www.nuget.org/profiles/🤖 Generated with Claude Code