Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

go-libp2p v0.33 #2623

Closed
6 of 19 tasks
sukunrt opened this issue Oct 27, 2023 · 1 comment
Closed
6 of 19 tasks

go-libp2p v0.33 #2623

sukunrt opened this issue Oct 27, 2023 · 1 comment

Comments

@sukunrt
Copy link
Member

sukunrt commented Oct 27, 2023

🗺 What's left for release

ETA: Week of Feb 19

WebRTC:

Misc:

QUIC:

Optional

🔦 Highlights

TLS encryption for TCP by default

For TCP Connections, the default encryption scheme has been changed from noise to TLS for better performance. See PR for details.

Note: When making TCP connections to nodes that only support noise this will add 1 extra round trip for connection establishment. If you wish to avoid this and keep noise the default, configure your node to prefer noise over TLS like

	node, err := libp2p.New(
        ... other options
		libp2p.Security("/noise", noise.New),
		libp2p.Security("/tls/1.0.0", libp2ptls.New),
	)

Misc

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
  • Make required changes to the release process.
@marten-seemann marten-seemann pinned this issue Oct 27, 2023
@p-shahi
Copy link
Member

p-shahi commented Feb 8, 2024

Should we update to the latest 0.41.0 version of quic-go https://github.com/quic-go/quic-go/releases/tag/v0.41.0 instead of a dot release of 0.40?

@p-shahi p-shahi closed this as completed Mar 7, 2024
@p-shahi p-shahi unpinned this issue Mar 19, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants