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

Feature 57: pin the feature's SDK and node-engine on the release branch first (issue 804) #347

Closed
mesh-tools wants to merge 1 commits from 57-pins into feat/57-config-and-provisioning
pull from: 57-pins
merge into: :feat/57-config-and-provisioning
Conversation 3 Commits 1 Files Changed 5
+382 -18
mesh-tools commented 2026-10-15 21:58:38 +00:00
Member
Copy Link
Copy Source

Step 1 of 3 to break a wait between mesh-host #114 and mesh-controller #346 (operator's approval, 2026-10-15 ~23:55):

  1. this pull request: only go.mod/go.sum/vendor — mesh-sdk d3e18250 (on mesh-sdk's release branch, #28) and the mesh-host replace at 5a7ec377 (mesh-host #114's head). The vendor diff is mesh-host's internal/declaration and mesh-sdk's new seal package. Without it, mesh-host #114's gate fails: the release controller cannot build mesh-host's new declaration code, which imports seal (issue 755).
  2. recheck and merge mesh-host #114.
  3. fix one test on #346 and recheck it: its broker test reads mesh-host beside at the release branch, and needs #114's issue 662 change there.

Tree bcb34784 = local 2dd0fb21; built and vetted locally against the release head fcdecb43. Merging here delivers nothing.

Step 1 of 3 to break a wait between mesh-host #114 and mesh-controller #346 (operator's approval, 2026-10-15 ~23:55): 1. this pull request: only go.mod/go.sum/vendor — mesh-sdk d3e18250 (on mesh-sdk's release branch, #28) and the mesh-host replace at 5a7ec377 (mesh-host #114's head). The vendor diff is mesh-host's internal/declaration and mesh-sdk's new seal package. Without it, mesh-host #114's gate fails: the release controller cannot build mesh-host's new declaration code, which imports seal (issue 755). 2. recheck and merge mesh-host #114. 3. fix one test on #346 and recheck it: its broker test reads mesh-host beside at the release branch, and needs #114's issue 662 change there. Tree bcb34784 = local 2dd0fb21; built and vetted locally against the release head fcdecb43. Merging here delivers nothing.
mesh-tools added 1 commit 2026-10-15 21:58:39 +00:00
Pin the feature's SDK and node-engine so the release controller builds mesh-host's new code (issue 804)
mesh/merge-gate head bcb3478462ca merged into trunk fcdecb436117 — pass: [release feat/57-config-and-provisioning, judged by its controller 8e285bcd134f] t…
Details
mesh/repo-check head bcb3478462ca merged into trunk fcdecb436117 — fail: [release feat/57-config-and-provisioning, judged by its controller 8e285bcd134f] i…
Details
mesh/delivery stopped: the pull request closed unmerged
Details
bcb3478462 
mesh-host's declaration code now imports mesh-sdk's seal package (issue 755);
the release branch's controller vendors mesh-host, so it needs both pins
before mesh-host's own pull request can be judged by it.
mesh-tools commented 2026-10-15 21:58:44 +00:00
Author
Member
Copy Link
Copy Source

Delivery novox/mesh-controller@bcb3478462ca — stopped since 2026-10-16T01:36:34Z

Delivery plan — builds nothing: the change touches no module of the mesh's graph

Transitions

  • 2026-10-15 21:58 (new) → proposed (announced): novox/mesh-controller#347's head announced
  • 2026-10-15 22:02 proposed → checked (checked): a verdict names this commit and the trunk's head as its trunk commit
  • 2026-10-15 22:02 checked → rejected (refused): the gate failed or could not run, or the repository's own check failed
  • 2026-10-16 01:36 rejected → stopped (closed): the pull request closed unmerged

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

<!-- mesh-delivery:view --> **Delivery** `novox/mesh-controller@bcb3478462ca` — **stopped** since 2026-10-16T01:36:34Z **Delivery plan** — builds nothing: the change touches no module of the mesh's graph **Transitions** - 2026-10-15 21:58 (new) → proposed (announced): novox/mesh-controller#347's head announced - 2026-10-15 22:02 proposed → checked (checked): a verdict names this commit and the trunk's head as its trunk commit - 2026-10-15 22:02 checked → rejected (refused): the gate failed or could not run, or the repository's own check failed - 2026-10-16 01:36 rejected → stopped (closed): the pull request closed unmerged The commit's note under `refs/notes/mesh-plan` keeps every transition: `git log --notes=mesh-plan`.
mesh-tools commented 2026-10-15 22:02:55 +00:00
Author
Member
Copy Link
Copy Source

