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

chore(deps): update all dependencies #226

Merged
merged 1 commit into from
May 23, 2024
Merged

chore(deps): update all dependencies #226

merged 1 commit into from
May 23, 2024

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented May 16, 2024

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence Type Update
@aptre/common 0.16.4 -> 0.16.6 age adoption passing confidence devDependencies patch
actions/checkout v4.1.5 -> v4.1.6 age adoption passing confidence action patch
github.com/libp2p/go-libp2p v0.33.2 -> v0.34.0 age adoption passing confidence require minor
github.com/multiformats/go-multiaddr v0.12.3 -> v0.12.4 age adoption passing confidence require patch
github.com/nats-io/nats-server/v2 v2.10.14 -> v2.10.16 age adoption passing confidence require patch
github.com/nats-io/nats.go v1.34.1 -> v1.35.0 age adoption passing confidence require minor
github.com/quic-go/quic-go v0.43.1 -> v0.44.0 age adoption passing confidence require minor
github/codeql-action v3.25.5 -> v3.25.6 age adoption passing confidence action patch

Release Notes

aperturerobotics/common (@​aptre/common)

v0.16.6

Compare Source

v0.16.5

Compare Source

actions/checkout (actions/checkout)

v4.1.6

Compare Source

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

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

multiformats/go-multiaddr (github.com/multiformats/go-multiaddr)

v0.12.4

Compare Source

What's Changed

Improved classification of IPv6 public addresses. For details see:

Full Changelog: multiformats/go-multiaddr@v0.12.3...v0.12.4

nats-io/nats-server (github.com/nats-io/nats-server/v2)

v2.10.16

Changelog

Refer to the 2.10 Upgrade Guide for backwards compatibility notes with 2.9.x.

[!WARNING]
A possible regression may result in a server panic at startup when tav.idx files were incorrectly truncated down to zero bytes. You can work around this problem by deleting tav.idx files that are zero bytes in length before starting the server. Zero-byte files could exist as a result of a previous server crash before a successful file sync to disk occurred.

