-
Notifications
You must be signed in to change notification settings - Fork 0
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 rust crate axum to 0.7.0 #145
Closed
Closed
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
Bumps [trim-newlines](https://github.com/sindresorhus/trim-newlines) from 3.0.0 to 3.0.1. - [Release notes](https://github.com/sindresorhus/trim-newlines/releases) - [Commits](https://github.com/sindresorhus/trim-newlines/commits) --- updated-dependencies: - dependency-name: trim-newlines dependency-type: indirect ... Signed-off-by: dependabot[bot] <[email protected]>
…newlines-3.0.1
`flexi_logger` version `0.18.0` broke a lot of stuff, this fixes those broken things.
fix(deps): update rust crate flexi_logger to 0.18.0
Instead of being given the option to start all of the sub-servers (`whirl run` or `whirl run all`), you are now given the option to specify a selection of sub-servers by passing a comma-seperated list to the `run` sub-command (`whirl run distributor,hub`). Despite the changes, `whirl run` still starts all of the available sub-servers!
fix(deps): update rust crate tokio to 1.6.2
I guess at some point I accidentally inserted a newline to the end of the `.license_template` file, don't know how I didn't notice until now but this commit fixes the errors that rustfmt would report.
fix(deps): update rust crate tokio to 1.7.0
Issue came back, reverted commit, issue is gone...
At the moment, the `version` key is never accessed, but once Whirl's "`1.0`" release is out, the configuration schema will need to be standardized, the `version` key will regulate that and also ensure no one is left behind when updating. BREAKING CHANGE: `version` key is created
fix(deps): update rust crate mimalloc to 0.1.26
renovate
bot
changed the title
fix(deps): update rust crate axum to 0.7.3
fix(deps): update rust crate axum to 0.7.4
Jan 13, 2024
renovate
bot
force-pushed
the
renovate/axum-0.x
branch
from
March 24, 2024 21:20
93063a8
to
bb65e4a
Compare
renovate
bot
changed the title
fix(deps): update rust crate axum to 0.7.4
fix(deps): update rust crate axum to 0.7.5
Mar 24, 2024
renovate
bot
force-pushed
the
renovate/axum-0.x
branch
from
May 5, 2024 09:44
bb65e4a
to
2dc1da7
Compare
renovate
bot
changed the title
fix(deps): update rust crate axum to 0.7.5
fix(deps): update rust crate axum to 0.7.0
May 5, 2024
renovate
bot
force-pushed
the
renovate/axum-0.x
branch
from
September 27, 2024 22:54
2dc1da7
to
386ea2c
Compare
Fuwn
force-pushed
the
renovate/axum-0.x
branch
from
October 21, 2024 03:43
386ea2c
to
d37cc63
Compare
Fuwn
force-pushed
the
renovate/axum-0.x
branch
from
October 21, 2024 03:50
d37cc63
to
386ea2c
Compare
Renovate Ignore NotificationBecause you closed this PR without merging, Renovate will ignore this update ( If you accidentally closed this PR, or if you changed your mind: rename this PR to get a fresh replacement PR. |
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:
0.4.4
->0.7.0
Release Notes
tokio-rs/axum (axum)
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)v0.6.20
: axum - v0.6.20Compare Source
WebSocketUpgrade::write_buffer_size
andWebSocketUpgrade::max_write_buffer_size
WebSocketUpgrade::max_send_queue
Handler
forT: IntoResponse
(#2140)v0.6.19
: axum - v0.6.19Compare Source
axum::extract::Query::try_from_uri
(#2058)IntoResponse
forBox<str>
andBox<[u8]>
(#2035).source()
of composite rejections (#2030)#[debug_handler]
(#2014)v0.6.18
: axum - v0.6.18Compare Source
Sec-WebSocket-Key
header inWebSocketUpgrade
(#1972)v0.6.17
: axum - v0.6.17Compare Source
CONNECT
requests (#1958)v0.6.16
: axum - v0.6.16Compare Source
MatchedPath
in fallbacks (#1934)Router
with something nested at/
was used as a fallback (#1934)Router::new().fallback(...)
isn't optimal (#1940)v0.6.15
: axum - v0.6.15Compare Source
v0.6.14
: axum - v0.6.14Compare Source
v0.6.13
: axum - v0.6.13Compare Source
axum::rejection=trace
target (#1890)Router::nest
introduced in0.6.0.
nest
now flattens the routes which performs better (#1711)MatchedPath
in nested handlers now gives the fullmatched path, including the nested path (#1711)
Deref
andDerefMut
for built-in extractors (#1922)v0.6.12
: axum - v0.6.12Compare Source
IntoResponse
forMultipartError
(#1861)v0.6.11
: axum - v0.6.11Compare Source
S: Debug
forimpl Debug for Router<S>
(#1836)v0.6.10
: axum - v0.6.10Compare Source
#[must_use]
attributes to types that do nothing unless used (#1809)TypedHeader
extractor (#1810)Router
via a dynamic library (#1806)v0.6.9
: axum - v0.6.9Compare Source
v0.6.8
: axum - v0.6.8Compare Source
Allow
missing from routers with middleware (#1773)KeepAlive::event
for customizing the event sent for SSE keep alive (#1729)v0.6.7
: axum - v0.6.7Compare Source
FormRejection::FailedToDeserializeFormBody
which is returnedif the request body couldn't be deserialized into the target type, as opposed
to
FailedToDeserializeForm
which is only for query parameters (#1683)MockConnectInfo
for settingConnectInfo
during tests (#1767)v0.6.6
: axum - v0.6.6Compare Source
MethodRouter
toRouter::fallback
(#1730)v0.6.5
: axum - v0.6.5Compare Source
#[debug_handler]
sometimes giving wrong borrow related suggestions (#1710)impl IntoResponse
as the return type from handler functions (#1736)v0.6.4
: axum - v0.6.4Compare Source
v0.6.3
: axum - v0.6.3Compare Source
IntoResponse
for&'static [u8; N]
and[u8; N]
(#1690)Path
support types usingserde::Deserializer::deserialize_any
(#1693)RawPathParams
(#1713)Clone
andService
foraxum::middleware::Next
(#1712)v0.6.2
: axum - v0.6.2Compare Source
body_text
andstatus
methods to built-in rejections (#1612)runtime
feature ofhyper
when usingtokio
(#1671)v0.6.1
: axum - v0.6.1Compare Source
Router::with_state
(#1580)v0.6.0
: axum - v0.6.0Compare Source
Routing
fixed: Nested routers are now allowed to have fallbacks (#1521):
The outer router's fallback will still apply if a nested router doesn't have
its own fallback:
breaking: The request
/foo/
no longer matches/foo/*rest
. If you wantto match
/foo/
you have to add a route specifically for that (#1086)For example:
breaking: Path params for wildcard routes no longer include the prefix
/
. e.g./foo.js
will match/*filepath
with a value offoo.js
, not/foo.js
(#1086)For example:
fixed: Routes like
/foo
and/*rest
are no longer consideredoverlapping.
/foo
will take priority (#1086)For example:
breaking: Automatic trailing slash redirects have been removed.
Previously if you added a route for
/foo
, axum would redirect calls to/foo/
to/foo
(or vice versa for/foo/
):Either explicitly add routes for
/foo
and/foo/
or useaxum_extra::routing::RouterExt::route_with_tsr
if you want the old behavior(#1119)
breaking:
Router::fallback
now only acceptsHandler
s (similarly towhat
get
,post
, etc. accept). Use the newRouter::fallback_service
forsetting any
Service
as the fallback (#1155)This fallback on 0.5:
Becomes this in 0.6
changed:
Router::nest
now only acceptsRouter
s, the general-purposeService
nesting method has been renamed tonest_service
(#1368)breaking: Allow
Error: Into<Infallible>
forRoute::{layer, route_layer}
(#924)breaking:
MethodRouter
now panics on overlapping routes (#1102)breaking:
Router::route
now only acceptsMethodRouter
s created withget
,post
, etc. Use the newRouter::route_service
for routing toany
Service
s (#1155)breaking: Adding a
.route_layer
onto aRouter
orMethodRouter
without any routes will now result in a panic. Previously, this just did
nothing. #1327
breaking:
RouterService
has been removed sinceRouter
now implementsService
when the state is()
. UseRouter::with_state
to provide thestate and get a
Router<()>
. Note thatRouterService
only existed in thepre-releases, not 0.5 (#1552)
Extractors
added: Added new type safe
State
extractor. This can be used withRouter::with_state
and gives compile errors for missing states, whereasExtension
would result in runtime errors (#1155)We recommend migrating from
Extension
toState
for sharing application state since that is more typesafe and faster. That is done by using
Router::with_state
andState
.This setup in 0.5
Becomes this in 0.6 using
State
:If you have multiple extensions, you can use fields on
AppState
and implementFromRef
:breaking: It is now only possible for one extractor per handler to consume
the request body. In 0.5 doing so would result in runtime errors but in 0.6 it
is a compile error (#1272)
axum enforces this by only allowing the last extractor to consume the
request.
For example:
This is done by reworking the
FromRequest
trait and introducing a newFromRequestParts
trait.If your extractor needs to consume the request body then you should implement
FromRequest
, otherwise implementFromRequestParts
.This extractor in 0.5:
Becomes this in 0.6:
For an example of how to write an extractor that accepts different
Content-Types
see the [parse-body-based-on-content-type
][parse-body-based-on-content-type] example.added:
FromRequest
andFromRequestParts
derive macro re-exports fromaxum-macros
behind themacros
feature (#1352)added: Add
RequestExt
andRequestPartsExt
which adds conveniencemethods for running extractors to
http::Request
andhttp::request::Parts
(#1301)added:
JsonRejection
now displays the path at which a deserializationerror occurred (#1371)
added: Add
extract::RawForm
for accessing raw urlencoded query bytes or request body (#1487)fixed: Used
400 Bad Request
forFailedToDeserializeQueryString
rejections, instead of
422 Unprocessable Entity
(#1387)changed: The inner error of a
JsonRejection
is nowserde_path_to_error::Error<serde_json::Error>
. Previously it wasserde_json::Error
(#1371)changed: The default body limit now applies to the
Multipart
extractor (#1420)breaking:
ContentLengthLimit
has been removed. UseDefaultBodyLimit
instead (#1400)breaking:
RequestParts
has been removed as part of theFromRequest
rework (#1272)
breaking:
BodyAlreadyExtracted
has been removed (#1272)breaking: The following types or traits have a new
S
type paramwhich represents the state (#1155):
Router
, defaults to()
MethodRouter
, defaults to()
FromRequest
, no defaultHandler
, no defaultbreaking:
MatchedPath
can now no longer be extracted in middleware fornested routes. In previous versions it returned invalid data when extracted
from a middleware applied to a nested router.
MatchedPath
can still beextracted from handlers and middleware that aren't on nested routers (#1462)
breaking: Rename
FormRejection::FailedToDeserializeQueryString
toFormRejection::FailedToDeserializeForm
(#1496)Middleware
middleware::from_fn
functions (#1088)middleware::from_fn_with_state
to enable running extractors that requirestate (#1342)
middleware::from_extractor_with_state
(#1396)map_request
,map_request_with_state
for transforming therequest with an async function (#1408)
map_response
,map_response_with_state
for transforming theresponse with an async function (#1414)
IntoResponse
(#1152)extractor_middleware
which was previously deprecated.Use
axum::middleware::from_extractor
instead (#1077)Handler::layer
to haveInfallible
as the error type (#1152)Misc
simple-router-wasm
examplefor more details (#1382)
ServiceExt
with methods for turning anyService
into aMakeService
similarly toRouter::into_make_service
(#1302)From
impls have been added toextract::ws::Message
to be more inline with
tungstenite
(#1421)#[derive(axum::extract::FromRef)]
(#1430)accept_unmasked_frames
setting in WebSocketUpgrade (#1529)WebSocketUpgrade::on_failed_upgrade
to customize what to dowhen upgrading a connection fails (#1539)
#[track_caller]
so the errormessage points to where the user added the invalid route, rather than
somewhere internally in axum (#1248)
S: Service
, the bounds have beenrelaxed so the response type must implement
IntoResponse
rather than being aliteral
Response
tokio
default feature needed for WASM support. If youdon't need WASM support but have
default_features = false
for other reasonsyou likely need to re-enable the
tokio
feature (#1382)handler::{WithState, IntoService}
are merged into one type,named
HandlerService
(#1418)v0.5.17
: axum - v0.5.17Compare Source
#[track_caller]
so the errormessage points to where the user added the invalid router, rather than
somewhere internally in axum (#1248)
Multipart
extractor work withRequestBodyLimit
middleware (#1379)DefaultBodyLimit::max
for changing the default body limit (#1397)v0.5.16
: axum - v0.5.16Compare Source
Security
breaking: Added default limit to how much data
Bytes::from_request
willconsume. Previously it would attempt to consume the entire request body
without checking its length. This meant if a malicious peer sent an large (or
infinite) request body your server might run out of memory and crash.
The default limit is at 2 MB and can be disabled by adding the new
DefaultBodyLimit::disable()
middleware. See its documentation for moredetails.
This also applies to these extractors which used
Bytes::from_request
internally:
Form
Json
String
Thanks to Shachar Menashe for reporting this vulnerability.
(#1346)
v0.5.15
: axum - v0.5.15Compare Source
Note: This is a re-release of 0.5.14 that fixes an accidental breaking change.
QueryRejection
response. (#1171)v0.5.14
: axum - v0.5.14Compare Source
Yanked, as it contained an accidental breaking change.
v0.5.13
: axum - v0.5.13Compare Source
WebSocketUpgrade
cannot upgrade the connection it will return aWebSocketUpgradeRejection::ConnectionNotUpgradable
rejection (#1135)WebSocketUpgradeRejection
has a new variantConnectionNotUpgradable
variant (#1135)
v0.5.12
: axum - v0.5.12Compare Source
debug_handler
which is an attribute macro that improvestype errors when applied to handler function. It is re-exported from
axum-macros
(#1144)v0.5.11
: axum - v0.5.11Compare Source
TryFrom<http:: Method>
forMethodFilter
and use newNoMatchingMethodFilter
error in case of failure (#1130)v0.5.10
: axum - v0.5.10Compare Source
Router
cheaper to clone (#1123)v0.5.9
: axum - v0.5.9Compare Source
headers
is enabled and theform
feature is disabled (#1107)
v0.5.8
: axum - v0.5.8Compare Source
Forwarded
header inHost
extractor (#1078)
IntoResponse
forForm
(#1095)v0.5.7
: axum - v0.5.7Compare Source
Default
forExtension
(#1043)Vec<(String, String)>
inextract::Path<_>
to get vector ofkey/value pairs (#1059)
extract::ws::close_code
which contains constants for close codes (#1067)impl IntoResponse
less in docs (#1049)v0.5.6
: axum - v0.5.6Compare Source
WebSocket::protocol
to return the selected WebSocket subprotocol, if there is one. (#1022)PathRejection::WrongNumberOfParameters
to hint at usingPath<(String, String)>
orPath<SomeStruct>
(#1023)PathRejection::WrongNumberOfParameters
now uses500 Internal Server Error
sinceit's a programmer error and not a client error (#1023)
InvalidFormContentType
mentioning the wrong content typev0.5.5
: axum - v0.5.5Compare Source
GET
,HEAD
, andOPTIONS
requests inContentLengthLimit
.Request with these methods are now accepted if they do not have a
Content-Length
header, andthe request body will not be checked. If they do have a
Content-Length
header they'll berejected. This allows
ContentLengthLimit
to be used as middleware around several routes,including
GET
routes (#989)MethodRouter::{into_make_service, into_make_service_with_connect_info}
(#1010)v0.5.4
: axum - v0.5.4Compare Source
response::ErrorResponse
andresponse::Result
forIntoResponse
-based error handling (#921)middleware::from_extractor
and deprecateextract::extractor_middleware
(#957)v0.5.3
: axum - v0.5.3Compare Source
AppendHeaders
for appending headers to a response rather than overriding them (#927)axum::extract::multipart::Field::chunk
method for streaming a single chunk fromthe field (#901)
v0.5.2
: axum - v0.5.2Compare Source
Yanked, as it contained an accidental breaking change.
v0.5.1
: axum - v0.5.1Compare Source
RequestParts::extract
which allows applying an extractor as a method call ([#897)v0.5.0
: axum - v0.5.0Compare Source
added: Document sharing state between handler and middleware (#783)
added:
Extension<_>
can now be used in tuples for building responses, and will set anextension on the response (#797)
added:
extract::Host
for extracting the hostname of a request (#827)added: Add
IntoResponseParts
trait which allows defining custom responsetypes for adding headers or extensions to responses (#797)
added:
TypedHeader
implements the newIntoResponseParts
trait so theycan be returned from handlers as parts of a response (#797)
changed:
Router::merge
now acceptsInto<Router>
(#819)breaking:
sse::Event
now accepts types implementingAsRef<str>
instead ofInto<String>
as field values.
breaking:
sse::Event
now panics if a setter method is called twice instead of silentlyoverwriting old values.
breaking: Require
Output = ()
onWebSocketStream::on_upgrade
(#644)breaking: Make
TypedHeaderRejectionReason
#[non_exhaustive]
(#665)breaking: Using
HeaderMap
as an extractor will no longer remove the headers and thusthey'll still be accessible to other extractors, such as
axum::extract::Json
. InsteadHeaderMap
will clone the headers. You should prefer to useTypedHeader
to extract only theheaders you need (#698)
This includes these breaking changes:
RequestParts::take_headers
has been removed.RequestParts::headers
returns&HeaderMap
.RequestParts::headers_mut
returns&mut HeaderMap
.HeadersAlreadyExtracted
has been removed.HeadersAlreadyExtracted
variant has been removed from these rejections:RequestAlreadyExtracted
RequestPartsAlreadyExtracted
JsonRejection
FormRejection
ContentLengthLimitRejection
WebSocketUpgradeRejection
<HeaderMap as FromRequest<_>>::Rejection
has been changed tostd::convert::Infallible
.breaking:
axum::http::Extensions
is no longer an extractor (ie itdoesn't implement
FromRequest
). Theaxum::extract::Extension
extractor isnot impacted by this and works the same. This change makes it harder to
accidentally remove all extensions which would result in confusing errors
elsewhere (#699)
This includes these breaking changes:
RequestParts::take_extensions
has been removed.RequestParts::extensions
returns&Extensions
.RequestParts::extensions_mut
returns&mut Extensions
.RequestAlreadyExtracted
has been removed.<Request as FromRequest>::Rejection
is nowBodyAlreadyExtracted
.<http::request::Parts as FromRequest>::Rejection
is nowInfallible
.ExtensionsAlreadyExtracted
has been removed.ExtensionsAlreadyExtracted
removed variant has been removed from these rejections:ExtensionRejection
PathRejection
MatchedPathRejection
WebSocketUpgradeRejection
breaking:
Redirect::found
has been removed (#800)breaking:
AddExtensionLayer
has been removed. UseExtension
instead. It now implementstower::Layer
(#807)breaking:
AddExtension
has been moved from the root module tomiddleware
breaking:
.nest("/foo/", Router::new().route("/bar", _))
now does the right thing andresults in a route at
/foo/bar
instead of/foo//bar
(#824)breaking: Routes are now required to start with
/
. Previously routes such as:foo
wouldbe accepted but most likely result in bugs (#823)
breaking:
Headers
has been removed. Arrays of tuples directly implementIntoResponseParts
so([("x-foo", "foo")], response)
now works (#797)breaking:
InvalidJsonBody
has been replaced withJsonDataError
to clearly signal that therequest body was syntactically valid JSON but couldn't be deserialized into the target type
breaking:
Handler
is no longer an#[async_trait]
but instead has anassociated
Future
type. That allows users to build their ownHandler
typeswithout paying the cost of
#[async_trait]
(#879)changed: New
JsonSyntaxError
variant added toJsonRejection
. This is returned when therequest body contains syntactically invalid JSON
fixed: Correctly set the
Content-Length
header for response toHEAD
requests (#734)
fixed: Fix wrong
content-length
forHEAD
requests to endpoints that returns chunkedresponses (#755)
fixed: Fixed several routing bugs related to nested "opaque" tower services (i.e.
non-
Router
services) (#841 and #842)changed: Update to tokio-tungstenite 0.17 (#791)
breaking:
Redirect::{to, temporary, permanent}
now accept&str
insteadof
Uri
(#889)breaking: Remove second type parameter from
Router::into_make_service_with_connect_info
and
Handler::into_make_service_with_connect_info
to supportMakeService
sthat accept multiple targets (#892)
v0.4.8
Compare Source
v0.4.7
: axum - v0.4.7Compare Source
tower::Layer
forExtension
(#801)AddExtensionLayer
. UseExtension
instead (#805)v0.4.6
: axum - v0.4.6Compare Source
middleware::from_fn
for creating middleware from async functions.This previously lived in axum-extra but has been moved to axum (#719)
Allow
header when responding with405 Method Not Allowed
(#733)v0.4.5
: v0.4.5Compare Source
axum-macros and is deprecated (#738)
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.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.