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

fix(deps): update module github.com/libp2p/go-libp2p to v0.35.0 #154

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Oct 29, 2023

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
github.com/libp2p/go-libp2p v0.31.0 -> v0.35.0 age adoption passing confidence

Release Notes

libp2p/go-libp2p (github.com/libp2p/go-libp2p)

v0.35.0

Compare Source

⚠️ Breaking Changes ⚠️

  • Resource Manager: ConnLimitPerCIDR is now called ConnLimitPerSubnet. The field previously named BitMask is now called PrefixLength. Apologies for the churn, but the old names were vague and confusing.

🔦 Highlights

  • Resource Manager: Renames ConnLimitPerCIDR to ConnLimitPerSubnet
  • Resource Manager: Able to provide connection limits for specific IP address blocks.
    • By default we new allow unlimited connections from localhost. Should help fix tests that broke with the previous behavior of limiting to only 8 connections per IP address.

What's Changed

Full Changelog: libp2p/go-libp2p@v0.34.1...v0.35.0

v0.34.1

Compare Source

Refer to the v0.34.0 release notes for breaking changes in v0.34

What's Changed

Full Changelog: libp2p/go-libp2p@v0.34.0...v0.34.1

v0.34.0

Compare Source

⚠️ Breaking Changes ⚠️

  1. Transient Connections are now called Limited Connections. The prior terminology was confusing to many, and conflicted with the transient definition in the resource manager. The term actually referred to a connection that was relayed and limited in some aspect (either data or time).
  2. libp2phttp: The well-known resource for libp2p protocols has changed. See the discussion thread for context. This means that new clients will not be able to reach the well-known endpoint automatically on old servers, and new servers won't respond to the old well-known endpoint to old clients. If you do not fully control the deployment of this, you should set EnableCompatibilityWithLegacyWellKnownEndpoint in libp2phttp.Host to true to enable backwards compatibility. This is not the default behavior because libp2phttp is still experimental and things are generally permitted to break. In this case supporting backwards compatibility was simple enough and we generally don't like breaking users even on an experimental feature.
  3. ResourceManager: This probably only affects 0.01% of use cases. The resource manager is now IP aware. Meaning it will set limits for how many connections it tracks per IP address or IP Address range (CIDR subnet). Look at ‎WithLimitPeersPerCIDR‎ for how to configure it. Almost all users will not need to touch this. If you're tests are suddenly breaking, this is might be why

🔦 Highlights

WebRTC Direct
  • We've significantly improved support for webrtc-direct transport with multiple security and performance fixes.
  • Based on the experience of webrtc-direct on v0.34 we intend to make it non experimental in v0.35
Transient Connections are now called Limited Connections
  • Connections to peers over relayed or other limited connections, previously called transient are now called limited throughout the code. Limited is more descriptive of the connection's behavior and it avoids conflict with Resource Manager's Transient scope.
  • For Connections, the Transient connection state has been renamed to Limited. This is a breaking change and you'll have to replace uses of conn.Stat().Transient with conn.Stat().Limited
  • Network context functions like network.WithUseTransient are deprecated, use their limited alternatives like network.WithUseLimited.
Limited Connectedness state
  • Peers connected to the host via relayed or any other limited connection now report their connectivity state as Limited.
  • This state is also reflected in EvtPeerConnectednessChanged event. Consumers only interested in peers connected over Unlimited connections can ignore events with Limited Connectedness. NOTE: This changes the behavior of the Connected Connectedness state. Previously it included all limited connections and now it doesn't. To keep existing behavior in your code you can replace checks connectedness == network.Connected with connectedness != network.NotConnected

What's Changed

New Contributors

Full Changelog: libp2p/go-libp2p@v0.33.0...v0.34.0

v0.33.2

Compare Source

A patch update to bring in a fix from go-multiaddr

Full Changelog: libp2p/go-libp2p@v0.33.1...v0.33.2

v0.33.1

Compare Source

The release updates the quic-go dependency to v0.42.0. This update includes a mitigation for a memory exhaustion attack against QUIC's connection ID mechanism.

Full Changelog: libp2p/go-libp2p@v0.33.0...v0.33.1

v0.33.0

Compare Source

What's Changed

🔦 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
  • WebRTC streams now wait for a FIN_ACK before closing data channels. For more details see the specs PR: https://github.com/libp2p/specs/pull/582
  • Removed unused public function crypto.GenerateEKeyPair. This was used in SECIO which has been long deprecated.
  • This release drops support for go1.20.

Changelog

New Contributors

Full Changelog: libp2p/go-libp2p@v0.32.1...v0.33.0

v0.32.2

Compare Source

This release contains the quic-go fix for the Honeybadger vulnerability: https://github.com/quic-go/quic-go/releases/tag/v0.39.4

Full Changelog: libp2p/go-libp2p@v0.32.1...v0.32.2

v0.32.1

Compare Source

