chore: publish the global tool as Fallout.GlobalTools#371
Merged
Conversation
The dotnet-tool package id was defaulting to the assembly name (Fallout.Cli), but the intended install name is Fallout.GlobalTools (matches Dennis's docs fix in cc077a6). Fallout.Cli was never pushed to nuget.org, so this is a pre-publication rename — non-breaking. Set the package identity, not the code: - Fallout.Cli.csproj: add <PackageId>Fallout.GlobalTools</PackageId>. Assembly/namespace stay Fallout.Cli; command stays `fallout`. Verified: pack produces Fallout.GlobalTools.*.nupkg. - templates/dotnet-tools.json + Program.Setup.cs comment: the manifest `fallout :setup` writes into user repos now pins `fallout.globaltools`. - UpdateNotificationAttribute: the in-tool update prompt now says `dotnet tool update Fallout.GlobalTools -g`. Docs match the new install name: - README install + upgrade note, introduction, 03-execution, github-actions, CONTRIBUTING pin reference, rebrand-plan mapping (package id vs namespace). - migration/from-globaltool-to-cli.md → draft:true (unpublished): it describes the never-released Fallout.Cli rename, now superseded. No Fallout.Cli → Fallout.GlobalTools migration is published (nobody to migrate). Deliberately left (not user-facing / need a coordinated publish first): - .config/dotnet-tools.json — repo's own dogfood pin (fallout.cli 10.3.45); can't flip until a Fallout.GlobalTools version is published. - tools/unlist-*.json, CHANGELOG history — records of already-published ids. - architecture/repository-layout/dependencies tables — name the internal project (Fallout.Cli), which is unchanged. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
ChrisonSimtian
force-pushed
the
chore/publish-tool-as-fallout-globaltools
branch
from
June 5, 2026 09:34
4c19d76 to
4816eb4
Compare
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.
Follow-up to Dennis's
cc077a6e("docs: update global tool name"), which set the install name toFallout.GlobalToolsin 2 docs but left the rest of the repo onFallout.Cli.The root cause:
Fallout.Cli.csprojhad no<PackageId>, so the package defaulted to the assembly nameFallout.Cli— i.e. Dennis's docs and the actual published id disagreed. This change makes them agree onFallout.GlobalTools.Not a breaking change:
Fallout.Cliwas never pushed to nuget.org, so this is a pre-publication rename. Targetsmain/target/2026.What changed
Package identity (not the code):
Fallout.Cli.csproj→<PackageId>Fallout.GlobalTools</PackageId>. Assembly/namespace stayFallout.Cli; command staysfallout. ✅ Verifieddotnet packemitsFallout.GlobalTools.*.nupkg.templates/dotnet-tools.json+Program.Setup.cscomment — the manifestfallout :setupwrites into user repos now pinsfallout.globaltools.UpdateNotificationAttribute— in-tool update prompt →dotnet tool update Fallout.GlobalTools -g.Docs (match the install name — point a):
introduction,03-execution,05-cicd/github-actions,CONTRIBUTINGpin ref,rebrand-planmapping.migration/from-globaltool-to-cli.md→draft: true(unpublished — point b). It documents the never-released→ Fallout.Clirename, now superseded; noFallout.Cli → Fallout.GlobalToolsmigration is published since nobody is onFallout.Cli. ✅ Verified the page is excluded from the built site.✅ Docs site builds clean; install pages render
Fallout.GlobalTools, noFallout.Cli.Deliberately left (flagging for a maintainer call)
.config/dotnet-tools.json— the repo's own dogfood pin (fallout.cli10.3.45). Can't flip tofallout.globaltoolsuntil a version is actually published under the new id, ordotnet tool restorebreaks the build.tools/unlist-*.json,CHANGELOG.mdchore(globaltool)!: rename Fallout.GlobalTool → Fallout.Cli #206 narrative — records of already-published ids; not rewritten.architecture/repository-layout/dependenciescomponent tables — these name the internal project (Fallout.Cli), which is unchanged. Left as-is; happy to switch them to the package name if you'd prefer consistency.🤖 Generated with Claude Code