chore(deps): @moshcoder/moshpit-resolve 0.1.1 -> 0.1.2 — unblocks main - #67
Merged
Conversation
vu1nz Security Review0 finding(s) in PR #? No security issues found. |
|
Review the following changes in direct dependencies. Learn more about Socket for GitHub.
|
|
All alerts resolved. Learn more about Socket for GitHub. This PR previously contained dependency changes with security issues that have been resolved, removed, or ignored. |
Unblocks main, red since #66 merged. #66 dropped dashes from both local copies of the name grammar while the published package still allowed them, so moshpit-drift.test.js failed on blue.lazy-loaded — and not merely on parsing: the two disagreed on where a tab goes, 'park' against the package and 'clearnet' against the new rule. That is the anchor earning its place. 0.1.2 carries the rule. The lockfile is the part that matters: CI installs frozen, so the ^0.1.1 range never picked the new version up on its own. Scoped to the one package deliberately. Doing this with `pnpm update --latest` first pulled the whole tree forward — TypeScript 5.9.3 to 7.0.2, eslint 9 to 10, babel 7 to 8, 3509 lines of lockfile — and broke Lint with "typescript-eslint does not support TS 7.0". This touches 11 lines. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
ralyodio
force-pushed
the
bump-moshpit-resolve
branch
from
August 1, 2026 13:42
ecbc1b1 to
fa675ae
Compare
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.
mainhas been red since #66 merged. This clears it.Why it was red
#66 dropped dashes from both local copies of the name grammar while the published package still allowed them, so
moshpit-drift.test.jsfailed — and not merely on parsing:The two disagreed on where a tab goes. That's the anchor earning its place.
Why publishing alone didn't fix it
@moshcoder/moshpit-resolve@0.1.2is published and carries the rule, but CI installs frozen from the lockfile — so the^0.1.1range never applied and it kept installing 0.1.1. The lockfile update is the actual fix.Verified
76 tests pass across
moshpit-drift.test.js,moshpit.test.jsandmoshpit-resolve.test.ts— includingparses hostnames the same way, which was the failing one.🤖 Generated with Claude Code