Merge check at bcb34784
Judged: head bcb3478462ca merged into trunk fcdecb436117; read beside it: mesh-catalog 1a2c917abfdb, mesh-controller-main 7543f64911c5, mesh-host 53fd32618916, mesh-tools 6b3e15042fee

  • mesh/merge-gate: PASS — [release feat/57-config-and-provisioning, judged by its controller 8e285bcd134f] the change touches no module of the mesh's graph
  • mesh/repo-check: FAIL — [release feat/57-config-and-provisioning, judged by its controller 8e285bcd134f] its merge-check.sh failed: --- FAIL: TestTheInstallersFirstUserListIsWhatTheControllerWouldCompose (0.75s); and TestTheCapturedSDKIsTheOneGoModPins

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

--- judged for the release branch feat/57-config-and-provisioning by its controller at 8e285bcd134f, with mesh-host's validator of feat/57-config-and-provisioning at 53fd32618916; read beside it: mesh-catalog feat/57-config-and-provisioning at 1a2c917abfdb, mesh-controller-main main at 7543f64911c5, mesh-host feat/57-config-and-provisioning at 53fd32618916, mesh-tools main at 6b3e15042fee
--- its merge-check.sh (go toolchain)
ok  	github.com/novox/mesh-controller/cmd/mesh-builder	1.087s
ok  	github.com/novox/mesh-controller/cmd/mesh-controller	190.851s
ok  	github.com/novox/mesh-controller/examples/objectstore-provisioner	1.029s
ok  	github.com/novox/mesh-controller/examples/postgres-provisioner	1.043s
ok  	github.com/novox/mesh-controller/examples/redis-provisioner	1.033s
ok  	github.com/novox/mesh-controller/examples/route-proxy	1.225s
ok  	github.com/novox/mesh-controller/internal/artifacts	1.070s
?   	github.com/novox/mesh-controller/internal/beside	[no test files]
--- FAIL: TestTheInstallersFirstUserListIsWhatTheControllerWouldCompose (0.75s)
    genesis_template_test.go:29: judged against /var/lib/build-agent/workspace/check/mesh-host as cloned beside this check
    genesis_template_test.go:48: the installer's user list lets the controller publish [$KV.mesh-controller_assignments.> $KV.mesh-controller_declared-config.> mesh.seat.mesh-controller.event.assignment-changed mesh.seat.mesh-controller.event.declared-config-changed], which it does not derive
