p2ptunnel icon indicating copy to clipboard operation
p2ptunnel copied to clipboard

Published 20 hours ago • verified publisher icon chenjia404

Update module github.com/libp2p/go-libp2p to v0.35.1

Open renovate[bot] opened this issue 9 months ago • 1 comments

Mend Renovate

This PR contains the following updates:

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

Release Notes

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

v0.35.1

Compare Source

What's Changed

  • identify: Don't filter addr if remote is neither public nor private (#​2820)
  • identify: fix bug in observed address handling (#​2825)
  • identify: add test for observed address handling (#​2828)
  • libp2phttp: workaround for ResponseWriter's CloseNotifier (#​2821)
  • circuitv2: improve voucher validation (#​2826)
  • webrtc: fix ufrag prefix for dialing (#​2832)

Full Changelog: https://github.com/libp2p/go-libp2p/compare/v0.35.0...v0.35.1

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: https://github.com/libp2p/go-libp2p/compare/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: https://github.com/libp2p/go-libp2p/compare/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: https://github.com/libp2p/go-libp2p/compare/v0.33.0...v0.34.0

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[bot] avatar May 20 '24 17:05 renovate[bot]