novox/mesh-host
8
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

Feature 57 (config and provisioning): release mesh-host #116

Merged
mesh-tools merged 1 commits from release/57-config-and-provisioning into main 2026-10-16 09:32:16 +00:00
Conversation 6 Commits 1 Files Changed 37
+3836 -60
mesh-tools commented 2026-10-16 08:26:22 +00:00
Member
Copy Link
Copy Source

Feature 57's release of mesh-host (the node-engine), as one commit on top of main: tree db310999 = the release branch merged with main (reviewed and merged there: #114; the one conflicting lock line already held main's addition). Route approved by the operator 10:26. Delivery group bundle A with mesh-sdk, mesh-controller and hq.

Feature 57's release of mesh-host (the node-engine), as one commit on top of main: tree db310999 = the release branch merged with main (reviewed and merged there: #114; the one conflicting lock line already held main's addition). Route approved by the operator 10:26. Delivery group bundle A with mesh-sdk, mesh-controller and hq.
mesh-tools added 1 commit 2026-10-16 08:26:23 +00:00
Feature 57 (config and provisioning): release mesh-host, the reviewed release branch on top of main
mesh/merge-gate head bff1ac14a198 merged into trunk 49c9002c04d3 beside mesh-controller#355@8c381172 — pass: builds mesh-host → ace, g14, novox, shanks; no…
Details
mesh/repo-check head bff1ac14a198 merged into trunk 49c9002c04d3 beside mesh-controller#355@8c381172 — pass: its merge-check.sh passed
Details
mesh/delivery delivered
Details
mesh/delivery-group group release/57-config-and-provisioning delivered: every member is delivered
Details
bff1ac14a1
mesh-tools commented 2026-10-16 08:26:37 +00:00
Author
Member
Copy Link
Copy Source

Delivery novox/mesh-host@bff1ac14a198 — delivered since 2026-10-16T09:39:08Z

Delivery plan — builds mesh-host → ace, g14, novox, shanks; no bus step

  • tier 0: mesh-host
  • ace: receives mesh-host
  • g14: receives mesh-host
  • novox: receives mesh-host
  • shanks: receives mesh-host
  • grants step: if this changes what the bus's user list says (a new tool, subject or user), novox is sent that list alone, every build there kept, before mesh-host is judged on its first machine

Group release/57-config-and-provisioning, in order: novox/hq@e7417cf124 → novox/mesh-controller@8c381172e7 → novox/mesh-host@bff1ac14a1 → novox/mesh-sdk@1bc5719b8b

Machines

  • mesh-host on every machine running it: sent

Transitions

  • 2026-10-16 08:26 (new) → proposed (announced): novox/mesh-host#116's head announced
  • 2026-10-16 08:28 proposed → checked (checked): a verdict names this commit and the trunk's head as its trunk commit
  • 2026-10-16 08:28 checked → rejected (refused): the gate failed or could not run, or the repository's own check failed
  • 2026-10-16 08:32 rejected → proposed (recheck): its check ran at 10:28 before its group sibling mesh-controller #355 (8c381172) was opened at 10:29; judge it beside that sibling (ADR 0382)
  • 2026-10-16 08:35 proposed → checked (checked): a verdict names this commit and the trunk's head as its trunk commit
  • 2026-10-16 08:35 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
  • 2026-10-16 09:33 ready → published (merged): on the trunk its modules follow: merged there, and its walk opened — or nothing for a walk to move
  • 2026-10-16 09:33 published → delivering (go): its walk started: let go by this owner in its group's order, by a person, or on the controller's own path — not a failed walk that carried a later commit for it, after which it waits for a walk of its own commit
  • 2026-10-16 09:39 delivering → delivered (done): its walk is done, carrying its own commit: every machine of its deploy plan passed, or was left as its policy says

The commit's note under refs/notes/mesh-plan keeps every transition: git log --notes=mesh-plan.

