diff --git a/03-DESIGN/01-to-be/47-milestones/H-lead-answers.md b/03-DESIGN/01-to-be/47-milestones/H-lead-answers.md index d3f8c2dd..f78a229c 100644 --- a/03-DESIGN/01-to-be/47-milestones/H-lead-answers.md +++ b/03-DESIGN/01-to-be/47-milestones/H-lead-answers.md @@ -1573,3 +1573,18 @@ Where two preparers disagreed, the chosen one is named. pipeline-ended is taken again and brings a mover the progress does not hold, the holder adds it to the progress at the mover's tier; its want is written when the progress reaches that tier, or at once when that tier has run already; never out of tier order. P7 (one tier rule for every mover), ADR 0682. +- **H-A-274 (a registry record holding the built digest ends the publish as published, 15:46)** Amends H-A-272: when + every missing artifact is held at its version with the built digest, the builder does not skip: it marks the + publish done from the registry's record (the artifact published, the version released when all are) and says so, + so a published event heard and lost never leaves an item asked for ever or skipped for ever. P4. +- **H-A-275 (a number a registry already holds at another digest is never reserved; a build so caught moves to the + next free number, 15:46)** Met live: the tool runner's release 0.1.37 is held by the artifact registry at another + digest than the build's, so its publish is asked again for ever and the release never comes. Before reserving a + number the builder reads each registry seat's versions for the module's artifacts and skips every number a registry + holds (the same rule as H-A-245 for tags, built now because the versions verb exists); a done build whose number + the registry holds at another digest is moved to the next free number with the finding version-held-elsewhere + (scope module) and its publish asked under the new number. In the builder. P2 (the registry's record is the truth + the number must follow), P4. +- **H-A-276 (a placed version outside the package file's range is said, 15:46)** Amends H-A-267: the Node build module + says in the journal when the latest release it places (the SDK's or another mesh package's) lies outside the range + the package file names. P4.