chore(deps): @moshcoder/moshpit-dns 0.2.1 -> 0.2.2 — unblocks main - #198
Merged
Conversation
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>
vu1nz Security Review0 finding(s) in PR #? No security issues found. |
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
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.
mainhas 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-dnscarried it, sodns-driftfailed exactly as designed:Why publishing alone didn't fix it
@moshcoder/moshpit-dns@0.2.2is published and carries the rule — and CI still failed, because it runs:The lockfile pins the exact version, so the
^0.2.1range inpackage.jsonnever applied. The lockfile update is the actual fix.Verified
test/dns-drift.test.mjs— 10 tests, 10 pass against 0.2.2, includingthe same hostnames are Moshpit nameswhich was the failing one.🤖 Generated with Claude Code