<!-- mesh-delivery:view --> **Delivery** `novox/mesh-host@bff1ac14a198` — **delivered** since 2026-10-16T09:39:08Z **Delivery plan** — builds mesh-host → ace, g14, novox, shanks; no bus step - tier 0: mesh-host - ace: receives mesh-host - g14: receives mesh-host - novox: receives mesh-host - shanks: receives mesh-host - grants step: if this changes what the bus's user list says (a new tool, subject or user), novox is sent that list alone, every build there kept, before mesh-host is judged on its first machine **Group** `release/57-config-and-provisioning`, in order: novox/hq@e7417cf1248c → novox/mesh-controller@8c381172e7ea → novox/mesh-host@bff1ac14a198 → novox/mesh-sdk@1bc5719b8b85 - novox/mesh-controller@8c381172e7ea before novox/mesh-host@bff1ac14a198: built by, over engine before controller - novox/mesh-controller@8c381172e7ea before novox/mesh-sdk@1bc5719b8b85: built by - composed together: pass — every machine composes with the change as it did without (4 of 4 compose) **Machines** - mesh-host on every machine running it: sent **Transitions** - 2026-10-16 08:26 (new) → proposed (announced): novox/mesh-host#116's head announced - 2026-10-16 08:28 proposed → checked (checked): a verdict names this commit and the trunk's head as its trunk commit - 2026-10-16 08:28 checked → rejected (refused): the gate failed or could not run, or the repository's own check failed - 2026-10-16 08:32 rejected → proposed (recheck): its check ran at 10:28 before its group sibling mesh-controller #355 (8c381172) was opened at 10:29; judge it beside that sibling (ADR 0382) - 2026-10-16 08:35 proposed → checked (checked): a verdict names this commit and the trunk's head as its trunk commit - 2026-10-16 08:35 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail - 2026-10-16 09:33 ready → published (merged): on the trunk its modules follow: merged there, and its walk opened — or nothing for a walk to move - 2026-10-16 09:33 published → delivering (go): its walk started: let go by this owner in its group's order, by a person, or on the controller's own path — not a failed walk that carried a later commit for it, after which it waits for a walk of its own commit - 2026-10-16 09:39 delivering → delivered (done): its walk is done, carrying its own commit: every machine of its deploy plan passed, or was left as its policy says The commit's note under `refs/notes/mesh-plan` keeps every transition: `git log --notes=mesh-plan`.
mesh-tools commented 2026-10-16 08:28:08 +00:00
Author
Member
Copy Link
Copy Source

Merge check at bff1ac14
Judged: head bff1ac14a198 merged into trunk 49c9002c04d3; read beside it: mesh-catalog 173c5d5ef434, mesh-controller d70bb1f38867, mesh-controller-main d70bb1f38867, mesh-tools 6b3e15042fee

  • mesh/merge-gate: FAIL — the controller the mesh runs does not build with this change's validator: docker run --label mesh.build=build-1792139188440155834 --volume /var/lib/build-agent/judge-cache/homes/build-1792139188440155834:/var/lib/build-agent/judge-cache/homes/build-1792139188440155834 --volume /var/lib/build-agent/judge-cache/go-cache:/var/lib/build-agent/judge-cache/go-cache --rm --network host --volume /var/lib/build-agent/workspace:/var/lib/build-agent/workspace --workdir /var/lib/build-agent/workspace/check/mesh-controller --user 0:0 --env HOME=/var/lib/build-agent/judge-cache/homes/build-1792139188440155834 --env GIT_CONFIG_COUNT=1 --env GIT_CONFIG_KEY_0=safe.directory --env GIT_CONFIG_VALUE_0=* --env XDG_CONFIG_HOME=/var/lib/build-agent/judge-cache/homes/build-1792139188440155834/.config --env GIT_CONFIG_GLOBAL=/dev/null --env GIT_CONFIG_NOSYSTEM=1 --env GOENV=off --env GOCACHE=/var/lib/build-agent/judge-cache/go-cache --env GOPATH=/var/lib/build-agent/judge-cache/homes/build-1792139188440155834/go --env CGO_ENABLED=0 --env GOFLAGS=-mod=vendor -buildvcs=false --env GOPROXY=off novox.internal:5100/mesh-tools-go/build@sha256:2054591ca034b68323d87ec887ba34f56819cb3364034360c0777da4b314dd54 go build -o /var/lib/build-agent/workspace/check/bin/judge-with-this-validator ./cmd/mesh-controller: exit status 1 (modules: mesh-host)
  • mesh/repo-check: PASS — its merge-check.sh passed

