mesh-catalog

6 Commits

Include renames

Author	SHA1	Message	Date
jschoubben	8e402c82bf	Pin mesh-sdk 2da0de7, the release's final head, in the modules the release changes (issue 774) mesh/delivery ready: it is merged on the Approve Details mesh/check checking 8e402c82bfb2 on 12c2574c9d54 \| novox/mesh-catalog#560 in group feat/774-l3-reland mesh/delivery-group group feat/774-l3-reland checking: the checker's verdict is out of date: novox/mesh-catalog@8e402c82bfb2 was judged on trunk f61265f7a0f3, … Details	2026-10-30 01:15:38 +01:00
jschoubben	9cb177cae6	Pin mesh-sdk 6e4a301 in the modules the release changes, and keep the others on their pins (issue 774)	2026-10-30 00:23:45 +01:00
jschoubben	1b16720030	Pin mesh-sdk 007b6fd, the release's final head (issue 774)	2026-10-30 00:10:13 +01:00
jschoubben	1f0ff6ed98	Every offer of twenty providers says its credential form; a check refuses one that does not; re-pin sdk 6b8c694 (issue 1952)	2026-10-29 22:49:41 +01:00
jochen	60641176ab	systemd-resolved: say when a route's domains do cross the bus mesh/merge-gate pass: builds new: modules/systemd-resolved, sent nowhere; no bus step; every machine composes with the change as it did without (4 of 4 com… Details mesh/repo-check pass: its merge-check.sh passed Details mesh/delivery stopped: covered: its merge 3da80a4b5051 adds a new module sent nowhere (plan moves no module) and is contained in a1406e7d796c which is de… Details	2026-10-07 21:35:49 +02:00
jochen	d53571213c	systemd-resolved: a machine's own resolver, routing a VPN's domains by link (hq ADR 0247) mesh/merge-gate fail: builds new: modules/systemd-resolved, sent nowhere; no bus step; a manifest the change touches fails the module check: modules/system… Details mesh/repo-check fail: its merge-check.sh failed: long-running resources without health: 70 Details mesh/delivery superseded: a newer head of the same pull request Details Holds node-resolver and provides split-dns at the machine's reach, for a machine whose VPN client pushes resolvers of its own. It writes the resolver file naming the machine's private address, gives resolved the mesh's resolvers as the default route, and serves routes, route and unroute on the mesh and, over a root-only socket, on the machine. Its guard keeps an outside write of the file for the module that handles it and puts the module's file back: at once when taken, after 90 s otherwise, so a write nothing declared to handle is still raised by the node-engine.	2026-10-07 21:28:11 +02:00