-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix(deps): update all non-major dependencies #55
Open
renovate
wants to merge
1
commit into
main
Choose a base branch
from
renovate/all-minor-patch
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+6
−6
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
added
the
Meta: Dependencies
Issues and PRs related to dependencies.
label
Feb 26, 2023
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
from
March 2, 2023 02:36
9c97274
to
5ecd0e5
Compare
renovate
bot
changed the title
fix(deps): update rust crate actix-web to 4.3.1
fix(deps): update all non-major dependencies
Mar 2, 2023
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
7 times, most recently
from
March 10, 2023 10:18
21b9ce5
to
94bf7c6
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
5 times, most recently
from
March 18, 2023 02:01
51abf37
to
7d6d71d
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
4 times, most recently
from
March 24, 2023 20:11
70183a2
to
9c9efe2
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
5 times, most recently
from
March 30, 2023 18:15
6692721
to
48d7326
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
3 times, most recently
from
April 11, 2023 07:37
15d5615
to
2046b50
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
2 times, most recently
from
April 13, 2023 09:24
96d4f51
to
e0024f6
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
4 times, most recently
from
September 16, 2024 10:18
7395dcf
to
e8c4e32
Compare
|
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
from
September 16, 2024 19:07
e8c4e32
to
7c459e9
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
4 times, most recently
from
September 30, 2024 19:50
b768804
to
34307f7
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
3 times, most recently
from
October 9, 2024 21:27
ddb13b1
to
bbf0180
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
10 times, most recently
from
October 22, 2024 19:02
7e79d03
to
931ce20
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
4 times, most recently
from
November 4, 2024 14:32
1b62ff7
to
d4e7f74
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
from
November 6, 2024 07:18
d4e7f74
to
4b8e855
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
from
November 7, 2024 13:18
4b8e855
to
346701e
Compare
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:
4.3.0
->4.9.0
1.0.69
->1.0.93
0.1.64
->0.1.83
0.21.0
->0.22.0
0.1.0
->0.1.3
0.99.17
->0.99.18
v4.0.0
->v4.2.1
v2.1.0
->v2.2.0
v2.4.1
->v2.10.0
0.19.3
->0.21.0
0.3.26
->0.3.31
0.2.9
->0.2.12
1.17.1
->1.20.2
1.6.1
->1.10.0
0.22.3
->0.27.0
0.4.1
->0.10.0
0.11.14
->0.12.0
0.32.3
->0.35.0
1.0.152
->1.0.214
1.0.93
->1.0.132
0.2.3
->0.2.4
0.2.3
->0.2.4
1.25.0
->1.41.1
0.1.37
->0.1.40
0.7.2
->0.7.14
0.3.16
->0.3.18
2.3.1
->2.5.3
0.9.4
->0.9.5
Release Notes
dtolnay/anyhow (anyhow)
v1.0.93
Compare Source
thiserror
v2v1.0.92
Compare Source
&raw const
and&raw mut
syntax insideensure!
(#390)v1.0.91
Compare Source
v1.0.90
Compare Source
v1.0.89
Compare Source
UnwindSafe
andRefUnwindSafe
impl consistently available between versions of Rust newer and older than 1.72 (#386)v1.0.88
Compare Source
v1.0.87
Compare Source
Error::new
andError::chain
, in no-std mode on Rust 1.81+ (#383)v1.0.86
Compare Source
ensure!
with non-literal after minus sign (#373)v1.0.85
Compare Source
ensure!
macro's rules to unblock some rustc pretty-printer improvements (#368, #371)v1.0.84
Compare Source
ensure!
through aNot
impl for a type that is notbool
(#367)v1.0.83
Compare Source
v1.0.82
Compare Source
v1.0.81
Compare Source
v1.0.80
Compare Source
v1.0.79
Compare Source
v1.0.78
Compare Source
v1.0.77
Compare Source
anyhow::Error::backtrace
available on stable Rust compilers 1.65+ (#293, thanks @LukasKalbertodt)v1.0.76
Compare Source
unsafe_op_in_unsafe_fn
lint (#329)v1.0.75
Compare Source
v1.0.74
Compare Source
v1.0.73
Compare Source
v1.0.72
Compare Source
v1.0.71
Compare Source
v1.0.70
Compare Source
dtolnay/async-trait (async-trait)
v0.1.83
Compare Source
v0.1.82
Compare Source
v0.1.81
Compare Source
syn
dependency (#272, thanks @klensy)v0.1.80
Compare Source
!
(#265, thanks @de-vri-es)v0.1.79
Compare Source
v0.1.78
Compare Source
v0.1.77
Compare Source
v0.1.76
Compare Source
v0.1.75
Compare Source
v0.1.74
Compare Source
v0.1.73
Compare Source
v0.1.72
Compare Source
v0.1.71
Compare Source
v0.1.70
Compare Source
v0.1.69
Compare Source
v0.1.68
Compare Source
v0.1.67
Compare Source
v0.1.66
Compare Source
v0.1.65
Compare Source
marshallpierce/rust-base64 (base64)
v0.22.1
Compare Source
alphabet::BIN_HEX
.v0.22.0
Compare Source
DecodeSliceError::OutputSliceTooSmall
is now conservative rather than precise. That is, the error will only occur if the decoded output cannot fit, meaning thatEngine::decode_slice
can now be used with exactly-sized output slices. As part of this,Engine::internal_decode
now returnsDecodeSliceError
instead ofDecodeError
, but that is not expected to affect any external callers.DecodeError::InvalidLength
now refers specifically to the number of valid symbols being invalid (i.e.len % 4 == 1
), rather than just the number of input bytes. This avoids confusing scenarios when based on interpretation you could make a case for eitherInvalidLength
orInvalidByte
being appropriate.v0.21.7
Compare Source
Alphabet::as_str()
v0.21.6
Compare Source
v0.21.5
Compare Source
Debug
andClone
impls for the general purpose Enginev0.21.4
Compare Source
encoded_len
const
, allowing the creation of arrays sized to encode compile-time-known data lengthsv0.21.3
Compare Source
source
instead ofcause
on Error typesv0.21.2
Compare Source
v0.21.1
Compare Source
DecoderReader
no longer sometimes erroneously ignorespadding #226
Breaking changes
Engine.internal_decode
return type changedmplanchard/cuid-rust (cuid2)
v0.1.3
Compare Source
Upcoming
top-level
cuid()
,slug()
, andis_cuid()
functions in favor oftheir version-specific counterparts (see below).
crate and publish it independently, like I have done for
cuid2
.The top-level
cuid
crate will then pull in the sub-crates dependingon features, making it easy to just pull the CUID version you need.
Added
cuid
library to disambiguateCUID versions:
cuid::cuid1()
: generate a v1 CUID, replacement for deprecatedcuid()
cuid::cuid1_slug()
: generate a v1 CUID slug, replacement for deprecatedslug()
cuid::is_cuid1()
- check whether a string looks like it could be a v1 CUID,replacement for deprecated
is_cuid()
cuid::is_cuid1_slug()
- check whether a string looks like it could be a v1 CUIDslug, replacement for deprecated
is_cuid()
cuid::cuid2_slug()
- generate a v2 CUID of length 10cuid::is_cuid2_slug()
- check whether a string looks like could be a v2 CUIDslug
cuid::Cuid2Constructor
- expose the v2 CUID constructor interfacecuid2
for parity with v1 functions:cuid2::slug()
- generate a v2 CUID of length 10cuid2::is_slug()
- check whether a string looks like could be a v2 CUIDslug
wasm32-unknown-unknown
and
wasm32-wasi
targets. I intend to add Javascript bindings and publishnpm packages in an upcoming update.
fingerprint algorithm, we instead use a v4 UUID. This does mean the
fingerprint will not be consistent on a host over time, which slightly
diverges from the behavior of CUIDs on other targets. Please open an
issue if this is a problem for you.
Changed
library was marked as insecure and deprecated by its creators, but this
was merely due to their personal stance that any k-sortable IDs are
insecure and should not be used. This library's author does not share
the same view. New functions have been provided to better disambiguate
creating v1 vs v2 IDs, and functions that do not explicitly specify
a version are still marked as deprecated.
rather than always starting at 0. This ensures that commandline-generated
CUIDs do not lose entropy relative to library-generated CUIDs due to
always having the same counter value.
cuid2::is_cuid()
/cuid::is_cuid2()
function has been improved andnow rejects more strings that are invalid CUIDs (contribution by @stormshield-kg)
cuid2
binary now supports an optional--length|-l
argument, whichenables specifying the length of the generated CUID (contribution by @der-fruhling)
Removed
#[cfg(nightly)]
blocks. Criterion benchmarksare the important ones, and those remain.
v0.1.2
Compare Source
Changed
implementation,
specifically:
to building a hash
a random choice from a static array of prime numbers
v0.1.1
Compare Source
Added
cuid-util
crateis_cuid2
function andis_cuid
aliasChanged
cuid
with the logic incuid-util
,yielding a solid performance improvement for CUID generation (10-20%)
#[inline]
annotations for main cuid2 functionsFixed
94d4cd0
: Removed unusedbigint
dependencyJelteF/derive_more (derive_more)
v0.99.18
Compare Source
docker/build-push-action (docker/build-push-action)
v4.2.1
Compare Source
Full Changelog: docker/build-push-action@v4.2.0...v4.2.1
v4.2.0
Compare Source
Full Changelog: docker/build-push-action@v4.1.1...v4.2.0
v4.1.1
Compare Source
Full Changelog: docker/build-push-action@v4.1.0...v4.1.1
v4.1.0
Compare Source
Full Changelog: docker/build-push-action@v4.0.0...v4.1.0
docker/login-action (docker/login-action)
v2.2.0
Compare Source
Full Changelog: docker/login-action@v2.1.0...v2.2.0
docker/setup-buildx-action (docker/setup-buildx-action)
v2.10.0
Compare Source
What's Changed
Full Changelog: docker/setup-buildx-action@v2.9.1...v2.10.0
v2.9.1
Compare Source
Full Changelog: docker/setup-buildx-action@v2.9.0...v2.9.1
v2.9.0
Compare Source
Full Changelog: docker/setup-buildx-action@v2.8.0...v2.9.0
v2.8.0
Compare Source
Full Changelog: docker/setup-buildx-action@v2.7.0...v2.8.0
v2.7.0
Compare Source
Full Changelog: docker/setup-buildx-action@v2.6.0...v2.7.0
v2.6.0
Compare Source
Full Changelog: docker/setup-buildx-action@v2.5.0...v2.6.0
v2.5.0
Compare Source
cleanup
input to remove builder and temp files by @crazy-max in https://github.com/docker/setup-buildx-action/pull/213docker
driver by @crazy-max in https://github.com/docker/setup-buildx-action/pull/218docker
driver by @crazy-max in https://github.com/docker/setup-buildx-action/pull/209Full Changelog: docker/setup-buildx-action@v2.4.1...v2.5.0
jonhoo/fantoccini (fantoccini)
v0.21.2
Compare Source
v0.21.1
Compare Source
v0.21.0
Compare Source
v0.20.0
Compare Source
rust-lang/futures-rs (futures-util)
v0.3.31
Compare Source
FuturesUnordered
when dropped future panics (#2886)task::waker_ref
(#2830)This is a breaking change but allowed because it is soundness bug fix.
AsyncBufRead::read_line
andAsyncBufReadExt::lines
(#2884)select!
/select_biased!
(#2832)This is technically a breaking change as it will now reject a very odd undocumented syntax that was previously accidentally accepted.
Waker::will_wake
change (#2865)stream::Iter::{get_ref,get_mut,into_inner}
(#2875)future::AlwaysReady
(#2825)io::{BufReader,BufWriter}
(#2848)v0.3.30
Compare Source
Note: This release of futures-util has been yanked due to a bug fixed in 0.3.31 and a compile failure with futures-task 0.3.31 and later.
{BiLock,SplitStream,SplitSink,ReadHalf,WriteHalf}::is_pair_of
(#2797)FuturesUnordered::clear
(#2809)AsyncBufReadExt::fill_buf
(#2801, #2812)v0.3.29
Compare Source
Note: This release of futures-util has been yanked due to a bug fixed in 0.3.31 and a compile failure with futures-task 0.3.31 and later.
TryStreamExt::try_ready_chunks
(#2757)TryStreamExt::{try_all,try_any}
(#2783)UnboundedSender::{len,is_empty}
(#2750)Sync
impl ofFuturesUnordered
(#2788)v0.3.28
Compare Source
Note: This release of futures-util has been yanked due to a bug fixed in 0.3.31 and a compile failure with futures-task 0.3.31 and later.
FlattenUnordered
(#2726, #2728)v0.3.27
Compare Source
Note: This release of futures-util has been yanked due to a bug fixed in 0.3.31 and a compile failure with futures-task 0.3.31 and later.
TryFlattenUnordered
(#2577, #2590, #2606, #2607)AbortHandle::is_aborted
(#2710)AbortRegistration::handle
(#2712)BiLock
strict-provenance compatible (#2716)hyperium/http (http)
v0.2.12
Compare Source
What's Changed
HeaderMap
, returning an error if oversize instead of panicking.HeaderName::from_lowercase
that could allow NUL bytes in some cases.v0.2.11
Compare Source
What's Changed
HeaderMap::iter()
.v0.2.10
Compare Source
Authority
to handle square brackets in incorrect order.HeaderMap::with_capacity()
to handle arithmetic overflow.matklad/once_cell (once_cell)
v1.20.2
Compare Source
portable_atomic
from Cargo.lock if it is not, in fact, used: #267This is a work-around for this cargo bhttps://github.com/rust-lang/cargo/issues/108010801.
v1.20.1
Compare Source
race
module using justportable_atomic
, withoutcritical_section
and providebetter error messages on targets without atomic CAS instruction,
#265.
v1.20.0
Compare Source
v1.19.0
Compare Source
portable-atomic
instead ofatomic-polyfill
, #251.v1.18.0
Compare Source
MSRV
is updated to 1.60.0 to take advantage ofdep:
syntax for cargo features,removing "implementation details" from publicly visible surface.
v1.17.2
Compare Source
Lazy::{force,deref}_mut()
, #231.rayon-rs/rayon (rayon)
v1.10.0
Compare Source
ParallelSlice::par_chunk_by
andParallelSliceMut::par_chunk_by_mut
work like the slice methodschunk_by
and
chunk_by_mut
added in Rust 1.77.v1.9.0
Compare Source
IndexedParallelIterator::by_exponential_blocks
andby_uniform_blocks
allow processing items in smaller groups at a time.iter::walk_tree
,walk_tree_prefix
, andwalk_tree_postfix
functions enable custom parallel iteration over tree-like structures.
ParallelIterator::collect_vec_list
returns items as a linkedlist of vectors, which is an efficient mode of parallel collection used by
many of the internal implementations of
collect
.ParallelSliceMut::par_split_inclusive_mut
,ParallelSlice::par_split_inclusive
, andParallelString::par_split_inclusive
all work like a normal split butkeeping the separator as part of the left slice.
ParallelString::par_split_ascii_whitespace
splits only on ASCIIwhitespace, which is faster than including Unicode multi-byte whitespace.
OsString
now implementsFromParallelIterator<_>
andParallelExtend<_>
for a few item types similar to the standard
FromIterator
andExtend
.Pattern
trait for string methods is now implemented for[char; N]
and&[char; N]
, matching any of the given characters.v1.8.1
Compare Source
"web_spin_lock"
crate feature makes mutexes spin on the mainbrowser thread in WebAssembly, rather than suffer an error about forbidden
atomics.wait
if they were to block in that context. Thanks @RReverser!v1.8.0
Compare Source
rustc
is now 1.63.ThreadPoolBuilder::use_current_thread
to 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_scoped
now usesstd::thread::scope
.std::thread::available_parallelism
instead of thenum_cpus
crate.v1.7.0
Compare Source
rustc
is now 1.59.ParallelIterator::take_any
andskip_any
methods work likeunordered
IndexedParallelIterator::take
andskip
, counting items inwhatever order they are visited in parallel.
ParallelIterator::take_any_while
andskip_any_while
methods worklike unordered
Iterator::take_while
andskip_while
, which previously hadno parallel equivalent. The "while" condition may be satisfied from anywhere
in the parallel iterator, affecting all future items regardless of position.
yield_now
andyield_local
functions will cooperatively yieldexecution to Rayon, either trying to execute pending work from the entire
pool or from just the local deques of the current thread, respectively.
redis-rs/redis-rs (redis)
v0.27.5
: v0.27.5Compare Source
Changes & Bug fixes
ConnectionManager
(#1372 @dcreager)DRYRUN
(#1373 @ArtemIsmagilov)hashbrown::HashMap
andhashbrown::HashSet
(#1359 @feelingsonice)CI improvements
v0.27.4
: redis v0.27.4Compare Source
Changes & Bug fixes
CI improvements
v0.27.3
Compare Source
Changes & Bug fixes
CI improvements
v0.27.2
Compare Source
Changes & Bug fixes
v0.27.1
: v0.27.1Compare Source
Changes & Bug fixes
v0.27.0
Compare Source
Features
Changes & Bug fixes
New Contributors
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), 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 was generated by Mend Renovate. View the repository job log.