Delivery plan — builds mesh-host → ace, g14, novox, shanks; no bus step

  • tier 0: mesh-host
  • ace: receives mesh-host
  • g14: receives mesh-host
  • novox: receives mesh-host
  • shanks: receives mesh-host
  • grants step: if this changes what the bus's user list says (a new tool, subject or user), novox is sent that list alone, every build there kept, before mesh-host is judged on its first machine
  • read by no module's build: RELEASE-57.md, cmd/mesh-host/filling_test.go, cmd/mesh-host/movesecret_test.go, cmd/mesh-host/nodekey_test.go, cmd/mesh-host/units_test.go, cmd/mesh-host/vaultbox_nats_test.go, examples/foundation-first-node.lock, internal/apply/filled_apply_test.go, internal/apply/filled_library_test.go, internal/apply/filled_test.go, internal/apply/ownership_test.go, internal/apply/vault_sealed_test.go, internal/declaration/ownership_test.go, internal/declaration/provisioner_test.go, internal/filling/filling.go, internal/filling/filling_test.go, internal/link/movesecret_test.go, validate/validate_test.go

Run by the build seat on novox as build-1792139188440155834 (builds --log build-1792139188440155834).

--- its merge-check.sh (go toolchain)
ok  	github.com/novox/mesh-host/cmd/mesh-bootstrap	1.027s
ok  	github.com/novox/mesh-host/cmd/mesh-host	10.246s
ok  	github.com/novox/mesh-host/examples	1.051s
ok  	github.com/novox/mesh-host/internal/accounts	3.963s
ok  	github.com/novox/mesh-host/internal/apply	37.572s
ok  	github.com/novox/mesh-host/internal/bootstrap	7.584s
ok  	github.com/novox/mesh-host/internal/bundle	1.018s
ok  	github.com/novox/mesh-host/internal/declaration	1.062s
ok  	github.com/novox/mesh-host/internal/filling	1.741s
ok  	github.com/novox/mesh-host/internal/firewall	1.873s
ok  	github.com/novox/mesh-host/internal/identity	2.057s
ok  	github.com/novox/mesh-host/internal/image	1.013s
ok  	github.com/novox/mesh-host/internal/inventory	1.041s
ok  	github.com/novox/mesh-host/internal/link	10.666s
ok  	github.com/novox/mesh-host/internal/liveness	3.009s
ok  	github.com/novox/mesh-host/internal/meshcli	1.549s
ok  	github.com/novox/mesh-host/internal/network	1.054s
ok  	github.com/novox/mesh-host/internal/outward	1.057s
ok  	github.com/novox/mesh-host/internal/profile	1.727s
ok  	github.com/novox/mesh-host/internal/reachable	1.015s
ok  	github.com/novox/mesh-host/internal/store	2.300s
ok  	github.com/novox/mesh-host/internal/system	1.021s
ok  	github.com/novox/mesh-host/internal/tunnel	1.029s
ok  	github.com/novox/mesh-host/internal/units	1.014s
ok  	github.com/novox/mesh-host/internal/upgrade	1.867s
ok  	github.com/novox/mesh-host/internal/witness	37.705s
ok  	github.com/novox/mesh-host/packaging	1.019s
?   	github.com/novox/mesh-host/rootsearch	[no test files]
ok  	github.com/novox/mesh-host/validate	1.020s
**Merge check** at `bff1ac14` Judged: head `bff1ac14a198` merged into trunk `49c9002c04d3`; read beside it: mesh-catalog `173c5d5ef434`, mesh-controller `d70bb1f38867`, mesh-controller-main `d70bb1f38867`, mesh-tools `6b3e15042fee` - `mesh/merge-gate`: **FAIL** — the controller the mesh runs does not build with this change's validator: docker run --label mesh.build=build-1792139188440155834 --volume /var/lib/build-agent/judge-cache/homes/build-1792139188440155834:/var/lib/build-agent/judge-cache/homes/build-1792139188440155834 --volume /var/lib/build-agent/judge-cache/go-cache:/var/lib/build-agent/judge-cache/go-cache --rm --network host --volume /var/lib/build-agent/workspace:/var/lib/build-agent/workspace --workdir /var/lib/build-agent/workspace/check/mesh-controller --user 0:0 --env HOME=/var/lib/build-agent/judge-cache/homes/build-1792139188440155834 --env GIT_CONFIG_COUNT=1 --env GIT_CONFIG_KEY_0=safe.directory --env GIT_CONFIG_VALUE_0=* --env XDG_CONFIG_HOME=/var/lib/build-agent/judge-cache/homes/build-1792139188440155834/.config --env GIT_CONFIG_GLOBAL=/dev/null --env GIT_CONFIG_NOSYSTEM=1 --env GOENV=off --env GOCACHE=/var/lib/build-agent/judge-cache/go-cache --env GOPATH=/var/lib/build-agent/judge-cache/homes/build-1792139188440155834/go --env CGO_ENABLED=0 --env GOFLAGS=-mod=vendor -buildvcs=false --env GOPROXY=off novox.internal:5100/mesh-tools-go/build@sha256:2054591ca034b68323d87ec887ba34f56819cb3364034360c0777da4b314dd54 go build -o /var/lib/build-agent/workspace/check/bin/judge-with-this-validator ./cmd/mesh-controller: exit status 1 (modules: mesh-host) - `mesh/repo-check`: **PASS** — its merge-check.sh passed **Delivery plan** — builds mesh-host → ace, g14, novox, shanks; no bus step - tier 0: mesh-host - ace: receives mesh-host - g14: receives mesh-host - novox: receives mesh-host - shanks: receives mesh-host - grants step: if this changes what the bus's user list says (a new tool, subject or user), novox is sent that list alone, every build there kept, before mesh-host is judged on its first machine - read by no module's build: RELEASE-57.md, cmd/mesh-host/filling_test.go, cmd/mesh-host/movesecret_test.go, cmd/mesh-host/nodekey_test.go, cmd/mesh-host/units_test.go, cmd/mesh-host/vaultbox_nats_test.go, examples/foundation-first-node.lock, internal/apply/filled_apply_test.go, internal/apply/filled_library_test.go, internal/apply/filled_test.go, internal/apply/ownership_test.go, internal/apply/vault_sealed_test.go, internal/declaration/ownership_test.go, internal/declaration/provisioner_test.go, internal/filling/filling.go, internal/filling/filling_test.go, internal/link/movesecret_test.go, validate/validate_test.go Run by the build seat on novox as `build-1792139188440155834` (`builds --log build-1792139188440155834`). ``` --- its merge-check.sh (go toolchain) ok github.com/novox/mesh-host/cmd/mesh-bootstrap 1.027s ok github.com/novox/mesh-host/cmd/mesh-host 10.246s ok github.com/novox/mesh-host/examples 1.051s ok github.com/novox/mesh-host/internal/accounts 3.963s ok github.com/novox/mesh-host/internal/apply 37.572s ok github.com/novox/mesh-host/internal/bootstrap 7.584s ok github.com/novox/mesh-host/internal/bundle 1.018s ok github.com/novox/mesh-host/internal/declaration 1.062s ok github.com/novox/mesh-host/internal/filling 1.741s ok github.com/novox/mesh-host/internal/firewall 1.873s ok github.com/novox/mesh-host/internal/identity 2.057s ok github.com/novox/mesh-host/internal/image 1.013s ok github.com/novox/mesh-host/internal/inventory 1.041s ok github.com/novox/mesh-host/internal/link 10.666s ok github.com/novox/mesh-host/internal/liveness 3.009s ok github.com/novox/mesh-host/internal/meshcli 1.549s ok github.com/novox/mesh-host/internal/network 1.054s ok github.com/novox/mesh-host/internal/outward 1.057s ok github.com/novox/mesh-host/internal/profile 1.727s ok github.com/novox/mesh-host/internal/reachable 1.015s ok github.com/novox/mesh-host/internal/store 2.300s ok github.com/novox/mesh-host/internal/system 1.021s ok github.com/novox/mesh-host/internal/tunnel 1.029s ok github.com/novox/mesh-host/internal/units 1.014s ok github.com/novox/mesh-host/internal/upgrade 1.867s ok github.com/novox/mesh-host/internal/witness 37.705s ok github.com/novox/mesh-host/packaging 1.019s ? github.com/novox/mesh-host/rootsearch [no test files] ok github.com/novox/mesh-host/validate 1.020s ```
mesh-tools commented 2026-10-16 08:35:42 +00:00
Author
Member
Copy Link
Copy Source

