This repository has been archived by the owner on Dec 22, 2023. It is now read-only.
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:
4.4.5
->4.4.8
0.3.28
->0.3.29
0.24.6
->0.24.7
0.12.0
->0.12.1
2.6.1
->2.7.1
0.30.0
->0.31.0
0.11.20
->0.11.22
0.31.7
->0.31.8
1.0.188
->1.0.192
1.0.107
->1.0.108
3.3.0
->3.4.0
0.9.25
->0.9.27
1.0.48
->1.0.50
1.32.0
->1.34.0
0.1.37
->0.1.40
1.4.1
->1.5.0
Release Notes
clap-rs/clap (clap)
v4.4.8
Compare Source
Features
Command::flatten_help
to allowgit stash -h
like help for subcommandsv4.4.7
Compare Source
Performance
v4.4.6
Compare Source
Internal
anstream
rust-lang/futures-rs (futures)
v0.3.29
Compare Source
TryStreamExt::try_ready_chunks
(#2757)TryStreamExt::{try_all,try_any}
(#2783)UnboundedSender::{len,is_empty}
(#2750)Sync
impl ofFuturesUnordered
(#2788)image-rs/image (image)
v0.24.7
Compare Source
New features:
{ImageBuffer, DynamicImage}::write_with_encoder
to simplify writingimages with custom settings.
GenericImageView
sBug fixes:
moka-rs/moka (moka)
v0.12.1
Compare Source
Fixed
future::Cache
that occurred whenget_with()
,entry().or_insert_with()
, and similar methods were used ([#329][gh-issue-0329]).v0.12.0
. Versions prior tov0.12.0
do nothave this bug.
Changed
ValueInitializer
([#331][gh-pull-0331], by[@Swatinem][gh-Swatinem]).
mongodb/mongo-rust-driver (mongodb)
v2.7.1
Compare Source
The MongoDB Rust driver team is pleased to announce the v2.7.1 release of the
mongodb
crate, now available for download from crates.io.This release fixes a bug that caused a memory leak in various circumstances.
Full Release Notes
Bugfixes
v2.7.0
Compare Source
The MongoDB Rust driver team is pleased to announce the v2.7.0 release of the
mongodb
crate, now available for download from crates.io.The Rust driver documentation is now hosted at https://www.mongodb.com/docs/drivers/rust/current/. This documentation includes detailed content about features, runnable examples, troubleshooting resources, and more.
Highlighted Changes
Serialization Behavior Change
When serializing values via serde, the serializer can indicate whether or not the target format is human-readable, allowing types to change behavior based on that. The Rust driver had inadvertently been serializing values given to
find_one_and_replace
andreplace_one
as human-readible when all other methods serialize as non-human-readible; this bug is fixed in 2.7.0, with those methods also serializing as non-human-readible.However, it is potentially possible (if unlikely) that user code may rely on this bug. If your code does rely on human-readable serialization, you can specify that via the new
human_readable_serialization
field inCollectionOptions
.run_cursor_command
The Rust driver provides the
run_command
method as a way for users to directly send bson commands to the server; this is particularly useful when the driver does not yet have support for a newly-added server command. However, using this with commands that return a cursor requires re-implementing the logic for cursor iteration, which can be tedious and error-prone. The newrun_cursor_command
method avoids those problems, directly returning aCursor
using the same iteration logic as other methods.SDAM Logging
The Rust driver will now log SDAM events when using the
tracing-unstable
feature.Client Management
The
Client
type now provides three additional ways to shape behavior to fit your workload:ClientOptions.max_connecting
lets you specify how many "in flight" connections can be established in parallel. This was previously fixed at 2 and defaults to the same value.Client::warm_connection_pool
will create new connections to bring the connection pool up tomin_pool_size
, which can provide more predictable performance in some circumstances.Client::shutdown
will cleanly stop background tasks and wait for outstanding handles to be dropped. This is particularly useful when using event handlers that reference external resources, as otherwise those handlers may be invoked in a background task even after theClient
has been dropped.Included Changes
Below are a selected list of changes with user impact; for a full list of changes see this GitHub query.
New Features
Improvements
Bugfixes
tafia/quick-xml (quick-xml)
v0.31.0
Compare Source
MSRV bumped to 1.56! Crate now uses Rust 2021 edition.
Enum representation was changed (it was buggy anyway) to ensure compatibility with
serde >= 1.0.181
New Features
xml
andxmlns
) to their appropriate URIs.Also, enforce namespace constraints related to these well-known namespaces.
ElementWriter
operations.Bug Fixes
xs:list
s from empty tags (<tag/>
or
<tag></tag>
). Previously anDeError::UnexpectedEof")
was returned in that caseunit structs, unit variants).
<int>123<something-else/></int>
is no longer validcontent. Previously all data after
123
up to closing tag would be silently skipped.simpleType
s (for example, attributes) intoOption
fields: now they are always deserialized asSome("")
.Misc Changes
Error
variant --Error::InvalidPrefixBind
.arbitrary
dependency -- we're actuallycompatible with version 1.0.0 and up.
ElementWriter::write_inner_content
(and newly added
ElementWriter::write_inner_content_async
of course).xs:list
s when some elements serialized to an empty string.seanmonstar/reqwest (reqwest)
v0.11.22
Compare Source
trust-dns
is enabled.v0.11.21
Compare Source
ClientBuilder::tls_info(bool)
, which will puttls::TlsInfo
into the response extensions.getsentry/sentry-rust (sentry)
v0.31.8
Compare Source
Various fixes & improvements
serde-rs/serde (serde)
v1.0.192
Compare Source
v1.0.191
Compare Source
v1.0.190
Compare Source
v1.0.189
Compare Source
serde-rs/json (serde_json)
v1.0.108
Compare Source
jonasbb/serde_with (serde_with)
v3.4.0
: serde_with v3.4.0Compare Source
Lower minimum required serde version to 1.0.152 (#653)
Thanks to @banool for submitting the PR.
This allows people that have a problem with 1.0.153 to still use
serde_with
.Add support for
core::ops::Bound
(#655)Thanks to @qsantos for submitting the PR.
dtolnay/serde-yaml (serde_yaml)
v0.9.27
Compare Source
v0.9.26
Compare Source
.nan
is deserialized as a positive NaN (#392, #393)dtolnay/thiserror (thiserror)
v1.0.50
Compare Source
v1.0.49
Compare Source
::core
in generated code (#255, thanks @mina86)tokio-rs/tokio (tokio)
v1.34.0
: Tokio v1.34.0Compare Source
Fixed
clear_readiness
after io driver shutdown (#6067)take
(#6080)broadcast::channel
link (#6100)Changed
::core
qualified imports instead of::std
insidetokio::test
macro (#5973)Added
fs::read_dir
to includeaix
(#6075)mpsc::Receiver::recv_many
(#6010)v1.33.0
: Tokio v1.33.0Compare Source
1.33.0 (October 9, 2023)
Fixed
Interest::add
with#[must_use]
(#6037)watch::Receiver::wait_for
(#6021)spawn_local
source location (#5984)Changed
watch
(#6018)Added
tokio::fs::File
(#5958)Interest::remove
method (#5906)DuplexStream
(#5985)?Sized
bound to{MutexGuard,OwnedMutexGuard}::map
(#5997)watch::Receiver::mark_unseen
(#5962, #6014, #6017)watch::Sender::new
(#5998)OnceCell::from_value
(#5903)Removed
stats
feature (#5952)Documented
Child::wait
is cancel safe (#5977)Semaphore
(#5939, #5956, #5978, #6031, #6032, #6050)broadcast
capacity is a lower bound (#6042)const_new
is not instrumented (#6002)mpsc::Sender::send
(#5947)watch
channel (#5954)Unstable
tokio-rs/tracing (tracing)
v0.1.40
: tracing 0.1.40Compare Source
This release fixes a potential stack use-after-free in the
Instrument::into_inner
method. Only uses of this method are affected by thisbug.
Fixed
mem::ManuallyDrop
instead ofmem::forget
inInstrument::into_inner
(#2765)
Thanks to @cramertj and @manishearth for finding and fixing this issue!
v0.1.39
: tracing 0.1.39Compare Source
This release adds several additional features to the
tracing
macros. Inaddition, it updates the
tracing-core
dependency to v0.1.32 andthe
tracing-attributes
dependency to v0.1.27.Added
ValueSet
s of any length (#2508)Changed
tracing-attributes
: updated to 0.1.27tracing-core
: updated to 0.1.32Fixed
(#2621, #2757)
clippy::let_with_type_underscore
] in macro-generatedcode ([#2609])
unknown_lints
in macro-generated code (#2626)#[instrument]
when the"log"
feature is enabled (#2599)
Documented
axum-insights
to relevant crates. (#2713)clippy-tracing
to related crates (#2628)tracing-cloudwatch
to related crates (#2667)tracing-etw
repo (#2602)v0.1.38
: tracing 0.1.38Compare Source
This
tracing
release changes theDrop
implementation forInstrumented
Future
s so that the attachedSpan
is entered when dropping theFuture
. Thismeans that events emitted by the
Future
'sDrop
implementation will now berecorded within its
Span
. It also adds#[inline]
hints to methods called inthe
event!
macro's expansion, for an improvement in both binary size andperformance.
Additionally, this release updates the
tracing-attributes
dependency tov0.1.24, which updates the [
syn
][syn] dependency to v2.x.x.tracing-attributes
v0.1.24 also includes improvements to the#[instrument]
macro; see the
tracing-attributes
0.1.24 release notes fordetails.
Added
Instrumented
futures will now enter the attachedSpan
in theirDrop
implementation, allowing events emitted when dropping the future to occur
within the span (#2562)
#[inline]
attributes for methods called by theevent!
macros, makinggenerated code smaller (#2555)
level
argument to#[instrument(err)]
and#[instrument(ret)]
to override the level ofthe generated return value event (#2335)
#[instrument]
is added to aconst fn
(#2418)
Changed
tracing-attributes
: updated to 0.1.24cfg-if
dependency (#2553)syn
][syn] dependency to 2.0 (#2516)Fixed
clippy::unreachable
warnings in#[instrument]
-generated code (#2356)syn
dependency (#2530)Documented
#[instrument(err)]
(#2433)#[instrument]
(#2350)Thanks to @nitnelave, @jsgf, @Abhicodes-crypto, @LukeMathWalker, @andrewpollack,
@quad, @klensy, @davidpdrsn, @dbidwell94, @ldm0, @NobodyXu, @ilsv, and @daxpedda
for contributing to this release!
uuid-rs/uuid (uuid)
v1.5.0
Compare Source
What's Changed
bytemuck
support by @John-Toohey in https://github.com/uuid-rs/uuid/pull/711New Contributors
Full Changelog: uuid-rs/uuid@1.4.1...1.5.0
Configuration
📅 Schedule: Branch creation - "after 11am on friday" in timezone Europe/Amsterdam, 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.
This PR has been generated by Mend Renovate. View repository job log here.