Repository navigation
[P4] Reserve Fallout.* package IDs on nuget.org #33
Description
Why now
Squatters watch the github trends + Reserved Names list. If we don't reserve our package IDs early, someone else can claim them. Even if we publish to GitHub Packages today, we want to lock in nuget.org names for future use.
Action
For each upcoming Fallout package, do one of:
- Publish a placeholder `0.0.0-reserved` package with empty content — claims the ID immediately.
- Submit a Reserved Names request to NuGet via https://www.nuget.org/policies/Reserved-Names — gets the `Fallout.*` prefix locked to our account, but takes admin time.
Recommend option 1 for speed. List of IDs to reserve:
```
Fallout.Common
Fallout.Build
Fallout.Build.Shared
Fallout.Components
Fallout.GlobalTool
Fallout.MSBuildTasks
Fallout.ProjectModel
Fallout.SolutionModel
Fallout.SourceGenerators
Fallout.Tooling
Fallout.Tooling.Generator
Fallout.Utilities
Fallout.Utilities.IO.Compression
Fallout.Utilities.IO.Globbing
Fallout.Utilities.Net
Fallout.Utilities.Text.Json
Fallout.Utilities.Text.Yaml
```
Required
- NuGet.org account under organization or personal handle
- NuGet API key with package-create scope
Done when
- All 17 IDs registered (placeholder `0.0.0-reserved` or via Reserved Names policy)
- Owner verified — we control the IDs
- Document the chosen account in the strategy memory
Activity
chore(rebrand): NUKE → Fallout cosmetic pass (license headers, docs, …
ChrisonSimtian commentedon May 20, 2026
Re-scope after the #35 bridge strategy
The original framing here ("squatters can claim our IDs if we delay") still stands, but the urgency has shifted now that #35 settled on GitHub Packages as the primary distribution feed during the rebrand window:
R0 + 12-24moper the timeline in the plan doc).What this means for this issue
The placeholder-publish step (option 1 in the body) is still worth doing, just not as a P4-blocker. It's defensive — squatter prevention — independent of when we actually start using the IDs. Doable in ~30 minutes any time we have an empty package CI lane.
Action proposal:
Will leave open for the milestone owner to decide; happy to execute the placeholder publish if you give the green light on the nuget.org account/API key setup.
chore(release): publish to nuget.org as primary feed (#58)
ChrisonSimtian commentedon May 20, 2026
Update 2026-05-21: Reservation request submitted to
support@nuget.org.Prefix requested:
Fallout(coversFallout.*). Cited the 15 currently-published packages atv10.2.12as evidence.Holding this issue open until Microsoft responds (typical turnaround 1–7 business days). Will update with the outcome.
ChrisonSimtian commentedon May 21, 2026
Approved by Microsoft —
Fallout.*prefix is now reserved on nuget.org. Published packages get the verified-owner badge; nobody else can publish to the namespace.chore(globaltool)!: rename Fallout.GlobalTool → Fallout.Cli
chore(globaltool)!: rename Fallout.GlobalTool → Fallout.Cli (#206)