chore(deps): lock file maintenance rust dependencies #11864
Merged
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:
2.3.2
->2.3.3
2.0.0
->2.3.3
4.3.8
->4.3.10
2.5.0
->2.6.0
0.10.0
->0.10.1
0.3
->0.4
0.3.3
->0.4.0
1.0.28
->1.0.29
2.0.22
->2.0.23
8.2.1
->8.2.3
0.7.0
->0.8.0
🔧 This Pull Request updates lock files to use the latest dependency versions.
Release Notes
bitflags/bitflags (bitflags)
v2.3.3
Compare Source
Changes to
-=
The
-=
operator was incorrectly changed to truncate bits that didn't correspond to valid flags in2.3.0
. This hasbeen fixed up so it once again behaves the same as
-
anddifference
.Changes to
!
The
!
operator previously calledSelf::from_bits_truncate
, which would truncate any bits that only partiallyoverlapped with a valid flag. It will now use
bits & Self::all().bits()
, so any bits that overlap any bitsspecified by any flag will be respected. This is unlikely to have any practical implications, but enables defining
a flag like
const ALL = !0
as a way to signal that any bit pattern is a known set of flags.Changes to formatting
Zero-valued flags will never be printed. You'll either get
0x0
for empty flags using debug formatting, or theset of flags with zero-valued flags omitted for others.
Composite flags will no longer be redundantly printed if there are extra bits to print at the end that don't correspond
to a valid flag.
What's Changed
Full Changelog: bitflags/bitflags@2.3.2...2.3.3
clap-rs/clap (clap)
v4.3.10
Compare Source
Performance
v4.3.9
Compare Source
Fixes
Command::ignore_errors
no longer masks help/versionxfix/enum-map (enum-map)
v2.6.0
Compare Source
New features
EnumMap::as_array
is now usable in const contexts.Other changes
This crate now follows "N minus two" MSRV policy. This means that
it supports the current Rust release, as well as the two before
that.
Upgraded syn to 2.0.0.
jeromefroe/lru-rs (lru)
v0.10.1
Compare Source
try_get_or_insert
method.rust-num/num-derive (num-derive)
v0.4.0
Compare Source
v0.3.3
Compare Source
NumOps
work withno_std
-- thanks @jedrzejboczar!v0.3.2
Compare Source
#[inline]
to all derived functions -- thanks @Amanieu!v0.3.1
Compare Source
num_traits
proc_macro helper for explicit import - thanks @jean-airoldie!dtolnay/quote (quote)
v1.0.29
Compare Source
proc_macro_span_shrink
-related build error when built with-Zminimal-versions
dtolnay/syn (syn)
v2.0.23
Compare Source
where [(); { T::COUNT }]:
in non-"full" mode (#1478)rustyhorde/vergen (vergen)
v8.2.3
Compare Source
gix
to 0.48.0build.rs
location.NOTE - Using a local offset will likely cause failures on Unix systems due to the
Soundness
check that thetime
crate performs. I don't want to introduce unsoundness support tovergen
.Configuration
📅 Schedule: Branch creation - "before 4am on Monday" (UTC), 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.