Point the tool manifest at the shipping package id and drop the CHANGELOG rule - #622
Merged
ChrisonSimtian merged 2 commits intoAug 4, 2026
Conversation
The manifest still pinned fallout.cli 10.3.45 — an unlisted version of a retired package id. Fallout.GlobalTool is the id the CLI ships under, and 10.4.0-rc.5 is the current release candidate. Verified with `dotnet tool restore`. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
CHANGELOG.md no longer exists, so the rule that every breaking change records an entry under a next-major [Unreleased] heading was unfollowable. Release notes are generated from PR labels via .github/release.yml, so the PR description plus its breaking-change label is now the durable record — point the rules there instead. Leaves the consumer-facing changelog features alone (ChangelogTasks, IHasChangelog, the Build.cs template): those are for user builds, not ours. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
ChrisonSimtian
added
target/vNext
ChrisonSimtian
marked this pull request as ready for review
August 4, 2026 05:20
This was referenced Aug 4, 2026
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 pieces of housekeeping that were both blocking cleanly closing out 10.4.
Tool manifest —
.config/dotnet-tools.jsonstill pinnedfallout.cli10.3.45, an unlisted version of a retired package id (last acceptance criterion on #575). Repointed atFallout.GlobalTool10.4.0-rc.5, the id the CLI actually ships under. Verified withdotnet tool restore.CHANGELOG rule —
CHANGELOG.mdwas deleted, so rule #1's "every breaking change gets aCHANGELOG.mdentry under the next-major[Unreleased]heading" was unfollowable (flagged in #575). Release notes are generated from PR labels via.github/release.yml, so the PR description +breaking-changelabel is the durable record. UpdatedAGENTS.md, the PR-creation flow it delegates to,CONTRIBUTING.md, therelease.ymlcomment, and the root-file list.Deliberately left alone:
ChangelogTasks,IHasChangelog, and theBuild.cstemplate — those are consumer-facing features for user builds, not this repo's process.Still referencing a CHANGELOG, left for a separate call:
docs/adr/0001-release-branch-model.md(historical record),docs/branching-and-release.mdEoL step,tests/Consumers/README.md.🤖 Generated with Claude Code