Merge check at bff1ac14
Judged: head bff1ac14a198 merged into trunk 49c9002c04d3; read beside it: mesh-catalog 173c5d5ef434, mesh-controller e8dac13a4977, mesh-controller-main d70bb1f38867, mesh-tools 6b3e15042fee
Siblings read beside it: novox/mesh-controller#355 8c381172e7ea merged onto d70bb1f38867 (main); judged by sibling novox/mesh-controller#355 merge e8dac13a4977

  • mesh/merge-gate: PASS — every machine composes with the change as it did without (4 of 4 compose) (modules: mesh-host)
  • mesh/repo-check: PASS — its merge-check.sh passed

Delivery plan — builds mesh-host → ace, g14, novox, shanks; no bus step

  • tier 0: mesh-host
  • ace: receives mesh-host
  • g14: receives mesh-host
  • novox: receives mesh-host
  • shanks: receives mesh-host
  • grants step: if this changes what the bus's user list says (a new tool, subject or user), novox is sent that list alone, every build there kept, before mesh-host is judged on its first machine
  • read by no module's build: RELEASE-57.md, cmd/mesh-host/filling_test.go, cmd/mesh-host/movesecret_test.go, cmd/mesh-host/nodekey_test.go, cmd/mesh-host/units_test.go, cmd/mesh-host/vaultbox_nats_test.go, examples/foundation-first-node.lock, internal/apply/filled_apply_test.go, internal/apply/filled_library_test.go, internal/apply/filled_test.go, internal/apply/ownership_test.go, internal/apply/vault_sealed_test.go, internal/declaration/ownership_test.go, internal/declaration/provisioner_test.go, internal/filling/filling.go, internal/filling/filling_test.go, internal/link/movesecret_test.go, validate/validate_test.go

