docs(changelog): the section describes one rollout state again - #11218
Merged
Conversation
#11207's frontend entry said "the chains are not identical — this one pushes `:latest` only after the promotion, where the API still pushes it alongside the deploy". #11212 is what changed that, so the sentence became false the moment it merged, and the section described two rollout states at once. Past tense, with the PR that closed the gap named rather than a position: the fragments fold in ABOVE the existing bullets at the release cut, so "the entry above" would be wrong now and right later, while "#11212" is true in both. Labelled skip-changelog: this is a correction to an existing entry, not a change worth its own line. It needs the label because the fragment gate compares bullet SETS, so an edited bullet is indistinguishable from an added one — measured, not assumed (`tools.changelog check` answered "[Unreleased] gained a bullet" when this same edit rode along in #11212). Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01UEScQMZFvxxNNyNJYryfa3
MarkusNeusinger
added
the
skip-changelog
Contributor
There was a problem hiding this comment.
🟢 Approval recommended
The documentation-only correction accurately reflects the merged deployment change.
Pull request overview
Updates the unreleased changelog to remain accurate after #11212 aligned the API deployment flow with the frontend.
Changes:
- Recasts the historical difference in past tense and records when the API caught up.
File summaries
| File | Description |
|---|---|
CHANGELOG.md |
Corrects the candidate-rollout entry. |
Review details
- Files reviewed: 1/1 changed files
- Comments generated: 0
- Review effort level: Balanced
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
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
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.
One line of
CHANGELOG.md, so the[Unreleased]section describes one rollout state instead of two.#11207's frontend entry said:
#11212 is what changed that, so the sentence became false the moment it merged. Now:
Past tense, and the closing PR named rather than a position: the release cut folds fragments in above the existing bullets, so "the entry above" would be wrong today and right after the cut, while
#11212is true in both.Why
skip-changelograther than a fragmentThis corrects an existing entry; it is not a change worth a release-notes line of its own. And it needs the label, because the fragment gate compares bullet sets — an edited bullet is indistinguishable from an added one. Measured rather than assumed, when this same edit first rode along in #11212:
That is the reason it was taken back out of #11212 and moved here.
The
skip-changeloglabel did not exist in this repository — #11215 documented it as the escape hatch without creating it — so it was created for this PR (grey, "No changelog fragment needed: this PR changes nothing worth a release-notes line"). The gate's ownif:condition now has something to match.Noted for later, not built here: the gate could tell an added bullet from a changed one by treating the bold title as the bullet's identity, which would let a correction like this pass without a label. That is a sibling-pair change for both repos, deliberately out of scope tonight.
🤖 Generated with Claude Code
https://claude.ai/code/session_01UEScQMZFvxxNNyNJYryfa3