Pin mesh-sdk at the fix that refuses an unresolvable machine alone (issue 1833) #437

Merged

mesh-tools merged 2 commits from fix/1833-one-machine-alone into main

2026-10-22 16:10:20 +00:00

Author	SHA1	Message	Date
jschoubben	28a278c146	Take mesh-sdk at bd7731f: a machine that does not resolve keeps its name and its address in the mesh as well as its tunnel (issue 1833) mesh/check failed: unit: ..test: node:internal/modules/esm/resolve:241 \| 28a278c1462a on b8f77577fed2 \| unit 3353 run, 0 kept, 7 skipped \| integration… mesh/repo-check head 28a278c1462a merged into trunk 11e364bd439f — pass: its merge-check.sh passed Details mesh/merge-gate head 28a278c1462a merged into trunk 11e364bd439f — pass: group fix/1833-one-machine-alone composed: every machine composes with the change … Details mesh/delivery delivered Details mesh/delivery-group group fix/1833-one-machine-alone delivered: every member is delivered Details	2026-10-22 15:27:27 +02:00
jschoubben	c34ab0e43a	Take mesh-sdk at c154bde: a machine that does not resolve keeps its place on the private network, so it alone is refused (issue 1833) One machine whose modules could not be resolved left the private network uncomposable when it was the hub, and every send to every machine was held. The SDK now keeps a refused machine at the place the controller already holds for it.	2026-10-22 15:04:47 +02:00