chore: Fallout.Cli follow-ups (manifest flip + ownership-gotcha doc)#209
Merged
Conversation
Two small follow-ups after the Fallout.GlobalTool → Fallout.Cli rename (#206) and the first-publish 403 we hit on the release pipeline (#208). ## 1. Flip this repo's `.config/dotnet-tools.json` to `Fallout.Cli` `Fallout.Cli 10.3.41` is now live on nuget.org (post-merge release pipeline rerun published it once the org-ownership issue cleared). Switching this repo's local tool manifest from the legacy `fallout.globaltool 10.3.37` pin to `fallout.cli 10.3.41`. Verified locally: > dotnet tool restore Tool 'fallout.cli' (version '10.3.41') was restored. Available commands: fallout Restore was successful. ## 2. Document the nuget.org first-publish gotcha in CLAUDE.md The "release pipeline" section already mentioned the `Fallout.*` prefix reservation but didn't cover the operational footgun we just hit: the nuget.org upload UI defaults the package owner to your personal account, not the org. Even after a successful upload that reserves the ID, the org's `NUGET_API_KEY` 403s on subsequent CI pushes until ownership is transferred to the org. Added two short paragraphs to the "Release pipeline" section walking through: 1. The owner-defaults-to-personal trap (with the fix), linked to #208. 2. The 5-30 min validation lag between upload-accepted and API-key-permission-propagated. So next time someone (likely future-Claude or future-Chris) adds a new `Fallout.X` package, this footgun is the first thing they see. ## Refs - #206 — Fallout.GlobalTool → Fallout.Cli rename (merged). - #208 — bug report for the ownership-mismatch we hit (will close once this doc note lands). Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
1 task
ChrisonSimtian
added a commit
that referenced
this pull request
May 27, 2026
Picks up four patches shipped overnight, notably: - #212: AES-GCM v2 secret format (per-secret salt+nonce, 600K PBKDF2) - #211: drop unused Build() + surface dotnet-tools.json in IDE config group - #209: manifest flip + ownership-gotcha doc - #207: ship README.md with every Fallout.* nupkg Verified locally: `dotnet tool restore` pulls 10.3.45 cleanly, `dotnet fallout --help` runs through the new in-tool runner without issue. 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.
Two small follow-ups after #206 (rename) and #208 (the first-publish 403 we hit on the release pipeline).
1. Flip this repo's
.config/dotnet-tools.jsontoFallout.CliFallout.Cli 10.3.41is now live on nuget.org (the release pipeline rerun published it once the org-ownership issue cleared). Switching this repo's local tool manifest from the legacyfallout.globaltool 10.3.37pin tofallout.cli 10.3.41.Verified locally:
2. Document the nuget.org first-publish gotcha in CLAUDE.md
The "Release pipeline" section in
CLAUDE.mdalready mentioned theFallout.*prefix reservation but didn't cover the operational footgun we just hit: the nuget.org upload UI defaults the package owner to your personal account, not the org. Even after a successful upload that reserves the ID, the org'sNUGET_API_KEY403s on subsequent CI pushes until ownership is transferred to the org.Added two short paragraphs to the "Release pipeline" section walking through:
So next time someone (likely future-Claude or future-Chris) adds a new
Fallout.Xpackage, this footgun is the first thing they see.Refs
Test plan
ubuntu-latestCI goes green — verifiesdotnet tool restoreresolvesFallout.Cli 10.3.41from nuget.org cleanly in CI as well.