From b5c95dcc2184b5393fa3ca5a6340c10af69c6a19 Mon Sep 17 00:00:00 2001 From: Anthony Ettinger Date: Tue, 4 Aug 2026 04:37:53 +0000 Subject: [PATCH] chore(release): v0.4.1 MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Ships the resolver fix from #15, which has been on main since it merged but was never published: the version stayed at 0.4.0, so `npm i @moshcoder/moshpit-dns` still gives you a bridge that answers `ANSWER: 0` for names that resolve perfectly well. That authoritative-empty answer is the worst shape available — a client treats it as final, `dig` reports the name exists, and nothing logs an error. The bug is invisible from the outside, which is why it survived a release. Same pattern as #14: a fix sitting behind a stale version is not shipped, it is just merged. --- package.json | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/package.json b/package.json index a070512..7f59f1f 100644 --- a/package.json +++ b/package.json @@ -1,6 +1,6 @@ { "name": "@moshcoder/moshpit-dns", - "version": "0.4.0", + "version": "0.4.1", "type": "module", "license": "MIT", "description": "Resolve Moshpit names on this machine. A tiny DNS bridge for .whatever endings, routed per-suffix so the rest of the internet is untouched.",