Skip to content

πŸ› changelog: recover v6-only fragments stranded in src/changelog.d - #18361

Merged
clubanderson merged 1 commit into
v6from
fix/18264-stranded-fragments-v6
Nov 16, 2026
Merged

clubanderson merged 1 commit into
v6from
fix/18264-stranded-fragments-v6

Conversation

@clubanderson

Copy link
Copy Markdown
Member

Refs #18264. This is the v6 companion to #18360, which fixes the same problem on v5.

Why

v6 has 81 fragments under src/changelog.d/. The release compiler never reads that directory. 13 of them are the v5 strays from #18360. The other 68 exist only on v6, and none of them reach the v6 top-up.

What

Note for the top-up that carries #18360

#18360 also moves fixed-adopted-pr-rebase.md (#13280) into the root changelog.d/ on v5. v6 had already moved and released that entry (f478d20, now in v6's CHANGELOG.md under "2026-11-08 (v6.0.0)"). When the top-up brings changelog.d/fixed-adopted-pr-rebase.md into v6, drop it in the resolution so the entry does not appear twice.

This PR should merge before the top-up carries #18360's release-time backstop. Otherwise v6's next release compile fails on the leftover strays, which is the backstop doing its job.

πŸ€– Generated with Claude Code

68 of v6's 81 fragments under src/changelog.d/ exist only on v6 and were
never compiled into CHANGELOG.md. Move 64 to the repo-root changelog.d/ so
the next v6 release carries them (two needed the required '- ' bullet
prefix), and delete 4 whose entries v6's CHANGELOG.md already records
(#11943, #11945 under v6.0.0; #11558 under v6.0.0; #10026 under v5.114.0).

The other 13 are the v5 strays; the v6 top-up carries their move from the
v5 fix.

Refs #18264

Signed-off-by: Andy Anderson <andy@clubanderson.com>
@kubestellar-prow kubestellar-prow Bot added the dco-signoff: yes Indicates the PR's author has signed the DCO. label Nov 16, 2026
@kubestellar-prow

Copy link
Copy Markdown
Contributor

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign hanthor for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Details Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@kubestellar-prow kubestellar-prow Bot added the size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. label Nov 16, 2026
@clubanderson
clubanderson merged commit 0cd0a4f into v6 Nov 16, 2026
80 of 85 checks passed
@kubestellar-prow
kubestellar-prow Bot deleted the fix/18264-stranded-fragments-v6 branch November 16, 2026 02:54
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dco-signoff: yes Indicates the PR's author has signed the DCO. size/XS Denotes a PR that changes 0-9 lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant