Closed Stebalien closed 3 years ago
Hey @Stebalien ,
By when do you estimate v0.14.0
will be fully tested and tagged for a release ?
We’re currently in the process of testing the code on our infrastructure. If everything goes well, we expect to cut the release end of this week / some time next week.
Re-opening till we finish the checklist.
This release happened a long time ago. Closing this issue.
unpin?
🗺 What's left for release
None
🔦 Highlights
We're happy to announce go-libp2p 0.14.0. This release introduces a few long awaited features, fixes a few bugs, and includes progress towards NAT hole punching.
Custom DNS Resolvers
You can now pass a custom DNS resolver through the
MultiaddrResolver
option. This can be used to add support for DoH, custom TLDs (e.g.,.eth
), etc.TCP Simultaneous Open
Adds initial support for TCP Simultaneous Open. If two peers open a TCP connection to each other at the same time using the same set of ports, they'll end up with a single TCP connection. Previously, go-libp2p would treat this as an error and disconnect. Now the connection succeeds. In the next libp2p release, this will be used to enable hole-punching for NAT traversal.
Improved Stream Multiplexer (Yamux) Performance
Yamux now uses variable sized receive windows to improve performance on high-latency, high-bandwidth connections.
Optimized Noise Read Throughput
The Noise security transport now buffers reads, reducing syscalls and significantly improving throughput.
Changelog
Contributors
✅ Release Checklist
go get -u ./...
to see if there are any out-of-date deps that look important. If there are, bubble them. Try to avoid directly updating indirect deps in go-libp2p's go.mod when possible.