release: v0.6.1 - #100
Merged
Merged
Conversation
Assembles the pending changelog fragment and points the README's download table at the release being cut. One fix since v0.6.0: a gateway endpoint written as a hostname is now resolved over a socket bound the same way the lane will be, so a host whose transparent proxy redirects port 53 into this client can still bring the client's own datapath up. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01MHr1RSawjHAuUBJwK63vxE
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.
Patch release over v0.6.0. One user-visible fix.
A gateway endpoint written as a hostname is now resolved over a bound socket (#99).
--local-addressbinds the sockets this client creates, but a dialer'sLocalAddrandControlnever reach the lookup that turns the endpoint name into the address it connects to, and the QUIC path went throughnet.ResolveUDPAddroutright. On a host whose transparent proxy redirects port 53 into this client, that unbound lookup cannot be answered — the name has to resolve before the datapath exists, and the datapath has to exist before the name resolves. Observed live: 25,365no such hostfailures in 67 minutes while the lane sockets themselves were going out direct correctly the whole time.Endpoints written as literal addresses were never affected and still take a path with no lookup in it.
Contents
CHANGELOG.mdassembled from the pending fragment viascripts/changelog.py release --version v0.6.1.Release sequence after this merges
release.ymlrequires a successful release-candidate run bound to the exact commit, and excludes pull-request runs, so: merge → main CI on the merge commit →release-candidatefor that SHA → tagv0.6.1.🤖 Generated with Claude Code
https://claude.ai/code/session_01MHr1RSawjHAuUBJwK63vxE