Release notes list every change with its pull request instead of "see CHANGELOG.md" (#4390)

GitHub release pages now list every change a release ships, one plain
line each, linked to the pull request that made it, instead of one
headline per version or "see CHANGELOG.md".

Why: the release page is where people read what changed, and recent
releases went out saying only "see CHANGELOG.md".

Nothing to do: the next release uses it; a release with no CHANGELOG
entry stops with `NOTES_MISSING` instead of publishing a stub.

Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com>
This commit is contained in:
Garry Tanandcapy-ai[bot] authored and GitHub committed 2026-11-17 17:14:39 +00:00
1 parent b1c32824fd
commit a9da30363c
12 files changed
+551 -118

No files matched your search

+3 -2
View File
@@ -239,8 +239,9 @@ moves `stable` more than once in 72 hours otherwise, except for a verified
security or regression fix (`--security` or `--regression`, with `--ref`): it takes the newest green commit on main's first-parent history
(its required check succeeded, the backstop check succeeded, every check run
completed and none failed, no active freeze), tags it `v<VERSION>`, publishes a
GitHub Release whose notes are one line per CHANGELOG version since the
previous release, and fast-forwards `stable`. New installs and team-mode installs
GitHub Release whose notes list every change in the CHANGELOG versions since
the previous release, one line each with the pull request that made it
([release notes](../../docs/releases.md#release-notes)), and fast-forwards `stable`. New installs and team-mode installs
follow `stable`; `gstack-config set update_channel main` follows every merge. A
hotfix is `--ref <sha on main>`, held by the same floor. Details, the floor's
refusal codes and the "nothing green in the window" failure mode: