Skip to content

chore(deps): @moshcoder/moshpit-dns 0.2.1 -> 0.2.2 — unblocks main - #198

Merged
ralyodio merged 1 commit into
mainfrom
bump-moshpit-dns
Aug 1, 2026
Merged

chore(deps): @moshcoder/moshpit-dns 0.2.1 -> 0.2.2 — unblocks main#198
ralyodio merged 1 commit into
mainfrom
bump-moshpit-dns

Conversation

@ralyodio

@ralyodio ralyodio commented Aug 1, 2026

Copy link
Copy Markdown
Contributor

main has been red since #193 merged. This clears it.

Why it was red

The dash rule landed in moshcode (#193) and in the drift guard covering it (#194) before @moshcoder/moshpit-dns carried it, so dns-drift failed exactly as designed:

blue.lazy-loaded
  + actual:   null                                  ← vendored
  - expected: { label: 'blue', tld: 'lazy-loaded' } ← published 0.2.1

Why publishing alone didn't fix it

@moshcoder/moshpit-dns@0.2.2 is published and carries the rule — and CI still failed, because it runs:

pnpm install --frozen-lockfile
+ @moshcoder/moshpit-dns 0.2.1

The lockfile pins the exact version, so the ^0.2.1 range in package.json never applied. The lockfile update is the actual fix.

Verified

test/dns-drift.test.mjs — 10 tests, 10 pass against 0.2.2, including the same hostnames are Moshpit names which was the failing one.

🤖 Generated with Claude Code

Unblocks main, which has been red since #193 merged.

The dash rule landed here (#193) and in the drift guard covering it
(#194) before the package carried it, so dns-drift correctly failed on
blue.lazy-loaded: vendored null, published { blue, lazy-loaded }. That
is the guard working.

0.2.2 carries the rule. The lockfile is the part that matters — CI runs
`pnpm install --frozen-lockfile`, so the ^0.2.1 range in package.json
never picked the new version up on its own; it installed 0.2.1 and kept
failing after the publish.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
@github-actions

github-actions Bot commented Aug 1, 2026

Copy link
Copy Markdown

vu1nz Security Review

0 finding(s) in PR #?

No security issues found.

@ralyodio ralyodio mentioned this pull request Aug 1, 2026
@ralyodio
ralyodio merged commit 8cabe9c into main Aug 1, 2026
3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant