From 6570469aebbe7f87a1790b534bb508369d06f715 Mon Sep 17 00:00:00 2001 From: jochen Date: Fri, 20 Nov 2026 20:06:17 +0100 Subject: [PATCH] Design 47 H: H-A-184, the pin stays within the series the module accepts --- 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 84933229..0eb5969a 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 @@ -972,3 +972,8 @@ Where two preparers disagreed, the chosen one is named. 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. +- **H-A-184 (the pin stays within the series the module accepts, 20:06)** Met in the build of H-A-183: a pin + by the package path across every series would move a module to a series it does not accept while its contents come + from the accepted one. The pin is the newest version the registry published for the package path within the + series the module accepts (the series that gives the fingerprint's contents); where the module accepts no series + yet, the newest published of the path. A publish in another series pins nothing and moves nothing. P7, P3.