mesh-catalog/modules/build-agent/go.mod at e0bc919d4945bb5f13f971f74643a0b714cf45da - mesh-catalog - Gitea: Git with a cup of tea

novox/mesh-catalog

Files

T

jochen e0bc919d49

mesh/merge-gate head e0bc919d4945 merged into trunk f88e3452f8b8 — pass: builds build-agent → ace, g14, novox, shanks; no bus step; every machine composes …

Details

mesh/repo-check head e0bc919d4945 merged into trunk f88e3452f8b8 — pass: its merge-check.sh passed, each part in its toolchain: merge-check.sh (go), merge-…

Details

mesh/delivery covered: a later merge that contains it was delivered: novox/mesh-catalog@2f5e97030a5c (merged as 5cd608ba into main, walk plan-17918799551…

Details

mesh/delivery-group group fix/121-genesis-package-registry delivered: every member is delivered

Details

Let genesis assign the build agent before the package registry exists (hq issue 121, ADR 0336)

build-agent's npm-package-registry becomes optional, so genesis's step 13 is no
longer refused with 'nothing provides npm-package-registry'. Until gitea is
assigned, the agent on genesis's node reads the genesis-package-registry
own-secret the installer seals at the packages step; it is issued outside the
mesh, so no other machine is given one. The binding and its credential are
composed only while bound (ADR 0330 §6), and no file names them otherwise.

2026-10-13 02:50:39 +02:00

4 lines

28 B

AMPL

Raw Blame History

	`module build-agent`

	`go 1.22`