Repository navigation
Update Rust crate async-nats to 0.52.0 - #200
Open
renovate[bot] wants to merge 1 commit into
Open
renovate[bot] wants to merge 1 commit into
renovate[bot] wants to merge 1 commit into
Conversation
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.51.0→0.52.0Release Notes
nats-io/nats.rs (async-nats)
v0.52.0Overview
This release fixes panics on line breaks in header values. A
\rinside a received header value panicked the connection task, so any client allowed to publish on a subject could stop its subscribers' connections. Upgrading is recommended.It is a minor release because
HeaderValueno longer implementsFrom<&str>andFrom<String>.Fixed
Breaking changes
HeaderValueno longer implementsFrom<&str>andFrom<String>. It implementsTryFrom<&str>,TryFrom<&String>andTryFrom<String>instead, returningParseHeaderValueErrorfor a value with\ror\n(#1673). Affected code fails to compile:headers.insert(k, HeaderValue::from(s))→headers.insert(k, s)HeaderValue::from(s),s.into()→HeaderValue::try_from(s)?to reject line breaks,HeaderValue::from_lossy(s)to replace themT: Into<HeaderValue>→T: IntoHeaderValuelet Ok(v) = HeaderValue::try_from(s)→ handleParseHeaderValueError, the error is no longerInfallibleString and integer values passed straight to
insertorappend, andstr::parse, keep working.Behaviour changes
\ror\ngets a space in place of each instead of panicking. This coversHeaderMap::insertandappend,PublishMessage::header,message_idandexpected_*, servicerespond(Err(..))and received messages. To reject such a value, convert it withHeaderValue::try_fromfirst (#1673).Stream::get_raw_message,get_last_raw_message_by_subjectand KVentrywithout direct get no longer fail on such a header value; they replace the line breaks the same way (#1673).Full Changelog: nats-io/nats.rs@async-nats/v0.51.0...async-nats/v0.52.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 was generated by Mend Renovate. View the repository job log.