From f45b9bd3fcc586b14bf6ab21c7bf9f88602c7cb8 Mon Sep 17 00:00:00 2001 From: Anthony Ettinger Date: Sat, 1 Aug 2026 14:47:09 +0000 Subject: [PATCH] chore(release): v0.16.1 v0.16.0 shipped the catch-all routing machinery and wired none of it in, so upgrading to it changed nothing: `dns enable` still wrote every claimed ending onto one `Domains=` line, systemd-resolved still accepted about 1090 of them and dropped the rest without an error a caller could see, and `curl ` still could not resolve. The release notes said routing had stopped being a list. It had not. #200 wires it, and makes it conditional rather than assumed: the upstreams are read from /etc/resolv.conf before routing is switched, and catch-all is only written when there is somewhere to forward. With no upstreams the per-ending list stays, because pointing every lookup at a bridge that cannot forward takes the machine's DNS with it rather than just Moshpit names. #201 keeps the resolver up when its socket errors after bind. The list is also getting worse on its own: 4593 endings this morning, 4882 by the afternoon, against a resolver cap near 1090. Co-Authored-By: Claude Opus 5 (1M context) --- package.json | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/package.json b/package.json index 8db7bd0..7b752f2 100644 --- a/package.json +++ b/package.json @@ -1,6 +1,6 @@ { "name": "moshcode", - "version": "0.16.0", + "version": "0.16.1", "type": "module", "description": "moshcode — a metal wrapper for coding engines and native UGig/CoinPay workflow CLIs, with OpenPRD and moshscript", "bin": {