From 84feb62eda994ba7ca7eeef1eb2926f17927abc5 Mon Sep 17 00:00:00 2001 From: jochen Date: Fri, 20 Nov 2026 17:45:47 +0100 Subject: [PATCH] Design 47 H: H-A-172, pins are in every form's fingerprint --- 03-DESIGN/01-to-be/47-milestones/H-lead-answers.md | 5 +++++ 1 file changed, 5 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 ba69af53..5f7188bd 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 @@ -895,3 +895,8 @@ Where two preparers disagreed, the chosen one is named. end while every placed mover's required steps passed; as soon as one failed or could not run and none is open the pipeline ends failed, and the why names each unplaced mover with its own reason (" has no registration", " waits on the publish of "). P3, P7. +- **H-A-172 (pins are in every form's fingerprint, 17:45)** Met in the build of H-A-167: the import form's + fingerprint (a module whose trunk build reported its imports) left the pins out, so such an importer never moved on + a re-pin and was never built again against the release. H-A-167 holds for both forms: a module's fingerprint + includes its sorted pins whatever form computed it, so every importer moves on a re-pin; a fingerprint with no pin + stays as it was. P3, P5, P7.