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 75e8212a..84933229 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 @@ -964,3 +964,11 @@ Where two preparers disagreed, the chosen one is named. subject) need them; parsing the gate's id form would couple the bridge to it (P9). `performed`'s value is the outcome and when, plus the act's repository and number as the act names them; nothing else. No trim of the live state: the whole values expire with the template's TTL. P7, P4, P9. +- **H-A-183 (a pin is the version the registry published for that package path, 20:02)** Met at main.39 + (19:58): the pin of H-A-161 named the newest release of the module holding the package (v0.1.97 of the builder for + its package `builds`, v0.1.25 of the bus module for `busgrants`), and the Go seat looks for the tag `/v`, which no release wrote for those packages: "invalid version: unknown revision", for every importer + of a nested package. A Go package's version is its tag (G ยง370): the pin is the newest version the registry + published for that package path, as the package-published events name it (path and version), never the module's + release number; a package the registry never published is unpinned and its importer's build waits for its publish + (H-A-165) and fails loud past the bound. P3, P7.