From 1209008abab0eab8010d9cbfde25d86f5059cba5 Mon Sep 17 00:00:00 2001 From: jochen Date: Tue, 17 Nov 2026 01:30:16 +0100 Subject: [PATCH] Answer A-457b: the builder's republish-max-versions setting goes with the path it bounded --- 03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md | 3 +++ 1 file changed, 3 insertions(+) diff --git a/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md b/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md index 2b29e9a8..828ac6c9 100644 --- a/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md +++ b/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md @@ -1442,3 +1442,6 @@ the principle that settles it, cited as "design 47 G A-n". written; never because its artifacts are published, so a release that never comes is tried again. At its start the builder asks an item for every reservation of a done build, whatever its artifacts. (From the review of A-456a and A-457a: one key per release filled the 1 MiB state for good, and an item went before its release.) +- **A-457b** (A-457, A-457a; principle 7) The builder's setting `republish-max-versions` goes: it bounded what one + `running` or `manifest-reads-changed` event queued for publish, and A-457 retired that path, so nothing reads it. + A value set for it in the mesh's configuration is left unread and may be removed there. (From the review of A-457a.) -- 2.54.0