chore(release): v0.4.0 - #14
Merged
Merged
Conversation
Ships the `records` command (#12), which inspects the CNAME, MX and TXT records published for a name, with type filtering and --json. It has been on main since #12 merged but was never published: the version stayed at 0.3.0, so `npm i @moshcoder/moshpit-dns` still gave you a build with no `records` subcommand at all. Same shape as the AAAA and no-dash fixes that sat unpublished behind a stale version earlier. Minor, not patch: this adds a command to the CLI surface. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
ThreatCrush Security Scan0 finding(s) No findings. |
ralyodio
added a commit
that referenced
this pull request
Aug 4, 2026
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.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Cuts 0.4.0 so the
recordscommand actually reaches npm.Why now
records(#12) has been onmainsince it merged, but the version was never bumped. Verified against the published tarball:So
npm i @moshcoder/moshpit-dnsinstalls a build with norecordssubcommand. This is the same failure mode as the AAAA fix and the no-dash label rule, both of which sat unpublished behind a stale version until someone noticed.Minor, not patch — this adds a command to the CLI surface.
Verified from the packed tarball
Not the source tree — the actual
.tgzthat will be published:0.4.0recordssubcommand presentmoshpit-dnsusage lists itrecordswith no name → usage linerecords foo.bar NONSENSE→unsupported record type: NONSENSE (expected CNAME, MX, or TXT)records foo.bar --json→ valid JSON against the live registry89 tests, 89 pass, 0 fail.Publishing to npm once this merges.
🤖 Generated with Claude Code