From f08d61099998c076a69fbee4a554291646d6567f Mon Sep 17 00:00:00 2001 From: jochen Date: Fri, 20 Nov 2026 17:26:03 +0100 Subject: [PATCH] Design 47 H: H-A-161, a package is pinned by its released version, never by a commit --- 03-DESIGN/01-to-be/47-milestones/H-lead-answers.md | 9 +++++++++ 1 file changed, 9 insertions(+) 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 eed823e3..ee5e0739 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 @@ -813,3 +813,12 @@ Where two preparers disagreed, the chosen one is named. for every re-serve: one serving routine owns a module's subscriptions, keeps those whose subject and queue are unchanged, adds the new, then stops the ones no longer named, so no subject is ever served twice or not at all. P3, P7. +- **H-A-161 (a package is pinned by its released version, never by a commit, 17:26)** Met in the builds of + main.15, main.20 and main.22: the indexer fills a module's `packages` (the pins the builder copies into the build + ask) with an accepted series' newest published version where it knows one, else with the commit of a module value + it holds, which Go turns into a pseudo-version of whatever that commit's tree was (mesh-delivery-sdk at a 11-19 + commit, nodeengine at the pre-H1 tree). G §370 makes a Go package's version its tag: a pin is the newest released + version of that package on the branch (the registry's, as the version-released events say), and a package with no + released version is not pinned at all; its importer's build then waits for that package's package-published by its + kind-1 edge (H §746, H-A-157) and fails loud past the builder's bound (H-A-155), never building against a commit. + P3, P7.