Run by the build seat on shanks as build-1792139562848621857 (builds --log build-1792139562848621857).

--- the gate: mesh-host
mesh-host: ok
long-running resources without health: 0
files asking for a setting without saying whether it is trusted: 0
1 manifest(s) checked. Judged against the seats this binary carries; a claim on one of the mesh's own seats is judged fully at registration, and a seat declared by a module not given here reads as unknown. Identities judged on a 6-character machine name, against the bounds of the providers given here
judging 0 module(s) changed against 4 machine(s), as the snapshot of 2026-10-16T01:34:49Z says they run
composing every machine as the mesh is
the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued
the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued
composing every machine with the change
the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued
the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued
merge gate: PASS — every machine composes with the change as it did without (4 of 4 compose)
judged by controller development build against the facts of 2026-10-16T01:34:49Z

machines:
  - a machine (f35): composes
  - holds mesh-dns-resolver (idt): composes
  - holds git, holds mesh-artifact-store, holds mesh-broker, holds mesh-catalog, holds mesh-delivery, holds mesh-dns-resolver, holds mesh-store, holds mesh-vault, holds npm-package-registry, the control node, the hub (ygcyr): composes
  - a machine (yvbpsm): composes

a merge would rebuild 1 module(s) in 1 tier(s): mesh-host

notes:
  - RELEASE-57.md, cmd/mesh-host/filling_test.go, cmd/mesh-host/movesecret_test.go, cmd/mesh-host/nodekey_test.go, cmd/mesh-host/units_test.go, cmd/mesh-host/vaultbox_nats_test.go, examples/foundation-first-node.lock, internal/apply/filled_apply_test.go, internal/apply/filled_library_test.go, internal/apply/filled_test.go, internal/apply/ownership_test.go, internal/apply/vault_sealed_test.go, internal/declaration/ownership_test.go, internal/declaration/provisioner_test.go, internal/filling/filling.go, internal/filling/filling_test.go, internal/link/movesecret_test.go and validate/validate_test.go read by no module's build, and rebuild nothing (issue 280)
