chore(deps): update crates #5425
Merged
Conversation
This file contains 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
![renovate[bot]](https://avatars.githubusercontent.com/in/2740?s=60&v=4){kind=small}
renovate
bot
force-pushed
the
renovate/crates
branch
6 times, most recently
from
6228c6e
to
300cf13
Compare
Boshen
force-pushed
the
renovate/crates
branch
from
e6f6319
to
5dc2f45
Compare
Boshen
approved these changes
Jan 24, 2024
Edited/Blocked NotificationRenovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR. You can manually request rebase by checking the rebase/retry box above. ⚠ Warning: custom changes will be lost. |
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:
1.0.71->1.0.790.1.10->0.1.121.0.4->1.0.50.7.1->0.8.00.1.71->0.1.772.0.4->2.1.00.15.7->0.15.80.3.6->0.5.15.5.0->5.5.32.4.0->2.5.00.11.2->0.13.01.0.11->1.0.160.3.28->0.3.300.3.28->0.3.304.3.7->4.5.00.8.3->0.9.00.17.5->0.17.71.30.0->1.34.00.10.5->0.12.00.22.1->0.23.0=2.13.3->=2.14.4=2.0.1->=2.1.0=2.13.0->=2.14.6=2.2.3->=2.3.01.18.0->1.19.01.2.1->1.2.20.6.3->0.6.40.4.6->0.4.101.0.76->1.0.781.7.0->1.8.11.9.1->1.10.30.7.4->0.8.20.6.0->0.7.10.7.42->0.7.431.6.0->1.6.10.8.12->0.8.161.0.100->1.0.1110.10.7->0.10.82.2.1->2.4.01.4.2->1.5.00.2.11->0.2.121.29.1->1.35.10.1.10->0.1.112.4.0->2.5.02.1.2->2.1.30.102.0->0.119.00.8.6->0.8.8Release Notes
dtolnay/anyhow (anyhow)
v1.0.79Compare Source
v1.0.78Compare Source
v1.0.77Compare Source
anyhow::Error::backtraceavailable on stable Rust compilers 1.65+ (#293, thanks @LukasKalbertodt)v1.0.76Compare Source
unsafe_op_in_unsafe_fnlint (#329)google/argh (argh)
v0.1.12Compare Source
v0.1.11Compare Source
dcchut/async-recursion (async-recursion)
v1.0.5Compare Source
What's Changed
Full Changelog: dcchut/async-recursion@v1.0.4...v1.0.5
rmanoka/async-scoped (async-scoped)
v0.8.0Compare Source
dtolnay/async-trait (async-trait)
v0.1.76Compare Source
v0.1.75Compare Source
v0.1.74Compare Source
v0.1.73Compare Source
v0.1.72Compare Source
mackwic/colored (colored)
v2.1.0Compare Source
1.70.console-rs/console (console)
v0.15.8Compare Source
Enhancements
wasm32-unknown-emscriptentarget. (#179)read_line_initial_textnow retains the initial prefix. (#190)Bugfixes
Termto get terminal size (#186)read_lineandread_line_initial_text's behavior. (#181)msys_tty_on. (#183)bheisler/criterion.rs (criterion)
v0.5.1Compare Source
Fixed
v0.5.0Compare Source
Changed
html_reportsfeatureFixed
--quick) no longer outputs 1ms for measured times over 5 secondsv0.4.0Compare Source
Removed
Criterion::can_plotfunction has been removed.Criterion::bench_function_over_inputsfunction has been removed.Criterion::bench_functionsfunction has been removed.Criterion::benchfunction has been removed.Changed
rayonandplottersare optional (and default) dependencies.--warm-up-time,--measurement-timeand--profile-time.Added
--discard-baselineflag for discarding rather than saving benchmark results.--quietflag for printing just a single line per benchmark.Throughput::BytesDecimaloption for measuring throughput in bytes but printing them usingdecimal units like kilobytes instead of binary units like kibibytes.
Fixed
bench_with_input, the input parameter will now be passed throughblack_boxbeforepassing it to the benchmark.
ia0/data-encoding (data-encoding)
v2.5.0Compare Source
colin-kiegel/rust-derive-builder (derive_builder)
v0.13.0Compare Source
build_fn(error(validation_error = <bool>))to disable generation ofValidationErrorwithin the builder's error so thatalloc::stringis avoided.allocfor controlling linking ofalloccrate duringno_std. This way users can useno_stdwithout providing aglobal_allocator.strip_optionfromsetterfortry_setter. Using these settings together previously caused a compile error #284v0.12.0Compare Source
defaultis used withfield(type = "...")rather than silently ignoringdefault#269crate = "..."to support re-export scenarios #274dtolnay/dyn-clone (dyn-clone)
v1.0.16Compare Source
v1.0.15Compare Source
v1.0.14Compare Source
v1.0.13Compare Source
v1.0.12Compare Source
rust-lang/futures-rs (futures)
v0.3.30Compare Source
{BiLock,SplitStream,SplitSink,ReadHalf,WriteHalf}::is_pair_of(#2797)FuturesUnordered::clear(#2809)AsyncBufReadExt::fill_buf(#2801, #2812)v0.3.29Compare Source
TryStreamExt::try_ready_chunks(#2757)TryStreamExt::{try_all,try_any}(#2783)UnboundedSender::{len,is_empty}(#2750)Syncimpl ofFuturesUnordered(#2788)sunng87/handlebars-rust (handlebars)
v4.5.0Compare Source
v4.4.0Compare Source
kyren/hashlink (hashlink)
v0.9.0Compare Source
reserveandtry_reservein caseswhere a rehash is needed. Previously would panic, adds the proper bounds on
reserve methods to do a rehash (previously bounds were missing, and reserve
would result in panics). (Thank you @cuviper)
v0.8.4#![no_std].console-rs/indicatif (indicatif)
v0.17.7Compare Source
v0.17.6Compare Source
mitsuhiko/insta (insta)
v1.34.0Compare Source
cargo-instainto a workspace. (#410)--manifest-pathwith regards to virtual workspaces. (#409)v1.33.0Compare Source
--all-targetsparameter support tocargo insta test. (#408)v1.32.0Compare Source
--profileparameter support tocargo insta test.rust-itertools/itertools (itertools)
v0.12.0Compare Source
Breaking
take_while_inclusiveconsume iterator by value (#709)Clonebound toUnique(#777)Added
Itertools::try_len(#723)sort_unstable(#796)GroupMap::fold_with(#778, #785)PeekNth::{peek_mut, peek_nth_mut}(#716)PeekNth::{next_if, next_if_eq}(#734)(Option<A>,Option<B>)toEitherOrBoth(#713)Either<A, B>toEitherOrBoth<A, B>(#715)ExactSizeIteratorforTuples(#761)ExactSizeIteratorfor(Circular)TupleWindows(#752)EitherOrBoth<T>a shorthand forEitherOrBoth<T, T>(#719)Changed
#[must_use]annotations on iterator adaptors (#794)Combinationslazy (#795)Intersperse(With)lazy (#797)Permutationslazy (#793)Productlazy (#800)TupleWindowslazy (#602)Combinations::{count, size_hint}(#729)CombinationsWithReplacement::{count, size_hint}(#737)Powerset::fold(#765)Powerset::count(#735)TupleCombinations::{count, size_hint}(#763)TupleCombinations::fold(#775)WhileSome::fold(#780)WithPosition::fold(#772)ZipLongest::fold(#774){min, max}_set*operations requireallocfeature, instead ofstd(#760)tree_fold1(#787)permutations(#724)multiunzip(#770)Notable Internal Changes
Permutations(#739, #748, #790)Merge/MergeBy/MergeJoinByimplementations (#736)Permutations::size_hint(#739)rustfmtin CI (#751)cargo hackto check MSRV (#754)v0.11.0Compare Source
Breaking
Itertools::merge_join_byalso accept functions returning bool (#704)PeekingNexttransitively over mutable references (#643)with_positionto yield(Position, Item)instead ofPosition<Item>(#699)Added
Itertools::take_while_inclusive(#616)PeekingNextforPeekingTakeWhile(#644)EitherOrBoth::{just_left, just_right, into_left, into_right, as_deref, as_deref_mut, left_or_insert, right_or_insert, left_or_insert_with, right_or_insert_with, insert_left, insert_right, insert_both}(#629)CloneforCircularTupleWindows(#686)CloneforChunks(#683)Itertools::process_results(#680)Changed
Cellinstead ofRefCellinFormatandFormatWith(#608)Itertools::max_set_by_key(#692)Cargo.toml(#672)equalwithIterator::eq(#591)dprint/jsonc-parser (jsonc-parser)
v0.23.0Compare Source
napi-rs/napi-rs (napi)
v2.14.4Compare Source
What's Changed
Full Changelog: https://github.com/napi-rs/napi-rs/compare/[email protected]@2.14.4
v2.14.3Compare Source
What's Changed
Full Changelog: https://github.com/napi-rs/napi-rs/compare/[@​napi-rs/cli](https://togithub.com/napi-rs/cli)[@​3](https://togithub.com/3)[email protected]
v2.14.2Compare Source
What's Changed
Full Changelog: https://github.com/napi-rs/napi-rs/compare/[email protected]@2.14.2
v2.14.1Compare Source
What's Changed
Full Changelog: https://github.com/napi-rs/napi-rs/compare/[email protected]@2.14.1
v2.14.0Compare Source
What's Changed
New Contributors
Full Changelog: https://github.com/napi-rs/napi-rs/compare/[email protected]@2.14.0
petgraph/petgraph (petgraph)
v0.6.4Compare Source
==========================
indexmapto 2.0.0 (#568_)#544_).. _
#544: https://github.com/petgraph/petgraph/pull/544.. _
#568: https://github.com/petgraph/petgraph/pull/568dtolnay/proc-macro2 (proc-macro2)
v1.0.78Compare Source
v1.0.77Compare Source
rayon-rs/rayon (rayon)
v1.8.1Compare Source
"web_spin_lock"crate feature makes mutexes spin on the mainbrowser thread in WebAssembly, rather than suffer an error about forbidden
atomics.waitif they were to block in that context. Thanks @RReverser!v1.8.0Compare Source
rustcis now 1.63.ThreadPoolBuilder::use_current_threadto use the builder thread aspart of the new thread pool. That thread does not run the pool's main loop,
but it may participate in work-stealing if it yields to rayon in some way.
FromParallelIterator<T>forBox<[T]>,Rc<[T]>, andArc<[T]>, as well asFromParallelIterator<Box<str>>andParallelExtend<Box<str>>forString.ThreadPoolBuilder::build_scopednow usesstd::thread::scope.std::thread::available_parallelisminstead of thenum_cpuscrate.rust-lang/regex (regex)
v1.10.3Compare Source
===================
This is a new patch release that fixes the feature configuration of optional
dependencies, and fixes an unsound use of bounds check elision.
Bug fixes:
Set
default-features=falsefor thememchrandaho-corasickdependencies.Fix unsound bounds check elision.
v1.10.2Compare Source
===================
This is a new patch release that fixes a search regression where incorrect
matches could be reported.
Bug fixes:
Revert broadening of reverse suffix literal optimization introduced in 1.10.1.
v1.10.1Compare Source
===================
This is a new patch release with a minor increase in the number of valid
patterns and a broadening of some literal optimizations.
New features:
Loosen ASCII-compatible rules such that regexes like
(?-u:☃)are now allowed.Performance improvements:
Broader the reverse suffix optimization to apply in more cases.
v1.10.0Compare Source
===================
This is a new minor release of
regexthat adds support for start and endword boundary assertions. That is,
\<and\>. The minimum supported Rustversion has also been raised to 1.65, which was released about one year ago.
The new word boundary assertions are:
\<or\b{start}: a Unicode start-of-word boundary (\W|\Aon the left,\won the right).\>or\b{end}: a Unicode end-of-word boundary (\won the left,\W|\zon the right)).
\b{start-half}: half of a Unicode start-of-word boundary (\W|\Aon theleft).
\b{end-half}: half of a Unicode end-of-word boundary (\W|\zon theright).
The
\<and\>are GNU extensions to POSIX regexes. They have been addedto the
regexcrate because they enjoy somewhat broad support in other regexengines as well (for example, vim). The
\b{start}and\b{end}assertionsare aliases for
\<and\>, respectively.The
\b{start-half}and\b{end-half}assertions are not found in anyother regex engine (although regex engines with general look-around support
can certainly express them). They were added principally to support the
implementation of word matching in grep programs, where one generally wants to
be a bit more flexible in what is considered a word boundary.
New features:
Add support for
\<and\>word boundary assertions.DFAs now have a
start_statemethod that doesn't use anInput.Performance improvements:
Unicode character class operations have been optimized in
regex-syntax.Make patterns containing lots of literal characters use less memory.
Bug fixes:
Fix a bug that could result in incorrect match spans when using a Unicode word
boundary and searching non-ASCII strings.
Fix panics that can occur in
Ast->Hirtranslation (not reachable fromregexcrate).
Remove guarantees in the API that connect the
uflag with a specific HIRrepresentation.
regex-automatabreaking change release:This release includes a
regex-automata 0.4.0breaking change release, whichwas necessary in order to support the new word boundary assertions. For
example, the
Lookenum has new variants and theLookSettype now usesu32instead of
u16to represent a bitset of look-around assertions. These areoverall very minor changes, and most users of
regex-automatashould be ableto move to
0.4from0.3without any changes at all.regex-syntaxbreaking change release:This release also includes a
regex-syntax 0.8.0breaking change release,which, like
regex-automata, was necessary in order to support the new wordboundary assertions. This release also includes some changes to the
Asttype to reduce heap usage in some cases. If you are using the
Asttypedirectly, your code may require some minor modifications. Otherwise, users of
regex-syntax 0.7should be able to migrate to0.8without any code changes.regex-literelease:The
regex-lite 0.1.1release contains support for the new word boundaryassertions. There are no breaking changes.
v1.9.6Compare Source
==================
This is a patch release that fixes a panic that can occur when the default
regex size limit is increased to a large number.
Fix a bug where computing the maximum haystack length for the bounded
backtracker could result underflow and thus provoke a panic later in a search
due to a broken invariant.
v1.9.5Compare Source
==================
This is a patch release that hopefully mostly fixes a performance bug that
occurs when sharing a regex across multiple threads.
Issue #934
explains this in more detail. It is also noted in the crate
documentation.
The bug can appear when sharing a regex across multiple threads simultaneously,
as might be the case when using a regex from a
OnceLock,lazy_staticorsimilar primitive. Usually high contention only results when using many threads
to execute searches on small haystacks.
One can avoid the contention problem entirely through one of two methods.
The first is to use lower level APIs from
regex-automatathat require passingstate explicitly, such as
meta::Regex::search_with.The second is to clone a regex and send it to other threads explicitly. This
will not use any additional memory usage compared to sharing the regex. The
only downside of this approach is that it may be less convenient, for example,
it won't work with things like
OnceLockorlazy_staticoronce_cell.With that said, as of this release, the contention performance problems have
been greatly reduced. This was achieved by changing the free-list so that it
was sharded across threads, and that ensuring each sharded mutex occupies a
single cache line to mitigate false sharing. So while contention may still
impact performance in some cases, it should be a lot better now.
Because of the changes to how the free-list works, please report any issues you
find with this release. That not only includes search time regressions but also
significant regressions in memory usage. Reporting improvements is also welcome
as well! If possible, provide a reproduction.
Bug fixes:
Fix a performance bug where high contention on a single regex led to massive
slow downs.
v1.9.4Compare Source
==================
This is a patch release that fixes a bug where
RegexSet::is_match(..)couldincorrectly return false (even when
RegexSet::matches(..).matched_any()returns true).
Bug fixes:
Fix a bug where a prefilter was incorrectly configured for a
RegexSet.v1.9.3Compare Source
==================
This is a patch release that fixes a bug where some searches could result in
incorrect match offsets being reported. It is difficult to characterize the
types of regexes susceptible to this bug. They generally involve patterns
that contain no prefix or suffix literals, but have an inner literal along with
a regex prefix that can conditionally match.
Bug fixes:
Fix a bug with the reverse inner literal optimization reporting incorrect match
offsets.
v1.9.2Compare Source
==================
This is a patch release that fixes another memory usage regression. This
particular regression occurred only when using a
RegexSet. In some cases,much more heap memory (by one or two orders of magnitude) was allocated than in
versions prior to 1.9.0.
Bug fixes:
Fix a memory usage regression when using a
RegexSet.rust-lang/regex (regex-syntax)
v0.8.2Compare Source
v0.8.1Compare Source
v0.8.0Compare Source
v0.7.5Compare Source
ridiculousfish/regress (regress)
v0.7.1Compare Source
v0.7.0Compare Source
Version 0.7.0 of regress, REGex in Rust with EmcaScript Syntax.
rkyv/rkyv (rkyv)
v0.7.43: 0.7.43Compare Source
This bugfix release closes a number of issues:
with_capacityconstructor forSharedSerializeMap,SharedDeserializeMap,DefaultValidator, andSharedValidator(#432)tinyvec/allocfeature cfg and docs (#428)EntryAPI to avoid double hash lookups (#426)HashMap/HashSetdata on deserialize (#427)VecDeque(#414)smol_strsupport (#411)OptionandResult(#413)Bytessuport (#408)Thanks to everyone who helped contribute to this release: @gz, @monoid, @b8591340, @alvra, @blp, @al8n, @cholcombe973, and @FallingSnow.
cessen/ropey (ropey)
v1.6.1Compare Source
GREsau/schemars (schemars)
v0.8.16Compare Source
Fixed:
JsonSchemav0.8.15Compare Source
Added:
JsonSchemaforBigDecimalfrombigdecimal0.4 (https://github.com/GREsau/schemars/pull/237)v0.8.14Compare Source
Added:
#[schemars(inner(...)]attribute to specify schema for array items (https://github.com/GREsau/schemars/pull/234)Changed:
JsonSchematrait:schema_id(), which is similar toschema_name(), but does not have to be human-readable, and defaults to the type name including module path. This allows schemars to differentiate between types with the same name in different modules/crates (https://github.com/GREsau/schemars/issues/62 / https://github.com/GREsau/schemars/pull/247)Fixed:
rust_decimal::Decimalandbigdecimal::BigDecimalnow match how those types are serialized by default, i.e. as numeric strings (https://github.com/GREsau/schemars/pull/248)v0.8.13Compare Source
Added:
JsonSchemaforsemver::Version(https://github.com/GREsau/schemars/pull/195 / https://github.com/GREsau/schemars/pull/238)JsonSchemafor types from indexmap v2 (https://github.com/GREsau/schemars/pull/226 / https://github.com/GREsau/schemars/pull/240)JsonSchemaforserde_json::value::RawValue([https://github.com/Cover serde_json RawValue type by schemars GREsau/schemars#183](https://togithub.com/GREsConfiguration
📅 Schedule: Branch creation - "on wednesday" (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.