chore(release): v3.8.6 - #55
Merged
Merged
Conversation
Ships the Tor fix (#54): with Tor on, only loopback bypassed the SOCKS proxy, so the registry lookup in front of every Moshpit navigation went out over Tor. A cold circuit does not answer inside the lookup budget, so resolution fell back to clearnet — correct for a registry that is down, wrong for one that was merely slow, and indistinguishable from the name not existing. The pit's own hosts now bypass Tor alongside loopback, computed from the configured bases so a self-hosted pit is covered too. The lookup budget goes 4s -> 8s in both the policy module and its extension port. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
vu1nz Security Review0 finding(s) in PR #? No security issues found. |
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.
Version bump only —
node scripts/set-version.mjs 3.8.6, 25 files, no code changes.What this release ships
#54 — the Tor fix. With Tor on, only loopback bypassed the SOCKS proxy, so the registry lookup that gates every Moshpit navigation went out over Tor. A cold circuit doesn't answer inside the lookup budget → resolution fell back to clearnet. Correct for a registry that's down, wrong for one that's merely slow, and indistinguishable from the name not existing.
The pit's own hosts now bypass Tor alongside loopback, computed from the configured bases so a self-hosted pit is covered too. Lookup budget 4s → 8s in both the policy module and its extension port.
After merge
Pushing the
v3.8.6tag triggersrelease.yml, which creates a draft GitHub Release and uploads per-platform artifacts. I have not pushed the tag — that publishes binaries, so it's yours to trigger unless you'd rather I did it.git tag v3.8.6 && git push origin v3.8.6🤖 Generated with Claude Code