What's Changed

Full Changelog: libp2p/go-libp2p@v0.32.0...v0.32.1

v0.32.0

Compare Source

🔦 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 https://github.com/libp2p/go-libp2p/issues/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

New Contributors

Full Changelog: libp2p/go-libp2p@v0.31.0...v0.32.0

v0.31.1

Compare Source

This release contains the quic-go fix for the Honeybadger vulnerability: https://github.com/quic-go/quic-go/releases/tag/v0.38.2


Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR has been generated by Mend Renovate. View repository job log here.

@renovate renovate bot changed the title Update module github.com/libp2p/go-libp2p to v0.32.0 fix(deps): update module github.com/libp2p/go-libp2p to v0.32.0 Oct 30, 2023
@renovate renovate bot force-pushed the renovate/github.com-libp2p-go-libp2p-0.x branch from 2bde7d6 to 763f700 Compare October 30, 2023 18:15
@renovate renovate bot changed the title fix(deps): update module github.com/libp2p/go-libp2p to v0.32.0 fix(deps): update module github.com/libp2p/go-libp2p to v0.32.1 Nov 7, 2023
@renovate renovate bot force-pushed the renovate/github.com-libp2p-go-libp2p-0.x branch from 763f700 to 7da9f40 Compare November 7, 2023 11:27
@renovate renovate bot force-pushed the renovate/github.com-libp2p-go-libp2p-0.x branch from 7da9f40 to 711729f Compare December 13, 2023 06:32
@renovate renovate bot changed the title fix(deps): update module github.com/libp2p/go-libp2p to v0.32.1 fix(deps): update module github.com/libp2p/go-libp2p to v0.32.2 Dec 13, 2023
@renovate renovate bot force-pushed the renovate/github.com-libp2p-go-libp2p-0.x branch from 711729f to 8ff77de Compare February 21, 2024 18:59
@renovate renovate bot changed the title fix(deps): update module github.com/libp2p/go-libp2p to v0.32.2 fix(deps): update module github.com/libp2p/go-libp2p to v0.33.0 Feb 21, 2024
@renovate renovate bot force-pushed the renovate/github.com-libp2p-go-libp2p-0.x branch from 8ff77de to 7ff4177 Compare March 18, 2024 23:43
@renovate renovate bot changed the title fix(deps): update module github.com/libp2p/go-libp2p to v0.33.0 fix(deps): update module github.com/libp2p/go-libp2p to v0.33.1 Mar 18, 2024
@renovate renovate bot force-pushed the renovate/github.com-libp2p-go-libp2p-0.x branch from 7ff4177 to 9c05d51 Compare March 29, 2024 00:34
@renovate renovate bot changed the title fix(deps): update module github.com/libp2p/go-libp2p to v0.33.1 fix(deps): update module github.com/libp2p/go-libp2p to v0.33.2 Mar 29, 2024
@renovate renovate bot force-pushed the renovate/github.com-libp2p-go-libp2p-0.x branch 4 times, most recently from b00f137 to d72e8a1 Compare April 18, 2024 23:03
@renovate renovate bot force-pushed the renovate/github.com-libp2p-go-libp2p-0.x branch 2 times, most recently from 7f05c1a to 98226f1 Compare April 21, 2024 17:19
@renovate renovate bot force-pushed the renovate/github.com-libp2p-go-libp2p-0.x branch from 98226f1 to fb05554 Compare April 21, 2024 21:33
@github-actions github-actions bot enabled auto-merge (squash) April 21, 2024 21:34
@renovate renovate bot force-pushed the renovate/github.com-libp2p-go-libp2p-0.x branch from fb05554 to 1c46eb6 Compare May 1, 2024 18:32
@renovate renovate bot force-pushed the renovate/github.com-libp2p-go-libp2p-0.x branch from 1c46eb6 to 0a78ede Compare May 20, 2024 21:23
@renovate renovate bot changed the title fix(deps): update module github.com/libp2p/go-libp2p to v0.33.2 fix(deps): update module github.com/libp2p/go-libp2p to v0.34.0 May 20, 2024
@renovate renovate bot force-pushed the renovate/github.com-libp2p-go-libp2p-0.x branch 2 times, most recently from 277f19c to fee1570 Compare May 23, 2024 19:26
@renovate renovate bot changed the title fix(deps): update module github.com/libp2p/go-libp2p to v0.34.0 fix(deps): update module github.com/libp2p/go-libp2p to v0.34.1 May 23, 2024
@renovate renovate bot force-pushed the renovate/github.com-libp2p-go-libp2p-0.x branch from fee1570 to ed60e64 Compare May 24, 2024 21:32
@renovate renovate bot changed the title fix(deps): update module github.com/libp2p/go-libp2p to v0.34.1 fix(deps): update module github.com/libp2p/go-libp2p to v0.35.0 May 24, 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

Successfully merging this pull request may close these issues.

None yet

0 participants