go-libp2p v0.28

[marten-seemann]

🗺 What's left for release

Smart dialing:

• swarm: implement smart dialing logic #2260
• identify: filter received addresses based on the node's remote address #2300
• identify: don't save signed peer records #2325
• swarm: make smart-dialing opt in #2340

WebSocket:

• websocket: switch back to the gorilla library #2280

Metrics:

• holepunch: add metrics #2246

Misc:

• quic: prioritise listen connections for reuse #2262
• swarm: duplicate tracking in dial worker loop doesn't work #2283
• fix: sendWindowUpdate respects deadlines go-yamux#105
• race condition writing the stream header when calling Write and Close quic-go/webtransport-go#77
• update deps, use contexts on UPnP functions go-nat#29
• consider reverting peerstore context changes #2327

🔦 Highlights

< top highlights for this release notes >

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. https://discuss.libp2p.io/t/go-libp2p-v0-28-0-released/1967
• Stage 2 - Update Upstream
  • Update the examples to the final release examples: update go-libp2p to v0.28.0 #2366
  • Add go-libp2p 0.28.0 to test-plans test-plans#191
  • 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 update go-libp2p to v0.29.0 ipfs/kubo#10001
• Make required changes to the release process.

[BigLep]

If webrtc is a maybe, will it be happening in 0.29, and will 0.29 be released in June?

[p-shahi]

If webrtc is a maybe, will it be happening in 0.29, and will 0.29 be released in June?

Removed it from maybe as it will not be ready for 0.28.0

We plan to deliver WebRTC browser-to-server in June and include it in a release (likely 0.29.0)

[BigLep]

@sukunrt @marten-seemann : I was thinking about the smart dialing changelog entry for the release and left some thoughts here: #2260 (comment)

[marten-seemann]

@p-shahi, can you announce the release on Discourse and then close this issue please?