Go Version
Dependencies
  • github.com/nats-io/jwt/v2 v2.5.6 (#​5328)
  • golang.org/x/sys v0.20.0 (#​5388)
  • golang.org/x/crypto v0.23.0 (#​5413)
Added
  • Added Left and Right subject mapping operations (#​5337) Thanks to @​sspates for the contribution!
  • Add a /expvarz monitoring endpoint (#​5374)
Improved

Accounts

  • Change AccountResolver() to use read lock to prevent contention (#​5351)
  • Improve muxed routes with large subject space (#​5399)

Gateway

  • Outbound may fail to detect stale connection (#​5356) Thanks to @​wjordan for the report!

JetStream

  • Optimize stream subject matching implementation (#​5316, #​5324, #​5329, #​5342, #​5353)
  • Improve filestore LoadNextMsg performance (#​5401)
  • Prevent blocking writes on meta state filestore flush (#​5333)
  • Add logging to measure writeFullState and enforceMsgPerSubjectLimit (#​5340)
  • Do not hold filestore lock on msg block loads when looking up the first sequence for subject (#​5363)
  • Improve various stream sourcing and mirror behaviors and performance (#​5366, #​5372, #​5379, #​5389)
  • Increase the compression threshold for Raft traffic (#​5371)
  • Put a maximum idle flush time for the filestore (#​5370)
  • Updated subject state expiration (#​5377)
  • Simplify writing the full state to index.db (#​5378)
  • Added in separate last subject timestamp to track access (#​5380)
  • Check consumer leader status without locks (#​5386)
  • Various Raft improvements with limited to no state (#​5427)
  • Improved consumer with AckAll performance of first ack with large first stream sequence (#​5446)
  • Various stream catchup improvements (#​5454)

WebSocket

  • Improve generating INFO data to send to clients (#​5405)
Fixed

Config

JetStream

  • Fix potential deadlock if a panic occurs during calculateSyncRequest (#​5321)
  • Fix corner cases of subject matching (#​5318, #​5339) Thanks to @​mihaitodor for the report!
  • Prevent stepping down for old election terms (#​5314)
  • Prevent WAL truncation during catch-up until after peerstate/snapshot check (#​5330)
  • Fix various delivery counter logic (#​5338, #​5361)
  • Reset election timeout only on granted vote request (#​5315)
  • Ensure stream catchup syncs after server crash and restart (#​5362)
  • Prevent race condition for mirroring a consumer (#​5369)
  • Ensure messages are removed after consumer updates occur on interest-based streams (#​5384) Thanks to @​MauriceVanVeen for the report and contribution!
  • Cleanup messages on interest stream after consumer interest changes (#​5385) Thanks to @​tyler-eon for the report and @​MauriceVanVeen for the contribution!
  • Fix potential redelivery of acked messages during server restarts (#​5419)
  • Hold onto tombstones for previous blocks on compact (#​5426)
  • Fixes for rescaling streams with sources (#​5428)

WebSocket

  • Fix data races during shutdown (#​5398)
Chores
Complete Changes
nats-io/nats.go (github.com/nats-io/nats.go)

v1.35.0

Compare Source

Changelog

Added
  • Service API:
    • Added API to read reply subject from micro.Request. Thanks @​mcosta74 for the contribution (#​1589)
  • Core NATS:
    • Added ForceReconnect method on connection for manually triggering reconnect (#​1624)
Fixed
  • KeyValue:
    • Fixed invalid DiscardPolicy being set when creating a new KeyValue store using the jetstream package. Previously created KV instances will be auto-repaired when calling CreateKeyValue (#​1616, #​1617)
  • JetStream:
    • Fixed validation for streams, consumers and KV buckets to avoid protocol errors (#​1613)
  • Core NATS:
    • Fixed ConnectedCB not being invoked when using RetryOnFailedConnect: true and the initial nats.Connect fails (#​1619)
Improved
  • Core NATS:
    • Remove unnecessary allocations from readMIMEHeader (#​1609)
  • KeyValue:
  • Legacy JetStream:
Complete Changes
quic-go/quic-go (github.com/quic-go/quic-go)

v0.44.0

Compare Source

v0.44 contains a lot of fixes related to HTTP Datagrams, new logic to determine (and configure) the QUIC packet size, as well as a significant speedup of the various parsers.

HTTP Datagram-related Fixes

The last release introduced support for HTTP Datagrams (RFC 9297). This release resolves a number of problems we discovered in the initial implementation:

QUIC Packet Size and Path MTU Discovery

Speeding up Parsing the variable-length Integers

The QUIC varint parser was rewritten to act on byte slices instead of a bytes.Reader. This is significantly faster (https://github.com/quic-go/quic-go/pull/4475). The new parser is now used for parsing QUIC frames (https://github.com/quic-go/quic-go/pull/4484), the QUIC packet header (https://github.com/quic-go/quic-go/pull/4481), the QUIC transport parameters (https://github.com/quic-go/quic-go/pull/4483) and HTTP datagrams (https://github.com/quic-go/quic-go/pull/4478).

Other Notable Changes

quic-go needs your support!

Is your project / company relying on quic-go?
Please consider funding the project. Any support is highly appreciated!

What's Changed

New Contributors

Full Changelog: quic-go/quic-go@v0.43.0...v0.44.0

github/codeql-action (github/codeql-action)

v3.25.6

Compare Source


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.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.


  • 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 chore(deps): update all dependencies to v0.16.4 chore(deps): update all dependencies to v0.16.4 - autoclosed May 16, 2024
@renovate renovate bot closed this May 16, 2024
@renovate renovate bot deleted the renovate/all branch May 16, 2024 07:17
@renovate renovate bot changed the title chore(deps): update all dependencies to v0.16.4 - autoclosed chore(deps): update all dependencies to v0.16.4 May 16, 2024
@renovate renovate bot reopened this May 16, 2024
@renovate renovate bot restored the renovate/all branch May 16, 2024 19:52
@renovate renovate bot changed the title chore(deps): update all dependencies to v0.16.4 chore(deps): update all dependencies May 16, 2024
@renovate renovate bot force-pushed the renovate/all branch 6 times, most recently from c259942 to cc9d526 Compare May 22, 2024 12:46
@paralin paralin merged commit 1d31d4c into master May 23, 2024
4 of 5 checks passed
@paralin paralin deleted the renovate/all branch May 23, 2024 08:59
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

None yet

1 participant