From 14ed54de3d460a28d916ec4ac331a632fcea4824 Mon Sep 17 00:00:00 2001 From: Claude Date: Tue, 18 Aug 2026 08:48:10 +0000 Subject: [PATCH] Write up a prerelease without summary paragraphs The summary above the sections was described as scaling with the size of the release, which says nothing about `X.Y.Z.pre.N`: a prerelease can carry a large section and still be a checkpoint in a cycle rather than the cycle itself. Summarizing one means writing that summary twice -- once on the prerelease, again on the release proper that folds its pull requests into its own section -- so a prerelease carries the list alone. Co-Authored-By: Claude Opus 5 Claude-Session: https://claude.ai/code/session_01LrJnRwFjCYw9h5U8LkRqqP --- docs/release.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/docs/release.md b/docs/release.md index 0aae65e84..39ac44ffc 100644 --- a/docs/release.md +++ b/docs/release.md @@ -101,7 +101,8 @@ The sections always appear in this order; delete the ones that end up empty, whi on a small release. Two things scale with the size of the release: - **Summary paragraphs**, above the first section. A patch release usually has none, 4.1.0 has four - paragraphs, and 4.0.0 has nine. + paragraphs, and 4.0.0 has nine. A prerelease has none whatever its size: the cycle it belongs to + is summarized once, on the release proper that folds it in. - **A list of the types whose signatures changed**, as the first line of `### Signature updates`, written as `**Updated classes/modules/methods:**` followed by the names in backticks. Used on `X.Y.0` releases only.