--- its merge-check.sh (go toolchain)
ok  	github.com/novox/mesh-host/cmd/mesh-bootstrap	1.015s
ok  	github.com/novox/mesh-host/cmd/mesh-host	7.728s
ok  	github.com/novox/mesh-host/examples	1.030s
ok  	github.com/novox/mesh-host/internal/accounts	1.490s
ok  	github.com/novox/mesh-host/internal/apply	7.355s
ok  	github.com/novox/mesh-host/internal/bootstrap	4.305s
ok  	github.com/novox/mesh-host/internal/bundle	1.032s
ok  	github.com/novox/mesh-host/internal/declaration	1.074s
ok  	github.com/novox/mesh-host/internal/filling	1.750s
ok  	github.com/novox/mesh-host/internal/firewall	1.817s
ok  	github.com/novox/mesh-host/internal/identity	1.112s
ok  	github.com/novox/mesh-host/internal/image	1.031s
ok  	github.com/novox/mesh-host/internal/inventory	1.054s
ok  	github.com/novox/mesh-host/internal/link	10.490s
ok  	github.com/novox/mesh-host/internal/liveness	2.115s
ok  	github.com/novox/mesh-host/internal/meshcli	1.566s
ok  	github.com/novox/mesh-host/internal/network	1.048s
ok  	github.com/novox/mesh-host/internal/outward	1.035s
ok  	github.com/novox/mesh-host/internal/profile	1.628s
ok  	github.com/novox/mesh-host/internal/reachable	1.034s
ok  	github.com/novox/mesh-host/internal/store	1.212s
ok  	github.com/novox/mesh-host/internal/system	1.036s
ok  	github.com/novox/mesh-host/internal/tunnel	1.044s
ok  	github.com/novox/mesh-host/internal/units	1.032s
ok  	github.com/novox/mesh-host/internal/upgrade	1.105s
ok  	github.com/novox/mesh-host/internal/witness	7.997s
ok  	github.com/novox/mesh-host/packaging	1.014s
?   	github.com/novox/mesh-host/rootsearch	[no test files]
ok  	github.com/novox/mesh-host/validate	1.014s
**Merge check** at `bff1ac14` Judged: head `bff1ac14a198` merged into trunk `49c9002c04d3`; read beside it: mesh-catalog `173c5d5ef434`, mesh-controller `e8dac13a4977`, mesh-controller-main `d70bb1f38867`, mesh-tools `6b3e15042fee` Siblings read beside it: novox/mesh-controller#355 `8c381172e7ea` merged onto `d70bb1f38867` (main); judged by sibling novox/mesh-controller#355 merge e8dac13a4977 - `mesh/merge-gate`: **PASS** — every machine composes with the change as it did without (4 of 4 compose) (modules: mesh-host) - `mesh/repo-check`: **PASS** — its merge-check.sh passed **Delivery plan** — builds mesh-host → ace, g14, novox, shanks; no bus step - tier 0: mesh-host - ace: receives mesh-host - g14: receives mesh-host - novox: receives mesh-host - shanks: receives mesh-host - grants step: if this changes what the bus's user list says (a new tool, subject or user), novox is sent that list alone, every build there kept, before mesh-host is judged on its first machine - read by no module's build: RELEASE-57.md, cmd/mesh-host/filling_test.go, cmd/mesh-host/movesecret_test.go, cmd/mesh-host/nodekey_test.go, cmd/mesh-host/units_test.go, cmd/mesh-host/vaultbox_nats_test.go, examples/foundation-first-node.lock, internal/apply/filled_apply_test.go, internal/apply/filled_library_test.go, internal/apply/filled_test.go, internal/apply/ownership_test.go, internal/apply/vault_sealed_test.go, internal/declaration/ownership_test.go, internal/declaration/provisioner_test.go, internal/filling/filling.go, internal/filling/filling_test.go, internal/link/movesecret_test.go, validate/validate_test.go Run by the build seat on shanks as `build-1792139562848621857` (`builds --log build-1792139562848621857`). ``` --- the gate: mesh-host mesh-host: ok long-running resources without health: 0 files asking for a setting without saying whether it is trusted: 0 1 manifest(s) checked. Judged against the seats this binary carries; a claim on one of the mesh's own seats is judged fully at registration, and a seat declared by a module not given here reads as unknown. Identities judged on a 6-character machine name, against the bounds of the providers given here judging 0 module(s) changed against 4 machine(s), as the snapshot of 2026-10-16T01:34:49Z says they run composing every machine as the mesh is the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued composing every machine with the change the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued merge gate: PASS — every machine composes with the change as it did without (4 of 4 compose) judged by controller development build against the facts of 2026-10-16T01:34:49Z machines: - a machine (f35): composes - holds mesh-dns-resolver (idt): composes - holds git, holds mesh-artifact-store, holds mesh-broker, holds mesh-catalog, holds mesh-delivery, holds mesh-dns-resolver, holds mesh-store, holds mesh-vault, holds npm-package-registry, the control node, the hub (ygcyr): composes - a machine (yvbpsm): composes a merge would rebuild 1 module(s) in 1 tier(s): mesh-host notes: - RELEASE-57.md, cmd/mesh-host/filling_test.go, cmd/mesh-host/movesecret_test.go, cmd/mesh-host/nodekey_test.go, cmd/mesh-host/units_test.go, cmd/mesh-host/vaultbox_nats_test.go, examples/foundation-first-node.lock, internal/apply/filled_apply_test.go, internal/apply/filled_library_test.go, internal/apply/filled_test.go, internal/apply/ownership_test.go, internal/apply/vault_sealed_test.go, internal/declaration/ownership_test.go, internal/declaration/provisioner_test.go, internal/filling/filling.go, internal/filling/filling_test.go, internal/link/movesecret_test.go and validate/validate_test.go read by no module's build, and rebuild nothing (issue 280) --- its merge-check.sh (go toolchain) ok github.com/novox/mesh-host/cmd/mesh-bootstrap 1.015s ok github.com/novox/mesh-host/cmd/mesh-host 7.728s ok github.com/novox/mesh-host/examples 1.030s ok github.com/novox/mesh-host/internal/accounts 1.490s ok github.com/novox/mesh-host/internal/apply 7.355s ok github.com/novox/mesh-host/internal/bootstrap 4.305s ok github.com/novox/mesh-host/internal/bundle 1.032s ok github.com/novox/mesh-host/internal/declaration 1.074s ok github.com/novox/mesh-host/internal/filling 1.750s ok github.com/novox/mesh-host/internal/firewall 1.817s ok github.com/novox/mesh-host/internal/identity 1.112s ok github.com/novox/mesh-host/internal/image 1.031s ok github.com/novox/mesh-host/internal/inventory 1.054s ok github.com/novox/mesh-host/internal/link 10.490s ok github.com/novox/mesh-host/internal/liveness 2.115s ok github.com/novox/mesh-host/internal/meshcli 1.566s ok github.com/novox/mesh-host/internal/network 1.048s ok github.com/novox/mesh-host/internal/outward 1.035s ok github.com/novox/mesh-host/internal/profile 1.628s ok github.com/novox/mesh-host/internal/reachable 1.034s ok github.com/novox/mesh-host/internal/store 1.212s ok github.com/novox/mesh-host/internal/system 1.036s ok github.com/novox/mesh-host/internal/tunnel 1.044s ok github.com/novox/mesh-host/internal/units 1.032s ok github.com/novox/mesh-host/internal/upgrade 1.105s ok github.com/novox/mesh-host/internal/witness 7.997s ok github.com/novox/mesh-host/packaging 1.014s ? github.com/novox/mesh-host/rootsearch [no test files] ok github.com/novox/mesh-host/validate 1.014s ```
mesh-tools added the mesh/ready label 2026-10-16 08:39:25 +00:00
mesh-tools commented 2026-10-16 08:39:37 +00:00
Author
Member
Copy Link
Copy Source

