go-libp2p v0.19.0

[marten-seemann]

🗺 What's left for release

Circuit v2 relay discovery

• use first kad bucket to discover circuit v2 nodes discover relay v2s using AutoRelay #1351
  • implement relay v2 discovery #1368
  • helper function to fill the peerChan with DHT nodes

QUIC

• update quic-go to a version that builds with Go 1.18 (make sure to include improve the error thrown when building with an unsupported Go version quic-go/quic-go#3364)

Resource Manager

• release and update go-libp2p-resource-manager
• update to yamux version including correctly release memory when the connection is closed go-yamux#81 (which fixes Peer with no streams but maxed out memory #1374)

🛠 BREAKING CHANGES

The mplex stream multiplexer was removed from the default list of stream multiplexers. If you still need to support both yamux and mplex, you can manually enable it using the following libp2p.Option:

libp2p.ChainOptions(
	libp2p.Muxer("/yamux/1.0.0", yamux.DefaultTransport),
	libp2p.Muxer("/mplex/6.7.0", mplex.DefaultTransport),
)

🔦 Highlights

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.
  • Make sure local tests are passing.
• Stage 1 - Upstream Testing
  • Create testing branches in lotus & go-ipfs with the new go-libp2p release and run CI/tests. Many upstream projects are tested in CI, but lotus & go-ipfs are not.
    • filecoin-project/lotus
    • ipfs/go-ipfs
  • (someday) Run upstream testground tests. Unfortunately, this is too time consuming at the moment.
    • (someday) Run bitswap testground tests.
    • (someday) Run DHT testground tests.
• Stage 2 - Infrastructure Testing
  • How: Using the testing branches created above, work with the infrastructure team to deploy the new libp2p versions to our infrastructure.
  • Where:
    • A go-ipfs gateway.
      • Deploy
      • Analyze
        • Look at pprof profile dumps, especially CPU profiles and heap allocation profiles, noting any significant changes.
    • A go-ipfs bootstrapper.
      • Deploy
      • Analyze
        • Look at pprof profile dumps, especially CPU profiles and heap allocation profiles, noting any significant changes.
        • Check peers (e.g., ipfs swarm peers) to make sure we're connecting to peers on all transports.
        • Check advertised addresses and protocols (e.g., ipfs id) to make sure they're sane.
• Stage 3 - Release
  • Tag the release on master.
  • 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 4 - Update Upstream
  • Update the examples to the final release
  • Update the upstream testing branches to the final release and create PRs.
    • filecoin-project/lotus
    • ipfs/go-bitswap
    • ipfs/go-ipfs
    • libp2p/go-libp2p-kad-dht
    • libp2p/go-libp2p-pubsub
    • libp2p/go-libp2p-daemon
• Make required changes to the release process.

[marten-seemann]

v0.19.0 has shipped: https://github.com/libp2p/go-libp2p/releases/tag/v0.19.0!