Build Go modules with Go's own release of the recipe's version, so the distribution's build no longer makes the guard refuse (issue 1560, ADR 0476)

+397 -40

4 Commits

Author	SHA1	Message	Date
mesh-tools	3c4deb8bee	Name the cause of a failed toolchain or module download, not Go's progress line before it (issue 1560, review round 1) mesh/merge-gate head 3c4deb8bee8b merged into trunk 76bb22c36270 — pass: builds mesh-build-go → g14, novox, shanks; no bus step; every machine composes wit… Details mesh/repo-check head 3c4deb8bee8b merged into trunk 76bb22c36270 — pass: its merge-check.sh passed, each part in its toolchain: merge-check.sh (go), merge-… Details mesh/delivery delivered Details	2026-10-21 00:59:12 +00:00
mesh-tools	4605fcf46d	Fill the shared module cache with the release by the probe before the real-go integration tests, and skip loudly when it cannot (issue 1560, ADR 0476)	2026-10-21 00:56:03 +00:00
mesh-tools	c5f8f81a07	Test that every step and the probe run Go's own release and the probe fills the module cache (issue 1560, ADR 0476)	2026-10-21 00:51:40 +00:00
mesh-tools	3f60d1ff31	Build Go modules with Go's own release of the recipe's version, put in the module cache by the probe, so the distribution's build no longer makes the guard refuse (issue 1560, ADR 0476)	2026-10-21 00:50:56 +00:00

Build Go modules with Go's own release of the recipe's version, so the distribution's build no longer makes the guard refuse (issue 1560, ADR 0476) #400