Repository navigation
chore(changelog): regenerate the Unreleased block from changelog.d/ - #1160
Merged
Merged
Conversation
`make docs-fragments-check` fails on pristine master: merged PRs add fragments
under changelog.d/ but nothing re-renders CHANGELOG.md's Unreleased block, so the
two drift apart. The gate names its own remedy, which is what this runs:
scripts/release/concat-changelog-fragments.sh --write
Finding, NOT fixed here because it changes what users see in a release:
regenerating prints
WARNING: changelog.d/chore/ is not a Keep-a-Changelog section; fragments here are SKIPPED.
WARNING: changelog.d/refactor/ is not a Keep-a-Changelog section; fragments here are SKIPPED.
Those two directories hold 27 fragments (24 chore, 3 refactor) whose content has
never reached CHANGELOG.md. The generator's SECTIONS list is the canonical
Keep-a-Changelog set -- added, changed, deprecated, removed, fixed, security --
so the skip is arguably by design: chores and refactors are not user-facing. But
the directories exist, authors keep writing to them, and the only signal is a
stderr warning nobody sees unless they run the script by hand.
That is a policy question with two defensible answers (map them onto Changed, or
delete the directories and reject the sections at PR time), so it is reported
rather than decided unilaterally.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
This reverts commit 80aa7a0.
lusoris
marked this pull request as ready for review
August 31, 2026 01:26
lusoris
enabled auto-merge (squash)
August 31, 2026 01:26
lusoris
marked this pull request as draft
August 31, 2026 01:27
auto-merge was automatically disabled
August 31, 2026 01:27
Pull request was converted to draft
lusoris
marked this pull request as ready for review
August 31, 2026 01:27
lusoris
enabled auto-merge (squash)
August 31, 2026 01:27
lusoris
marked this pull request as draft
August 31, 2026 01:27
auto-merge was automatically disabled
August 31, 2026 01:27
Pull request was converted to draft
lusoris
marked this pull request as ready for review
August 31, 2026 01:27
lusoris
enabled auto-merge (squash)
August 31, 2026 01:27
This was referenced Aug 31, 2026
3 of 6 tasks
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.
Summary
make docs-fragments-check— a required check — fails on pristine master.Merged PRs add fragments under
changelog.d/but nothing re-rendersCHANGELOG.md's Unreleased block, so the two drift apart. The gate names its ownremedy, which is all this PR runs:
A finding I did not fix here
Regenerating prints:
Those two directories hold 27 fragments — 24 under
chore/, 3 underrefactor/— whose content has never reachedCHANGELOG.md.The generator's section list is the canonical Keep-a-Changelog set
(
added changed deprecated removed fixed security), so the skip is arguably bydesign: chores and refactors are not user-facing. But the directories exist,
authors keep writing to them, and the only signal is a stderr warning nobody sees
unless they run the script by hand.
That is a policy question with two defensible answers — map them onto
Changed,or delete the directories and reject those sections at PR time — so it is
reported rather than decided unilaterally. Happy to do either.
Type
build/ci— tooling / infraChecklist
make docs-fragments-checkexits 0 (it exits 2 on master).CHANGELOG.mdis generated output.Bug-status hygiene
docs/state.md— no runtime bug; this is a generated-artefact sync.Netflix golden-data gate
assertAlmostEqual(...)score.Deep-dive deliverables
AGENTS.mdinvariant note — no rebase-sensitive invariants.changelog.d/changed/regen-unreleased-block.md.CHANGELOG.mdandchangelog.d/are fork-added.Reproducer
See the dropped fragments:
Known follow-ups
chore/+refactor/question above.regeneration should be a release-please step rather than a manual one, since
the gate is required and the fix is purely mechanical.