FAIL
FAIL	github.com/novox/mesh-controller/internal/broker	3.456s
ok  	github.com/novox/mesh-controller/internal/builder	40.289s
ok  	github.com/novox/mesh-controller/internal/catalogue	8.746s
ok  	github.com/novox/mesh-controller/internal/conditions	2.625s
ok  	github.com/novox/mesh-controller/internal/envfile	1.035s
ok  	github.com/novox/mesh-controller/internal/facts	1.041s
ok  	github.com/novox/mesh-controller/internal/identity	4.941s
ok  	github.com/novox/mesh-controller/internal/inventory	36.039s
ok  	github.com/novox/mesh-controller/internal/lease	17.701s
ok  	github.com/novox/mesh-controller/internal/licences	3.958s
ok  	github.com/novox/mesh-controller/internal/licences/adapters	1.031s
nats: permissions violation: Permissions Violation for Publish to "mesh.seat.s.tool.v.anchor" on connection [5]
could not read whether b-1 was cancelled, so it is built: nats: no responders available for request
could not read whether b-2 was cancelled, so it is built: nats: no responders available for request
could not read whether b-3 was cancelled, so it is built: nats: no responders available for request
could not read whether b-3 was cancelled, so it is built: nats: no responders available for request
could not read whether w-1 was cancelled, so it is built: nats: no responders available for request
could not read whether w-2 was cancelled, so it is built: nats: no responders available for request
could not read whether w-3 was cancelled, so it is built: nats: no responders available for request
could not read whether build-old-seat was cancelled, so it is built: nats: no responders available for request
could not read whether b-594 was cancelled, so it is built: nats: no responders available for request
could not read whether b-594 was cancelled, so it is built: nats: no responders available for request
internal/link conformance: NOT JUDGED AGAINST THE CLONE: the seat placed no mesh-sdk beside this check in MESH_CHECK_BESIDE=/var/lib/build-agent/workspace/check (it does once mesh-controller #220 has rolled out); read the captured copy at 5933eb757d443293631be2bed27a96288c2348d8
--- FAIL: TestTheCapturedSDKIsTheOneGoModPins (0.00s)
    conformance_test.go:213: the SDK is captured at 5933eb757d443293631be2bed27a96288c2348d8 but go.mod pins d3e182503c19: capture it again at the pinned commit, as testdata/beside/CAPTURED says
2026/10/15 22:00:03 the notices of messages consumers gave up on cannot be taken, so none is kept until they can: asking about consumer controller on DEAD_LETTER_NOTICES: nats: stream not found
could not read whether build-1792101604086581301 was cancelled, so it is built: nats: no responders available for request
could not read whether build-1792101424086581301 was cancelled, so it is built: nats: no responders available for request
could not read whether build-1792101484086581301 was cancelled, so it is built: nats: no responders available for request
could not read whether build-1792101604824695536 was cancelled, so it is built: nats: no responders available for request
could not read whether build-1792101604825695536 was cancelled, so it is built: nats: no responders available for request
could not read whether build-1792101604826695536 was cancelled, so it is built: nats: no responders available for request
could not read whether build-1792101604827695536 was cancelled, so it is built: nats: no responders available for request
could not read whether build-1792101604828695536 was cancelled, so it is built: nats: no responders available for request
could not read whether build-1792101604829695536 was cancelled, so it is built: nats: no responders available for request
could not read whether build-1792101604830695536 was cancelled, so it is built: nats: no responders available for request
could not read whether build-1792101604831695536 was cancelled, so it is built: nats: no responders available for request
could not read whether build-1792101604832695536 was cancelled, so it is built: nats: no responders available for request
could not read whether build-1792101604833695536 was cancelled, so it is built: nats: no responders available for request
could not read whether build-1792101604834695536 was cancelled, so it is built: nats: no responders available for request
could not read whether build-1792101604835695536 was cancelled, so it is built: nats: no responders available for request
could not read whether build-1792101604836695536 was cancelled, so it is built: nats: no responders available for request
could not read whether build-1792101604837695536 was cancelled, so it is built: nats: no responders available for request
could not read whether build-1792101604838695536 was cancelled, so it is built: nats: no responders available for request
could not read whether build-1792101604839695536 was cancelled, so it is built: nats: no responders available for request
could not read whether build-1792101604840695536 was cancelled, so it is built: nats: no responders available for request
could not read whether build-1792101604841695536 was cancelled, so it is built: nats: no responders available for request
could not read whether build-1792101604844695536 was cancelled, so it is built: nats: no responders available for request
could not read whether build-1792101604847695536 was cancelled, so it is built: nats: no responders available for request
could not read whether build-1792101604842695536 was cancelled, so it is built: nats: no responders available for request
could not read whether build-1792101604843695536 was cancelled, so it is built: nats: no responders available for request
could not read whether build-1792101604845695536 was cancelled, so it is built: nats: no responders available for request
could not read whether build-1792101604846695536 was cancelled, so it is built: nats: no responders available for request
could not read whether build-1792100950901674241 was cancelled, so it is built: nats: no responders available for request
could not read whether build-1792101550901674241 was cancelled, so it is built: nats: no responders available for request
build-cancelled was cancelled by hand as this machine took it; not built
build-waited-cancelled was cancelled by hand as this machine took it; not built
2026/10/15 22:00:20 the notices of messages consumers gave up on cannot be taken, so none is kept until they can: nats: consumer not found
2026/10/15 22:00:35 how sonarr on media hears what it consumes gave up on message 1 of EVENTS (mesh.mod.gitea.event.pull.merged) after 5 deliveries; kept as dead letter 1
2026/10/15 22:00:36 another controller holds the controller's consumer on CONTROL; standing by until it lets go
2026/10/15 22:00:37 took the controller's consumer on CONTROL: the controller that held it let go
2026/10/15 22:00:38 kept what home-server says about the machine, and refused its account of declaration d11 (epoch 57, sequence 11, report 40): the account kept is newer
2026/10/15 22:00:38 kept what home-server says about the machine, and refused its account of declaration d12 (epoch 57, sequence 12, report 40): the account kept is newer
2026/10/15 22:00:40 kept what home-server says about the machine, and not its account of declaration d1: the mesh has sent it d2 since
2026/10/15 22:00:40 anchor took over the tunnel on wg0: its overlay key is the tunnel's now
FAIL
FAIL	github.com/novox/mesh-controller/internal/link	57.882s
ok  	github.com/novox/mesh-controller/internal/lint	2.501s
ok  	github.com/novox/mesh-controller/internal/outward	1.078s
ok  	github.com/novox/mesh-controller/internal/overlay	1.061s
ok  	github.com/novox/mesh-controller/internal/secrets	1.526s
ok  	github.com/novox/mesh-controller/internal/store	3.389s
ok  	github.com/novox/mesh-controller/internal/testbus	1.234s
ok  	github.com/novox/mesh-controller/internal/token	1.019s
FAIL
--- what failed, picked from the whole of its output (the whole is in the build's log)
--- FAIL: TestTheInstallersFirstUserListIsWhatTheControllerWouldCompose (0.75s)
    genesis_template_test.go:29: judged against /var/lib/build-agent/workspace/check/mesh-host as cloned beside this check
    genesis_template_test.go:48: the installer's user list lets the controller publish [$KV.mesh-controller_assignments.> $KV.mesh-controller_declared-config.> mesh.seat.mesh-controller.event.assignment-changed mesh.seat.mesh-controller.event.declared-config-changed], which it does not derive
FAIL	github.com/novox/mesh-controller/internal/broker	3.456s
--- FAIL: TestTheCapturedSDKIsTheOneGoModPins (0.00s)
    conformance_test.go:213: the SDK is captured at 5933eb757d443293631be2bed27a96288c2348d8 but go.mod pins d3e182503c19: capture it again at the pinned commit, as testdata/beside/CAPTURED says
FAIL	github.com/novox/mesh-controller/internal/link	57.882s
**Merge check** at `bcb34784` Judged: head `bcb3478462ca` merged into trunk `fcdecb436117`; read beside it: mesh-catalog `1a2c917abfdb`, mesh-controller-main `7543f64911c5`, mesh-host `53fd32618916`, mesh-tools `6b3e15042fee` - `mesh/merge-gate`: **PASS** — [release feat/57-config-and-provisioning, judged by its controller 8e285bcd134f] the change touches no module of the mesh's graph - `mesh/repo-check`: **FAIL** — [release feat/57-config-and-provisioning, judged by its controller 8e285bcd134f] its merge-check.sh failed: --- FAIL: TestTheInstallersFirstUserListIsWhatTheControllerWouldCompose (0.75s); and TestTheCapturedSDKIsTheOneGoModPins Run by the build seat on shanks as `build-1792101521360848751` (`builds --log build-1792101521360848751`). ``` --- judged for the release branch feat/57-config-and-provisioning by its controller at 8e285bcd134f, with mesh-host's validator of feat/57-config-and-provisioning at 53fd32618916; read beside it: mesh-catalog feat/57-config-and-provisioning at 1a2c917abfdb, mesh-controller-main main at 7543f64911c5, mesh-host feat/57-config-and-provisioning at 53fd32618916, mesh-tools main at 6b3e15042fee --- its merge-check.sh (go toolchain) ok github.com/novox/mesh-controller/cmd/mesh-builder 1.087s ok github.com/novox/mesh-controller/cmd/mesh-controller 190.851s ok github.com/novox/mesh-controller/examples/objectstore-provisioner 1.029s ok github.com/novox/mesh-controller/examples/postgres-provisioner 1.043s ok github.com/novox/mesh-controller/examples/redis-provisioner 1.033s ok github.com/novox/mesh-controller/examples/route-proxy 1.225s ok github.com/novox/mesh-controller/internal/artifacts 1.070s ? github.com/novox/mesh-controller/internal/beside [no test files] --- FAIL: TestTheInstallersFirstUserListIsWhatTheControllerWouldCompose (0.75s) genesis_template_test.go:29: judged against /var/lib/build-agent/workspace/check/mesh-host as cloned beside this check genesis_template_test.go:48: the installer's user list lets the controller publish [$KV.mesh-controller_assignments.> $KV.mesh-controller_declared-config.> mesh.seat.mesh-controller.event.assignment-changed mesh.seat.mesh-controller.event.declared-config-changed], which it does not derive FAIL FAIL github.com/novox/mesh-controller/internal/broker 3.456s ok github.com/novox/mesh-controller/internal/builder 40.289s ok github.com/novox/mesh-controller/internal/catalogue 8.746s ok github.com/novox/mesh-controller/internal/conditions 2.625s ok github.com/novox/mesh-controller/internal/envfile 1.035s ok github.com/novox/mesh-controller/internal/facts 1.041s ok github.com/novox/mesh-controller/internal/identity 4.941s ok github.com/novox/mesh-controller/internal/inventory 36.039s ok github.com/novox/mesh-controller/internal/lease 17.701s ok github.com/novox/mesh-controller/internal/licences 3.958s ok github.com/novox/mesh-controller/internal/licences/adapters 1.031s nats: permissions violation: Permissions Violation for Publish to "mesh.seat.s.tool.v.anchor" on connection [5] could not read whether b-1 was cancelled, so it is built: nats: no responders available for request could not read whether b-2 was cancelled, so it is built: nats: no responders available for request could not read whether b-3 was cancelled, so it is built: nats: no responders available for request could not read whether b-3 was cancelled, so it is built: nats: no responders available for request could not read whether w-1 was cancelled, so it is built: nats: no responders available for request could not read whether w-2 was cancelled, so it is built: nats: no responders available for request could not read whether w-3 was cancelled, so it is built: nats: no responders available for request could not read whether build-old-seat was cancelled, so it is built: nats: no responders available for request could not read whether b-594 was cancelled, so it is built: nats: no responders available for request could not read whether b-594 was cancelled, so it is built: nats: no responders available for request internal/link conformance: NOT JUDGED AGAINST THE CLONE: the seat placed no mesh-sdk beside this check in MESH_CHECK_BESIDE=/var/lib/build-agent/workspace/check (it does once mesh-controller #220 has rolled out); read the captured copy at 5933eb757d443293631be2bed27a96288c2348d8 --- FAIL: TestTheCapturedSDKIsTheOneGoModPins (0.00s) conformance_test.go:213: the SDK is captured at 5933eb757d443293631be2bed27a96288c2348d8 but go.mod pins d3e182503c19: capture it again at the pinned commit, as testdata/beside/CAPTURED says 2026/10/15 22:00:03 the notices of messages consumers gave up on cannot be taken, so none is kept until they can: asking about consumer controller on DEAD_LETTER_NOTICES: nats: stream not found could not read whether build-1792101604086581301 was cancelled, so it is built: nats: no responders available for request could not read whether build-1792101424086581301 was cancelled, so it is built: nats: no responders available for request could not read whether build-1792101484086581301 was cancelled, so it is built: nats: no responders available for request could not read whether build-1792101604824695536 was cancelled, so it is built: nats: no responders available for request could not read whether build-1792101604825695536 was cancelled, so it is built: nats: no responders available for request could not read whether build-1792101604826695536 was cancelled, so it is built: nats: no responders available for request could not read whether build-1792101604827695536 was cancelled, so it is built: nats: no responders available for request could not read whether build-1792101604828695536 was cancelled, so it is built: nats: no responders available for request could not read whether build-1792101604829695536 was cancelled, so it is built: nats: no responders available for request could not read whether build-1792101604830695536 was cancelled, so it is built: nats: no responders available for request could not read whether build-1792101604831695536 was cancelled, so it is built: nats: no responders available for request could not read whether build-1792101604832695536 was cancelled, so it is built: nats: no responders available for request could not read whether build-1792101604833695536 was cancelled, so it is built: nats: no responders available for request could not read whether build-1792101604834695536 was cancelled, so it is built: nats: no responders available for request could not read whether build-1792101604835695536 was cancelled, so it is built: nats: no responders available for request could not read whether build-1792101604836695536 was cancelled, so it is built: nats: no responders available for request could not read whether build-1792101604837695536 was cancelled, so it is built: nats: no responders available for request could not read whether build-1792101604838695536 was cancelled, so it is built: nats: no responders available for request could not read whether build-1792101604839695536 was cancelled, so it is built: nats: no responders available for request could not read whether build-1792101604840695536 was cancelled, so it is built: nats: no responders available for request could not read whether build-1792101604841695536 was cancelled, so it is built: nats: no responders available for request could not read whether build-1792101604844695536 was cancelled, so it is built: nats: no responders available for request could not read whether build-1792101604847695536 was cancelled, so it is built: nats: no responders available for request could not read whether build-1792101604842695536 was cancelled, so it is built: nats: no responders available for request could not read whether build-1792101604843695536 was cancelled, so it is built: nats: no responders available for request could not read whether build-1792101604845695536 was cancelled, so it is built: nats: no responders available for request could not read whether build-1792101604846695536 was cancelled, so it is built: nats: no responders available for request could not read whether build-1792100950901674241 was cancelled, so it is built: nats: no responders available for request could not read whether build-1792101550901674241 was cancelled, so it is built: nats: no responders available for request build-cancelled was cancelled by hand as this machine took it; not built build-waited-cancelled was cancelled by hand as this machine took it; not built 2026/10/15 22:00:20 the notices of messages consumers gave up on cannot be taken, so none is kept until they can: nats: consumer not found 2026/10/15 22:00:35 how sonarr on media hears what it consumes gave up on message 1 of EVENTS (mesh.mod.gitea.event.pull.merged) after 5 deliveries; kept as dead letter 1 2026/10/15 22:00:36 another controller holds the controller's consumer on CONTROL; standing by until it lets go 2026/10/15 22:00:37 took the controller's consumer on CONTROL: the controller that held it let go 2026/10/15 22:00:38 kept what home-server says about the machine, and refused its account of declaration d11 (epoch 57, sequence 11, report 40): the account kept is newer 2026/10/15 22:00:38 kept what home-server says about the machine, and refused its account of declaration d12 (epoch 57, sequence 12, report 40): the account kept is newer 2026/10/15 22:00:40 kept what home-server says about the machine, and not its account of declaration d1: the mesh has sent it d2 since 2026/10/15 22:00:40 anchor took over the tunnel on wg0: its overlay key is the tunnel's now FAIL FAIL github.com/novox/mesh-controller/internal/link 57.882s ok github.com/novox/mesh-controller/internal/lint 2.501s ok github.com/novox/mesh-controller/internal/outward 1.078s ok github.com/novox/mesh-controller/internal/overlay 1.061s ok github.com/novox/mesh-controller/internal/secrets 1.526s ok github.com/novox/mesh-controller/internal/store 3.389s ok github.com/novox/mesh-controller/internal/testbus 1.234s ok github.com/novox/mesh-controller/internal/token 1.019s FAIL --- what failed, picked from the whole of its output (the whole is in the build's log) --- FAIL: TestTheInstallersFirstUserListIsWhatTheControllerWouldCompose (0.75s) genesis_template_test.go:29: judged against /var/lib/build-agent/workspace/check/mesh-host as cloned beside this check genesis_template_test.go:48: the installer's user list lets the controller publish [$KV.mesh-controller_assignments.> $KV.mesh-controller_declared-config.> mesh.seat.mesh-controller.event.assignment-changed mesh.seat.mesh-controller.event.declared-config-changed], which it does not derive FAIL github.com/novox/mesh-controller/internal/broker 3.456s --- FAIL: TestTheCapturedSDKIsTheOneGoModPins (0.00s) conformance_test.go:213: the SDK is captured at 5933eb757d443293631be2bed27a96288c2348d8 but go.mod pins d3e182503c19: capture it again at the pinned commit, as testdata/beside/CAPTURED says FAIL github.com/novox/mesh-controller/internal/link 57.882s ```
mesh-tools commented 2026-10-16 01:35:10 +00:00
Author
Member
Copy Link
Copy Source

Closed: superseded by #346, merged into feat/57-config-and-provisioning at 2026-10-16 03:32 as cf897e89, which carries these pins (mesh-sdk d3e18250, mesh-host 5a7ec377). Feature 57, issue 804.

Closed: superseded by #346, merged into feat/57-config-and-provisioning at 2026-10-16 03:32 as cf897e89, which carries these pins (mesh-sdk d3e18250, mesh-host 5a7ec377). Feature 57, issue 804.
mesh-tools closed this pull request 2026-10-16 01:35:10 +00:00

Pull request closed

Please reopen this pull request to perform a merge.
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
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-controller#347