Repository navigation
chore(deps): update rust crate async-nats to 0.51 - #531
Open
dreadnode-renovate-bot[bot] wants to merge 1 commit into
Open
dreadnode-renovate-bot[bot] wants to merge 1 commit into
dreadnode-renovate-bot[bot] wants to merge 1 commit into
Conversation
| datasource | package | from | to | | ---------- | ---------- | ------ | ------ | | crate | async-nats | 0.50.0 | 0.51.0 |
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #531 +/- ##
=======================================
Coverage 80.50% 80.50%
=======================================
Files 460 460
Lines 161612 161612
=======================================
+ Hits 130103 130104 +1
+ Misses 31509 31508 -1 🚀 New features to boost your workflow:
|
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
0.50→0.51Release Notes
nats-io/nats.rs (async-nats)
v0.51.0Overview
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
fipsthis moves the bundled AWS-LC-FIPS module from 3.x to 4.x.MessagesErrorKind::RequestLimitExceededandOrderedErrorKind::RequestLimitExceeded(#1631),BatchErrorKind::PinnedClient(#1652). Exhaustivematches on these enums need a new arm.server_2_11:priority_timeoutonconsumer::Configandpull::Config,priority_groupsonconsumer::Info(#1653). Struct literals without..Default::default()need updating (Infohas noDefault).ConnectErrorsources are now tokio-websockets 0.13 types, so downcasts to the 0.10 type stop matching (#1656).Behaviour changes
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 connectionrequest_timeout. When it is not set, API requests keep usingrequest_timeout(#1636).fetch(),batch()andsequence()returnBatchErrorKind::PinnedClienton aPriorityPolicy::PinnedClientconsumer. Usestream()ormessages()instead (#1652).409 Exceeded MaxRequest*now ends withMessagesErrorKind::RequestLimitExceededinstead of re-pulling forever. Batch and expiry defaults the user did not set are capped at the consumer's limits, andOrderedConfig::max_batchnow reaches the server (#1631).{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 soput(), uses direct get when the stream allows it, so lookups of missing objects no longer count as JetStream API errors (#1632).ws://andwss://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)
🚦 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.
This PR has been generated by Mend Renovate CLI.