go-libp2p v0.32

[marten-seemann]

Release date: Oct 23 2023

🗺 What's left for release

WebRTC:

• WebRTC Direct transport implementation #2337

Smart Dialing:

• Implement Happy Eyeballs for TCP #2394

Misc:

• Connect should wait for an acceptable connection #1603
• switch away from github.com/golang/mock #2528
• httplibp2p: cannot mount a protocol at the root #2545
• swarm: fix recursive resolving of DNS multiaddrs #2564
• swarm: wait for transient connections to upgrade for NewStream #2542
• tcp: fix build on riscv64 #2590
• update quic-go to v0.39.1, set a static resumption token generator key #2572
• swarm: cleanup stream handler goroutine #2610

🔦 Highlights

WebRTC Direct

This release adds support for WebRTC Direct. WebRTC Direct allows browser nodes to connect to go-libp2p directly, without any configuration (e.g. TLS certificates) needed on the go-libp2p side. This is useful for browser nodes that aren’t able to use Webtransport. Note that WebRTC Direct cannot be used to connect a browser node to a go-libp2p node behind a NAT / firewall. This requires using WebRTC, which is currently being worked on #2009.

Happy Eyeballs for TCP

In the last couple of releases we’ve shipped Smart Dialing and Black hole Detection. This release continues our effort to improve the dial prioritisation logic to avoid spurious dials with the introduction of Happy Eyeballs for TCP addresses. As recommended by RFC 8305, when dialing a peer’s TCP addresses, we now dial the IPv6 address first and only dial the peer’s IPv4 address if we have not established the IPv6 TCP connection within 250ms.

Misc

• host.NewStream now waits for a hole punched connection to be available rather than returning network.ErrTransientConn immediately.
• go-libp2p now works on riscv64 architectures.

Changelog

< changelog generated by scripts/mkreleaselog >

✅ Release Checklist

• Stage 0 - Finishing Touches
  • Go through relevant libp2p repos looking for unreleased changes that should make it into the release. If you find any, cut releases.
  • Run 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.
• Stage 1 - Release
  • Publish the release through the GitHub UI, adding the release notes. Some users rely on this to receive notifications of new releases.
  • Announce the release on the discuss.libp2p.io.
• Stage 2 - Update Upstream
  • Update the examples to the final release
  • Update the upstream dependencies to the final release and create PRs.
    • filecoin-project/lotus
    • go-libp2p-kad-dht
    • go-libp2p-pubsub (In case of breaking changes.)
    • ipfs/kubo
  • Add new release to interop tester in test-plans
• Make required changes to the release process.

[master255]

Waiting for a memory leak fix to use this in my project :)

[master255]

@marten-seemann Can you tell me which version is best to take now for release on production?

[marten-seemann]

Stop tagging me. JUST STOP IT!

[master255]

What's the problem? It's a simple appeal to a specific person. Or do you not want to answer me anymore?