Skip to content

chore(deps): bump async-nats from 0.50.0 to 0.51.0 - #335

Open
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/cargo/async-nats-0.51.0
Open

dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/cargo/async-nats-0.51.0

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Nov 2, 2026

Copy link
Copy Markdown
Contributor

Bumps async-nats from 0.50.0 to 0.51.0.

Release notes

Sourced from async-nats's releases.

Release async-nats/v0.51.0

Overview

This release adds pinned client support for pull consumers and fixes a number of panics and hangs across JetStream, KV, Object Store and Service APIs. JetStream API requests are now bounded by the JetStream context timeout when it is set.

It is a minor release because it adds variants to error kind enums, adds public fields to consumer types and raises the MSRV to 1.89.

Added

Fixed

Changed

Breaking changes

  • MSRV is now Rust 1.89, required by tokio-websockets 0.13 (#1656).
  • The minimum aws-lc-rs version is now 1.18, as older releases allow an aws-lc-fips-sys that does not build with CMake 4. Under fips this moves the bundled AWS-LC-FIPS module from 3.x to 4.x.
  • New error kind variants: MessagesErrorKind::RequestLimitExceeded and OrderedErrorKind::RequestLimitExceeded (#1631), BatchErrorKind::PinnedClient (#1652). Exhaustive matches on these enums need a new arm.
  • New public fields behind server_2_11: priority_timeout on consumer::Config and pull::Config, priority_groups on consumer::Info (#1653). Struct literals without ..Default::default() need updating (Info has no Default).
  • Websocket errors behind ConnectError sources are now tokio-websockets 0.13 types, so downcasts to the 0.10 type stop matching (#1656).

Behaviour changes

  • When the JetStream context timeout (ContextBuilder::timeout, Context::set_timeout) is set, it is now the only bound for every JetStream API request, whether it is lower or higher than the connection request_timeout. When it is not set, API requests keep using request_timeout (#1636).
  • fetch(), batch() and sequence() return BatchErrorKind::PinnedClient on a PriorityPolicy::PinnedClient consumer. Use stream() or messages() instead (#1652).
  • A pull consumer stream rejected with 409 Exceeded MaxRequest* now ends with MessagesErrorKind::RequestLimitExceeded instead of re-pulling forever. Batch and expiry defaults the user did not set are capped at the consumer's limits, and OrderedConfig::max_batch now reaches the server (#1631).
  • A recreated ordered consumer is named {name}_{n}, using the configured name or the name the server gave the first consumer. The previous consumer is now deleted on recreation, unnamed ones included (#1626).
  • ObjectStore::info(), and so put(), uses direct get when the stream allows it, so lookups of missing objects no longer count as JetStream API errors (#1632).
  • For ws:// and wss:// on the default port, the Host header no longer includes the port. webpki-roots is no longer a dependency (#1656).

New Contributors

... (truncated)

Commits
  • e22f657 Release async-nats/v0.51.0
  • 4e70300 Redact secrets in ConnectInfo Debug output
  • 1815112 Fix service error Display swapping code and status
  • de95c75 Name the pull id helper for the pull it reads
  • e10693c Split the pinned tests back into one behaviour each
  • 37a030f Cover the 423 pin reset, get_last and the standby in pinned tests
  • b61f5f5 Point the PinnedClient docs at stream().group(..).messages()
  • b3252c7 Store the pin only when it changes
  • 7df7694 Clarify why the pin is read from the last header
  • 0f50af0 Support the pinned client priority policy in pull streams
  • Additional commits viewable in compare view

Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

Bumps [async-nats](https://github.com/nats-io/nats.rs) from 0.50.0 to 0.51.0.
- [Release notes](https://github.com/nats-io/nats.rs/releases)
- [Commits](nats-io/nats.rs@async-nats/v0.50.0...async-nats/v0.51.0)

---
updated-dependencies:
- dependency-name: async-nats
  dependency-version: 0.51.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <[email protected]>
@dependabot dependabot Bot added chore maintenance, dependency updates, code cleanup dependencies dependency updates and version bumps labels Nov 2, 2026
@coderabbitai

coderabbitai Bot commented Nov 2, 2026

Copy link
Copy Markdown

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

Run configuration
  • Source mode: Auto
  • Repository: Unavailable
  • Branch: Unavailable
  • File: No configuration file from this repository applied
  • Commit: Unavailable
  • Layers: defaults
  • Review profile: CHILL
  • Plan: Advanced
  • Run ID: 6001ce07-6370-46d1-9911-937c741af32d

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

  • Trigger review
  • Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

chore maintenance, dependency updates, code cleanup dependencies dependency updates and version bumps

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants