mesh-build-go: a mesh Go package comes from the Go package registry alone, two download passes (design 47 H2 H-A-494) #743

Merged
mesh-tools merged 1 commits from fix/goproxy-registry-only into main 2026-11-22 20:14:42 +00:00
1 Commits
Author SHA1 Message Date
jschoubben 837cd2570a mesh-build-go: take mesh packages from the Go package registry alone
The public proxy serves the forge's paths from git tags and direct reaches
the forge's git, so a version missing from the registry was found elsewhere
instead of failing loudly. The fetch now downloads in two passes over every
directory: first each pinned mesh package with GOPROXY=<seat>,off (a miss says
"the Go package registry holds no <pkg>@<v>"; no binding refuses "no Go
package registry bound"), and every zero-version requirement of the graph is
taken or refused then; second the rest of the build list with the public
proxy alone, no direct. Before either, a go.mod naming a mesh package at a
version other than the zero version is refused, so no forge path can reach
the public proxy; a pull request head is placed only for an ask's commit, and
the placement of go.mod-named pins goes. Every other go command (test, lint,
compile) runs with GOPROXY=off; GOPRIVATE and the account's ssh settings leave
goEnv, as repository fetches set their own.

Builds: design 47 H2 H-A-494, H-A-494 addendum (two downloads), H-A-494 second addendum (a forge path at a real version is refused), H-A-494 third addendum (a pull request head places only an ask's commit pin); design 51 Go packages (the recipe test refuses direct)
2026-11-22 21:10:09 +01:00