ready at bff1ac14a1

Tree db310999 = the reviewed release branch (#114). The operator's word for releasing feature 57: 10:10 and 10:26.

ready at bff1ac14a198a1e2181053582728024c758bb800 Tree db310999 = the reviewed release branch (#114). The operator's word for releasing feature 57: 10:10 and 10:26.
mesh-tools removed the mesh/ready label 2026-10-16 08:39:39 +00:00
mesh-tools commented 2026-10-16 08:39:40 +00:00
Author
Member
Copy Link
Copy Source

mesh-delivery: the ready mark at is cleared: the head is now bff1ac14a1, pushed after it. Mark the new head ready once it is reviewed.

mesh-delivery: the ready mark at is cleared: the head is now bff1ac14a198a1e2181053582728024c758bb800, pushed after it. Mark the new head ready once it is reviewed.
mesh-tools added the mesh/ready label 2026-10-16 08:41:11 +00:00
mesh-tools commented 2026-10-16 08:41:11 +00:00
Author
Member
Copy Link
Copy Source

ready at bff1ac14a1

Marked again (issue 873: the label was cleared).

ready at bff1ac14a198a1e2181053582728024c758bb800 Marked again (issue 873: the label was cleared).
mesh-tools merged commit cd13f7726e into main 2026-10-16 09:32:16 +00:00
mesh-tools deleted branch release/57-config-and-provisioning 2026-10-16 09:32:18 +00:00
Sign in to join this conversation.
Reviewers
No Reviewers
Labels
Clear labels
mesh/ready
Reviewed and ready: mesh-delivery merges at the marked head once its checks pass (hq ADR 0364)
No labels mesh/ready
Milestone
No items
No Milestone
Assignees
Clear assignees
jschoubben mesh-tools miel.truyen
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: novox/mesh-host#116