Answer A-457b: the builder's republish-max-versions setting goes with the path it bounded
This commit is contained in:
@@ -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.)
|
||||
|
||||
Reference in New Issue
Block a user