From c7850092fa08cea79e9ffcbf66a3b975781b5913 Mon Sep 17 00:00:00 2001 From: jochen Date: Thu, 12 Nov 2026 15:16:30 +0100 Subject: [PATCH] Correct A-285: the group's packages are group-packages, since packages already holds the Go versions Claude-Session: https://claude.ai/code/session_01NcbgfGKaxw984XyAPfLm4h --- 03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md b/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md index 8b6b7b57..0c785505 100644 --- a/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md +++ b/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md @@ -402,8 +402,9 @@ the principle that settles it, cited as "design 47 G A-n". contracts) by the form ADR 0500 ยง5 gives the SDK, and serves them to every member that imports them; the latest published version is used only for a package the group does not change. - **A-285** (A-284; principles 7 and 8) The fetch of a build step carries the group's packages as one list, - `packages`, each a package of a member at its commit with `path`, its directory in that member (empty for the - member's root); the single `package` field and its tagged form go. The build module packs each and places it by + `group-packages` (beside `packages`, which stays the Go mesh packages' versions), each a package of a member at + its commit with `path`, its directory in that member (empty for the member's root); the single `package` field + and its tagged form go. The build module packs each and places it by its `package.json` name in every member that names it, in place of the registry's. The SDK's `lib` artifact names its paths (`package.json`, `package-lock.json`, `tsconfig.json`, `src`) in mesh-sdk's manifest, so the indexer holds them and a change to them is a changed package.