The Go build module's step workspace holds the generated-from directories and the same-repository zero-version packages (design 47 H, H-A-136, H-A-137) #710

Merged
mesh-tools merged 2 commits from fix/47-H1-zero-version-tree into main 2026-11-20 12:56:52 +00:00
2 Commits
Author SHA1 Message Date
jschoubben 30f274bcb0 mesh-build-go: a narrowed root module keeps its seats/ and every generated package
A module at the repository's root naming generated-from "." (mesh-contracts)
kept nothing of it: the narrowing kept "." alone, which prunes everything,
so the seat generator's check of go-meshconfig still found every file out
of step. Such a module now keeps the seats/ directory the generator reads
and the paths of every artifact naming generated-from; nothing else of the
root.

Builds: design 47 H H-A-137
2026-11-20 13:03:05 +01:00
jschoubben c52907a346 mesh-build-go: a narrowed workspace keeps generated-from and same-repository zero-version packages
The first pipeline of the clean state (main.3) failed every build of a
mesh-delivery-contracts client: the fetch narrowed the tree to the
artifact's paths (ADR 0499 clause 4), which removed
modules/mesh-delivery-sdk, so its requirement at the zero version found
"no module of that path in the fetched tree". The same narrowing left the
seat generator's out-of-step check without its seat definitions.

The narrowed workspace now also holds every generated-from directory an
artifact of the module names and the directory of every package of the
same repository the artifact's go.mod requires at the zero version, found
by the repository's manifests; the root's manifest and lock files are not
kept when narrowing from the root. The fetch's own Go modules stay those
under the artifact's paths (A-447a), not the added directories.

Builds: design 47 H H-A-136; design 47 G-22 A-447a

Claude-Session: https://claude.ai/code/session_01JG73KHUnBze48rdua8u2sy
2026-11-20 12:41:16 +01:00