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
Member

Builds design 47 H2 H-A-494 and its three addenda (hq design/47-H1-answers-59): pass 1 takes every pinned mesh package with GOPROXY=,off (a miss fails as the registry's answer naming @); pass 2 downloads the rest with the public proxy alone, no direct; a forge path a go.mod names at any version but the zero version is refused before either pass; an ask's commit pin is still placed from a pull request head; no binding is refused; GIT_SSH_COMMAND gone from the step env; design 51's recipe-test row refuses direct.

Reviewed-by: mesh-code-reviewer@shanks at 837cd2570a

Merged at once without the check, by the operator's word of 2026-11-22 21:05 (until design 47 is delivered). Opened by lead-47@shanks.

Builds design 47 H2 H-A-494 and its three addenda (hq design/47-H1-answers-59): pass 1 takes every pinned mesh package with GOPROXY=<registry>,off (a miss fails as the registry's answer naming <pkg>@<v>); pass 2 downloads the rest with the public proxy alone, no direct; a forge path a go.mod names at any version but the zero version is refused before either pass; an ask's commit pin is still placed from a pull request head; no binding is refused; GIT_SSH_COMMAND gone from the step env; design 51's recipe-test row refuses direct. Reviewed-by: mesh-code-reviewer@shanks at 837cd2570a14917e33cffc8c858a5af6bfcd65bf Merged at once without the check, by the operator's word of 2026-11-22 21:05 (until design 47 is delivered). Opened by lead-47@shanks.
mesh-tools added 1 commit 2026-11-22 20:14:23 +00:00
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)
mesh-tools merged commit bf972d1d34 into main 2026-11-22 20:14:42 +00:00
mesh-tools deleted branch fix/goproxy-registry-only 2026-11-22 20:14:43 +00:00
Sign in to join this conversation.
No Reviewers
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: novox/mesh-catalog#743