Skip to content

chore(deps): update rust crate async-nats to 0.51 - #531

Open
dreadnode-renovate-bot[bot] wants to merge 1 commit into
mainfrom
renovate/async-nats-0.x
Open

dreadnode-renovate-bot[bot] wants to merge 1 commit into
mainfrom
renovate/async-nats-0.x

Conversation

@dreadnode-renovate-bot

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

Package Type Update Change
async-nats workspace.dependencies minor 0.50 → 0.51

Release Notes

nats-io/nats.rs (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

Full Changelog: nats-io/nats.rs@async-nats/v0.50.0...async-nats/v0.51.0


Configuration

📅 Schedule: (UTC)

  • 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 CLI.

| datasource | package    | from   | to     |
| ---------- | ---------- | ------ | ------ |
| crate      | async-nats | 0.50.0 | 0.51.0 |
@codecov

codecov Bot commented Oct 28, 2026

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 80.50%. Comparing base (ff50382) to head (13e6af3).
⚠️ Report is 6 commits behind head on main.

Additional details and impacted files

Impacted file tree graph

@@           Coverage Diff           @@
##             main     #531   +/-   ##
=======================================
  Coverage   80.50%   80.50%           
=======================================
  Files         460      460           
  Lines      161612   161612           
=======================================
+ Hits       130103   130104    +1     
+ Misses      31509    31508    -1     

see 1 file with indirect coverage changes

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

This branch has not been deployed

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

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants