Repository navigation
Add v1.6 breaking-change ledger + CLAUDE.md tracking rule - #8260
Merged
Aaronontheweb merged 1 commit intoJun 12, 2026
Merged
Conversation
Introduces BREAKING_CHANGES_V1.6.md to record every breaking behavior, wire-format, or public-API change merged to dev during the v1.6 cycle, and adds a CLAUDE.md rule requiring such changes to be logged there in the same PR until a stable v1.6.0 ships. Seeds the ledger with the planned Source.ActorRef PoisonPill/Kill behavior change.
Aaronontheweb
enabled auto-merge (squash)
June 12, 2026 20:25
Aaronontheweb
disabled auto-merge
June 12, 2026 20:25
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
Adds a process for tracking breaking changes during the v1.6 development cycle.
BREAKING_CHANGES_V1.6.md(new, repo root) — a living ledger of every breaking behavior, wire-format, or public-API change merged todevahead of a stablev1.6.0. Includes the definition of "breaking", lifecycle rules (recorded in the same PR; retired once v1.6.0 ships), an entry-format template, and aStatuscolumn so an in-flight change can be listed asPlannedand flipped toMergedwhen it lands.CLAUDE.md— new step in "Making Changes" plus a "Tracking Breaking Changes (v1.6 cycle)" subsection making the ledger mandatory for breaking changes until v1.6.0 ships.The ledger is seeded with the first known entry (status
Planned): the upcomingSource.ActorRef<T>migration off the legacyActorPublisher, which dropsPoisonPill/Kill-as-completion behavior.Why
During the v1.6 run-up there will be several intentional breaking changes. Capturing them in one place as they land — rather than reconstructing them at release time — keeps the eventual upgrade guide accurate and gives reviewers a single spot to weigh each break.
Docs-only / process change; no source or test impact.