-
Notifications
You must be signed in to change notification settings - Fork 3
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
chore(deps): update all non-major dependencies #19
Open
renovate
wants to merge
1
commit into
master
Choose a base branch
from
renovate/all-minor-patch
base: master
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.
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
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
from
September 18, 2023 21:17
29be620
to
1530547
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
from
September 19, 2023 15:09
1530547
to
8c3f6f7
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
from
October 1, 2023 17:38
8c3f6f7
to
6b3ea05
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
from
October 2, 2023 09:33
6b3ea05
to
5d30287
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
from
October 2, 2023 19:14
5d30287
to
72c92e9
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
from
October 3, 2023 13:41
72c92e9
to
8600900
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
from
October 6, 2023 06:48
8600900
to
c4b0a69
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
from
October 9, 2023 13:29
c4b0a69
to
ae260c7
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
from
October 9, 2023 21:36
ae260c7
to
1099f9e
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
from
October 13, 2023 04:51
1099f9e
to
1aa0758
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
from
October 14, 2023 00:54
1aa0758
to
7151a70
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
from
October 14, 2023 15:40
7151a70
to
404e417
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
from
October 16, 2023 15:22
404e417
to
c021c65
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
from
October 19, 2023 04:57
c021c65
to
31f5fad
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
4 times, most recently
from
August 20, 2024 01:20
c079879
to
fa77346
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
3 times, most recently
from
August 30, 2024 09:19
d9b27d2
to
1c3131c
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
4 times, most recently
from
September 9, 2024 16:03
3d4b945
to
6424397
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
3 times, most recently
from
September 23, 2024 17:04
a88c09f
to
1d6dce9
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
3 times, most recently
from
September 30, 2024 19:00
b4bfde9
to
4912261
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
11 times, most recently
from
October 22, 2024 21:11
60481e3
to
b987550
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
from
October 24, 2024 15:50
b987550
to
1988f20
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
None yet
0 participants
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.6.20
->0.7.7
0.21.4
->0.22.1
0.10.57
->0.10.68
1.9.5
->1.11.1
0.11.20
->0.12.8
1.72
->1.82
1.0.188
->1.0.213
1.0.106
->1.0.132
1.32.0
->1.41.0
0.4.13
->0.5.1
0.4.4
->0.6.1
0.1.37
->0.1.40
0.3.17
->0.3.18
2.4.1
->2.5.2
1.0.2
->1.1.4
Release Notes
tokio-rs/axum (axum)
v0.7.7
: axum v0.7.7Compare Source
rustdoc now generates tables of content in the sidebar (#2921)
v0.7.6
: axum - v0.7.6Compare Source
Arc
during deserialization ofPath
axum::serve::Serve::tcp_nodelay
andaxum::serve::WithGracefulShutdown::tcp_nodelay
(#2653)Router::has_routes
function (#2790)Serve::local_addr
andWithGracefulShutdown::local_addr
functions (#2881)v0.7.5
: axum - v0.7.5Compare Source
axum::serve
directly witha
Router
orMethodRouter
(#2586)h2
is no longer pulled as a dependency unless thehttp2
featureis enabled (#2605)
v0.7.4
: axum - v0.7.4Compare Source
debug_handler
on tuple response types (#2201)must_use
attribute toServe
andWithGracefulShutdown
(#2484)axum_core::body::BodyDataStream
from axumv0.7.3
: axum - v0.7.3Compare Source
Body
implementsFrom<()>
now (#2411)tracing
feature by default (#2460)serve
(#2398)RouterIntoService
implementsClone
(#2456)v0.7.2
: axum - v0.7.2Compare Source
axum::body::to_bytes
(#2373)serve
(#2400)v0.7.1
: axum - v0.7.1Compare Source
v0.7.0
: axum - v0.7.0Compare Source
WebSocketUpgrade::max_send_queue
(i.e. the
B
type param has been removed) (#1751 and #1789):FromRequestParts
FromRequest
HandlerService
HandlerWithoutStateExt
Handler
LayeredFuture
Layered
MethodRouter
Next
RequestExt
RouteFuture
Route
Router
hyper::Body
as that type is removedin hyper 1.0. Instead axum has its own body type at
axum::body::Body
(#1751)extract::BodyStream
has been removed asbody::Body
implements
Stream
andFromRequest
directly (#1751)sse::Event::json_data
to useaxum_core::Error
as its error type (#1762)DefaultOnFailedUpdgrade
toDefaultOnFailedUpgrade
(#1664)OnFailedUpdgrade
toOnFailedUpgrade
(#1664)TypedHeader
has been move toaxum-extra
(#1850)Empty
andFull
. Useaxum::body::Body::empty
andaxum::body::Body::from
respectively (#1789)IntoResponse::into_response
must useaxum::body::Body
as the body type.axum::response::Response
does this(#1789)
BoxBody
type alias and itsbox_body
constructor. Use
axum::body::Body::new
instead (#1789)RawBody
extractor.axum::body::Body
implementsFromRequest
directly (#1789)http-body
no longer implementIntoResponse
:Full
, useBody::from
insteadEmpty
, useBody::empty
insteadBoxBody
, useBody::new
insteadUnsyncBoxBody
, useBody::new
insteadMapData
, useBody::new
insteadMapErr
, useBody::new
insteadaxum::extract::Request
type alias where the body isaxum::body::Body
(#1789)Router::as_service
andRouter::into_service
to workaroundtype inference issues when calling
ServiceExt
methods on aRouter
(#1835)axum::Server
as it was removed in hyper 1.0. Insteaduse
axum::serve(listener, service)
or hyper/hyper-util for more configuration options (#1868)Router::nest
.Routers nested with
Router::nest_service
will no longer inherit fallbacks (#1956)Sec-WebSocket-Key
header inWebSocketUpgrade
(#1972)axum::extract::Query::try_from_uri
(#2058)IntoResponse
forBox<str>
andBox<[u8]>
([#2035])MethodFilter
. It no longer uses bitflags (#2073).source()
of composite rejections (#2030)#[debug_handler]
(#2014)IntoResponse
for(R,) where R: IntoResponse
(#2143)NestedPath
extractor (#1924)handle_error
function to existingServiceExt
trait (#2235)impl<T> IntoResponse(Parts) for Extension<T>
now requiresT: Clone
, as that is required by the http crate (#1882)axum::Json::from_bytes
(#2244)FromRequestParts
forhttp::request::Parts
(#2328)FromRequestParts
forhttp::Extensions
(#2328)DefaultBodyLimit
to individual routes (#2157)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 Enginesfackler/rust-openssl (openssl)
v0.10.68
Compare Source
What's Changed
Full Changelog: sfackler/rust-openssl@openssl-v0.10.67...openssl-v0.10.68
v0.10.67
Compare Source
What's Changed
MdCtxRef::digest_verify_final
by @alex in https://github.com/sfackler/rust-openssl/pull/2283New Contributors
Full Changelog: sfackler/rust-openssl@openssl-v0.10.66...openssl-v0.10.67
v0.10.66
Compare Source
What's Changed
MemBio::get_buf
with empty results by @alex in https://github.com/sfackler/rust-openssl/pull/2266Full Changelog: sfackler/rust-openssl@openssl-v0.10.65...openssl-v0.10.66
v0.10.65
Compare Source
What's Changed
pkgconf
package on some distros by @JonathanBrouwer in https://github.com/sfackler/rust-openssl/pull/2253New Contributors
Full Changelog: sfackler/rust-openssl@openssl-v0.10.64...openssl-v0.10.65
v0.10.64
Compare Source
What's Changed
Full Changelog: sfackler/rust-openssl@openssl-v0.10.63...openssl-v0.10.64
v0.10.63
Compare Source
What's Changed
Full Changelog: sfackler/rust-openssl@openssl-v0.10.62...openssl-v0.10.63
v0.10.62
Compare Source
What's Changed
rand_priv_bytes
by @overvenus in https://github.com/sfackler/rust-openssl/pull/2126New Contributors
Full Changelog: sfackler/rust-openssl@openssl-v0.10.61...openssl-v0.10.62
v0.10.61
: openssl v0.10.61Compare Source
v0.10.60
Compare Source
What's Changed
update_unchecked
tosymm::Crypter
by @alex in https://github.com/sfackler/rust-openssl/pull/2100X509StoreRef::objects
, it is unsound by @alex in https://github.com/sfackler/rust-openssl/pull/2099Full Changelog: sfackler/rust-openssl@openssl-v0.10.59...openssl-v0.10.60
v0.10.59
Compare Source
What's Changed
New Contributors
Full Changelog: sfackler/rust-openssl@openssl-v0.10.58...openssl-v0.10.59
v0.10.58
Compare Source
What's Changed
New Contributors
Full Changelog: sfackler/rust-openssl@openssl-v0.10.57...openssl-v0.10.58
rust-lang/regex (regex)
v1.11.1
Compare Source
===================
This is a new patch release of
regex
that fixes compilation on nightlyRust when the unstable
pattern
crate feature is enabled. Users on nightlyRust without this feature enabled are unaffected.
Bug fixes:
Fix the
Pattern
trait implementation as a result of nightly API breakage.v1.11.0
Compare Source
===================
This is a new minor release of
regex
that brings in an update to theUnicode Character Database. Specifically, this updates the Unicode data
used by
regex
internally to the version 16 release.New features:
Add new
regex::SetMatches::matched_all
method.Update to Unicode Character Database (UCD) version 16.
v1.10.6
Compare Source
===================
This is a new patch release with a fix for the
unstable
crate feature thatenables
std::str::Pattern
trait integration.Bug fixes:
Fix the
Pattern
trait implementation as a result of nightly API breakage.v1.10.5
Compare Source
===================
This is a new patch release with some minor fixes.
Bug fixes:
Escape invalid UTF-8 when in the
Debug
impl ofregex::bytes::Match
.v1.10.4
Compare Source
===================
This is a new patch release with some minor fixes.
Fixes a bug with compiling a reverse NFA automaton in
regex-automata
.Clarifies that when
Cow::Borrowed
is returned from replace APIs, it isequivalent to the input.
v1.10.3
Compare 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=false
for thememchr
andaho-corasick
dependencies.Fix unsound bounds check elision.
v1.10.2
Compare 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.1
Compare 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.0
Compare Source
===================
This is a new minor release of
regex
that 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|\A
on the left,\w
on the right).\>
or\b{end}
: a Unicode end-of-word boundary (\w
on the left,\W|\z
on the right)).
\b{start-half}
: half of a Unicode start-of-word boundary (\W|\A
on theleft).
\b{end-half}
: half of a Unicode end-of-word boundary (\W|\z
on theright).
The
\<
and\>
are GNU extensions to POSIX regexes. They have been addedto the
regex
crate 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_state
method 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->Hir
translation (not reachable fromregex
crate).
Remove guarantees in the API that connect the
u
flag with a specific HIRrepresentation.
regex-automata
breaking change release:This release includes a
regex-automata 0.4.0
breaking change release, whichwas necessary in order to support the new word boundary assertions. For
example, the
Look
enum has new variants and theLookSet
type now usesu32
instead of
u16
to represent a bitset of look-around assertions. These areoverall very minor changes, and most users of
regex-automata
should be ableto move to
0.4
from0.3
without any changes at all.regex-syntax
breaking change release:This release also includes a
regex-syntax 0.8.0
breaking change release,which, like
regex-automata
, was necessary in order to support the new wordboundary assertions. This release also includes some changes to the
Ast
type to reduce heap usage in some cases. If you are using the
Ast
typedirectly, your code may require some minor modifications. Otherwise, users of
regex-syntax 0.7
should be able to migrate to0.8
without any code changes.regex-lite
release:The
regex-lite 0.1.1
release contains support for the new word boundaryassertions. There are no breaking changes.
v1.9.6
Compare 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.
seanmonstar/reqwest (reqwest)
v0.12.8
Compare Source
multipart::Form::file()
method for adding files easily.Body::wrap()
to wrap anyhttp_body::Body
type.v0.12.7
Compare Source
impl Service<http::Request<_>>
forClient
.v0.12.6
Compare Source
danger_accept_invalid_hostnames
forrustls
.impl Service<http::Request<Body>>
forClient
and&'_ Client
.!Sync
bodies inBody::wrap_stream()
.hickory-dns
is used.Proxy
so thatHTTP(S)_PROXY
values take precendence overALL_PROXY
.blocking::RequestBuilder::header()
from unsettingsensitive
on passed header values.v0.12.5
Compare Source
blocking::ClientBuilder::dns_resolver()
method to change DNS resolver in blocking client.http3
feature back,Configuration
📅 Schedule: Branch creation - "before 4am on Monday" (UTC), Automerge - At any time (no schedule defined).
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR is behind base branch, 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.