Skip to content
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.

Sign up for GitHub

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

Jump to bottom

chore(deps): update all non-major #20

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

chore(deps): update all non-major #20

wants to merge 1 commit into from

Conversation

snapiz
Copy link
Contributor

@snapiz snapiz commented Oct 30, 2023 •
edited
Loading

This PR contains the following updates:

Package Type Update Change
axum dependencies minor 0.6.20 -> 0.7.5
http dependencies patch 0.2.9 -> 0.2.12
leptos dependencies minor 0.5.1 -> 0.6.11
leptos_axum dependencies minor 0.5.1 -> 0.6.11
leptos_meta dependencies minor 0.5.1 -> 0.6.11
leptos_router dependencies minor 0.5.1 -> 0.6.11
log dependencies patch 0.4.20 -> 0.4.21
simple_logger dependencies minor 4.2.0 -> 4.3.3
thiserror dependencies patch 1.0.50 -> 1.0.59
tokio (source) dependencies minor 1.33.0 -> 1.37.0
tower-http dependencies minor 0.4.4 -> 0.5.2
wasm-bindgen (source) dependencies patch =0.2.87 -> =0.2.92

Release Notes

tokio-rs/axum (axum)

v0.7.5: axum - v0.7.5

Compare Source

  • fixed: Fixed layers being cloned when calling axum::serve directly with
    a Router or MethodRouter (#​2586)
  • fixed: h2 is no longer pulled as a dependency unless the http2 feature
    is enabled (#​2605)

v0.7.4: axum - v0.7.4

Compare Source

  • fixed: Fix performance regression present since axum 0.7.0 (#​2483)
  • fixed: Improve debug_handler on tuple response types (#​2201)
  • added: Add must_use attribute to Serve and WithGracefulShutdown (#​2484)
  • added: Re-export axum_core::body::BodyDataStream from axum

v0.7.3: axum - v0.7.3

Compare Source

  • added: Body implements From<()> now (#​2411)
  • change: Update version of multer used internally for multipart (#​2433)
  • change: Update tokio-tungstenite to 0.21 (#​2435)
  • added: Enable tracing feature by default (#​2460)
  • added: Support graceful shutdown on serve (#​2398)
  • added: RouterIntoService implements Clone (#​2456)

v0.7.2: axum - v0.7.2

Compare Source

  • added: Add axum::body::to_bytes (#​2373)
  • fixed: Gracefully handle accept errors in serve (#​2400)

v0.7.1: axum - v0.7.1

Compare Source

  • fix: Fix readme.

v0.7.0: axum - v0.7.0

Compare Source

  • breaking: Update public dependencies. axum now requires
  • breaking: axum now requires tower-http 0.5
  • breaking: Remove deprecated WebSocketUpgrade::max_send_queue
  • breaking: The following types/traits are no longer generic over the request body
    (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
  • breaking: axum no longer re-exports hyper::Body as that type is removed
    in hyper 1.0. Instead axum has its own body type at axum::body::Body (#​1751)
  • breaking: extract::BodyStream has been removed as body::Body
    implements Stream and FromRequest directly (#​1751)
  • breaking: Change sse::Event::json_data to use axum_core::Error as its error type (#​1762)
  • breaking: Rename DefaultOnFailedUpdgrade to DefaultOnFailedUpgrade (#​1664)
  • breaking: Rename OnFailedUpdgrade to OnFailedUpgrade (#​1664)
  • breaking: TypedHeader has been move to axum-extra (#​1850)
  • breaking: Removed re-exports of Empty and Full. Use
    axum::body::Body::empty and axum::body::Body::from respectively (#​1789)
  • breaking: The response returned by IntoResponse::into_response must use
    axum::body::Body as the body type. axum::response::Response does this
    (#​1789)
  • breaking: Removed the BoxBody type alias and its box_body
    constructor. Use axum::body::Body::new instead (#​1789)
  • breaking: Remove RawBody extractor. axum::body::Body implements FromRequest directly (#​1789)
  • breaking: The following types from http-body no longer implement IntoResponse:
    • Full, use Body::from instead
    • Empty, use Body::empty instead
    • BoxBody, use Body::new instead
    • UnsyncBoxBody, use Body::new instead
    • MapData, use Body::new instead
    • MapErr, use Body::new instead
  • added: Add axum::extract::Request type alias where the body is axum::body::Body (#​1789)
  • added: Add Router::as_service and Router::into_service to workaround
    type inference issues when calling ServiceExt methods on a Router (#​1835)
  • breaking: Removed axum::Server as it was removed in hyper 1.0. Instead
    use axum::serve(listener, service) or hyper/hyper-util for more configuration options (#​1868)
  • breaking: Only inherit fallbacks for routers nested with Router::nest.
    Routers nested with Router::nest_service will no longer inherit fallbacks (#​1956)
  • fixed: Don't remove the Sec-WebSocket-Key header in WebSocketUpgrade (#​1972)
  • added: Add axum::extract::Query::try_from_uri (#​2058)
  • added: Implement IntoResponse for Box<str> and Box<[u8]> ([#​2035])
  • breaking: Simplify MethodFilter. It no longer uses bitflags (#​2073)
  • fixed: Fix bugs around merging routers with nested fallbacks (#​2096)
  • fixed: Fix .source() of composite rejections (#​2030)
  • fixed: Allow unreachable code in #[debug_handler] (#​2014)
  • change: axum's MSRV is now 1.66 (#​1882)
  • added: Implement IntoResponse for (R,) where R: IntoResponse (#​2143)
  • changed: For SSE, add space between field and value for compatibility (#​2149)
  • added: Add NestedPath extractor (#​1924)
  • added: Add handle_error function to existing ServiceExt trait (#​2235)
  • breaking: impl<T> IntoResponse(Parts) for Extension<T> now requires
    T: Clone, as that is required by the http crate (#​1882)
  • added: Add axum::Json::from_bytes (#​2244)
  • added: Implement FromRequestParts for http::request::Parts (#​2328)
  • added: Implement FromRequestParts for http::Extensions (#​2328)
  • fixed: Clearly document applying DefaultBodyLimit to individual routes (#​2157)
hyperium/http (http)

v0.2.12

Compare Source

What's Changed
  • Add methods to allow trying to allocate in the HeaderMap, returning an error if oversize instead of panicking.
  • Fix HeaderName::from_lowercase that could allow NUL bytes in some cases.

v0.2.11

Compare Source

What's Changed

  • Fix MIRI warnings in HeaderMap::iter().

v0.2.10

Compare Source

  • Fix parsing of Authority to handle square brackets in incorrect order.
  • Fix HeaderMap::with_capacity() to handle arithmetic overflow.
leptos-rs/leptos (leptos)

v0.6.11

Compare Source

The primary purpose of this release is that it includes a fix for an unfortunate memory leak when using leptos_router on the server.

Also included are

  • the ability to spread both attributes and event handlers onto an element (see the new spread example for the full set of possibilities)
  • implementing IntoView directly for Rc<str>
  • massive improvements to the spans for error reporting in the view macro
  • migrating all our examples to use the stable features/syntax by default, to reduce confusion for new users

It's important to me to say that all three of the new features above were implemented by community members. This release brings us to over 250 total contributors over time, not to mention everyone who's done work on docs, templates, or libraries that exist outside this repo. Thank you to everyone who's been involved in this project so far.

What's Changed
New Contributors

Full Changelog: leptos-rs/leptos@v0.6.10...v0.6.11

v0.6.10

Compare Source

Mostly a patch release with a number of bugfixes, as well as some nice quality-of-life improvements:

  • allowing #[prop(attrs)] on slots
  • add support for on: to dynamic children of components (i.e., when you do <MyComponent on:.../>, the event listener is now applied correctly to more of the children of <MyComponent/>)

What's Changed

New Contributors

Full Changelog: leptos-rs/leptos@v0.6.9...v0.6.10

v0.6.9

Compare Source

Mostly this release exists to fix imports in Cargo, as well as a few minor bug fixes

What's Changed

New Contributors

Full Changelog: leptos-rs/leptos@v0.6.8...v0.6.9

v0.6.8

Compare Source

Mostly this release is to disable file hashing by default, and streamline it's use. It can now be enabled by setting hash-files=true in your Cargo.toml or setting the LEPTOS_HASH_FILES=true env var when running cargo-leptos. If you're using Docker or moving the bin to a new folder, you need to copy the (by default) hash.txt file from target/{release_profile_name} to the same folder as your binary, and make sure the env var or cargo.toml option is enabled. Also some minor bug fixes

What's Changed

New Contributors

Full Changelog: leptos-rs/leptos@v0.6.7...v0.6.8

v0.6.7: 0.6.7

Compare Source

Hello everyone! Some lovely changes in here. My favorite is the addition of version hashes to css,js, and wasm files to automatically invalidate browser caching issues. Be sure to update to the latest version of cargo leptos(v0.2.8) to test out this feature. As always, big thanks to our returning contributors and welcome to the new folks!

What's Changed

New Contributors

Full Changelog: leptos-rs/leptos@v0.6.6...v0.6.7

v0.6.6

Compare Source

Fixed some issues with examples, integrated a server macro for Spin, and improved a number of typos. Thanks to all that participated!
For general 0.6 release notes, see here.

What's Changed

New Contributors

Full Changelog: leptos-rs/leptos@v0.6.5...v0.6.6

v0.6.5: 0.6.5

Compare Source

This fixes a few bugs that have popped up since 0.6. For general 0.6 release notes, see here.

What's Changed

Full Changelog: leptos-rs/leptos@v0.6.4...v0.6.5

v0.6.4: 0.6.4

Compare Source

This fixes a few bugs that have popped up since 0.6.3. For general 0.6 migration notes, see here.

What's Changed

Full Changelog: leptos-rs/leptos@v0.6.3...v0.6.4

v0.6.3: 0.6.3

Compare Source

This is release for our new server functions rewrite and Axum 0.7 support.
This should be a relatively feature-rich release, with limited breaking changes.

Migration

Actix
  • You can remove any explicit .handle_server_fns() call in your main.rs, as server functions are now handled in .leptos_routes()
  • The current extract function has been removed, and replaced with a new extract that has the same API as the current extractor. I think this API is strictly better, but please share feedback if you disagree.
Axum
  • This release supports Axum 0.7, so you'll need to migrate from Axum 0.6. The easiest way to do this is probably to consult the diff on one of the examples. (Note that along with Axum 0.7, you'll need to update to http 1.0 and tower_http 0.5.)
  • You can remove any explicit .handle_server_fns() call in your main.rs, as server functions are now handled in .leptos_routes()
  • The current extract function has been removed, and replaced with a new extract that has the same API as the current extractor. I think this API is strictly better, but please share feedback if you disagree.
  • RequestParts has been removed, as http::request::Parts now implements Clone: any use_context::<RequestParts>() should be updated to use Parts directly instead.
ServerFnError::new()

The addition of custom error types means that constructing ServerFnError inside server functions can cause type inference errors:

let oops = Err(ServerFnError::ServerError("No server state".to_string()));
return oops;  // this is fine
oops? // this is not: cannot infer type of the type parameter `E` declared on the enum `ServerFnError`

As a result, we've added a helper ServerFnError::new which simply constructs a ServerFnError::<NoCustomError>::ServerError:

let oops = Err(ServerFnError::new("No server state"));
return oops;  // this is fine
oops? // this is also fine now

This has the benefit of being more concise than the earlier pattern in any case.

Features

A rewritten server function system that is backwards-compatible, but reduces binary size and increases flexibility, specifically by allowing

  • automatic setup of server fn handlers with .leptos_routes() from the integrations
  • a variety of additional built-in encodings (rkyv, multipart forms/file uploads) in addition to the current set (GET URL, POST URL, CBOR, Rkyv) (#​1868, #​1989)
  • support for streaming responses from server functions (#​1284)
  • ability to create custom user encodings for input and output by deriving IntoReq, FromReq, IntoRes, and/or FromRes traits
  • ability to mix and match encodings easily: This server function should be a JSON POST request and a ByteStream response, this one should be GET URL request and an rkyv response, etc.; any combination of the encodings above is supported
  • custom error types (#​1657)
  • a #[middleware] macro to add per-server-function middleware from the Tower or Actix ecosystems (#​1461)

Note: The additional included encodings (serde_lite, rkyv, multipart form data) are all enabled by additive features on the server_fn crate. If you want to use them you can just add that crate as a dependency and enable the required features.

Example: You can find a comprehensive example of these new features in the new server_fns_axum example.

Full Changelog: leptos-rs/leptos@v0.5.7...0.6.3

v0.6.2

Compare Source

This is release for our new server functions rewrite and Axum 0.7 support.
This should be a relatively feature-rich release, with limited breaking changes.

Migration

Actix
  • You can remove any explicit .handle_server_fns() call in your main.rs, as server functions are now handled in .leptos_routes()
  • The current extract function has been removed, and replaced with a new extract that has the same API as the current extractor. I think this API is strictly better, but please share feedback if you disagree.
Axum
  • This release supports Axum 0.7, so you'll need to migrate from Axum 0.6. The easiest way to do this is probably to consult the diff on one of the examples. (Note that along with Axum 0.7, you'll need to update to http 1.0 and tower_http 0.5.)
  • You can remove any explicit .handle_server_fns() call in your main.rs, as server functions are now handled in .leptos_routes()
  • The current extract function has been removed, and replaced with a new extract that has the same API as the current extractor. I think this API is strictly better, but please share feedback if you disagree.
  • RequestParts has been removed, as http::request::Parts now implements Clone: any use_context::<RequestParts>() should be updated to use Parts directly instead.
ServerFnError::new()

The addition of custom error types means that constructing ServerFnError inside server functions can cause type inference errors:

let oops = Err(ServerFnError::ServerError("No server state".to_string()));
return oops;  // this is fine
oops? // this is not: cannot infer type of the type parameter `E` declared on the enum `ServerFnError`

As a result, we've added a helper ServerFnError::new which simply constructs a ServerFnError::<NoCustomError>::ServerError:

let oops = Err(ServerFnError::new("No server state"));
return oops;  // this is fine
oops? // this is also fine now

This has the benefit of being more concise than the earlier pattern in any case.

Features

A rewritten server function system that is backwards-compatible, but reduces binary size and increases flexibility, specifically by allowing

  • automatic setup of server fn handlers with .leptos_routes() from the integrations
  • a variety of additional built-in encodings (rkyv, multipart forms/file uploads) in addition to the current set (GET URL, POST URL, CBOR, Rkyv) (#​1868, #​1989)
  • support for streaming responses from server functions (#​1284)
  • ability to create custom user encodings for input and output by deriving IntoReq, FromReq, IntoRes, and/or FromRes traits
  • ability to mix and match encodings easily: This server function should be a JSON POST request and a ByteStream response, this one should be GET URL request and an rkyv response, etc.; any combination of the encodings above is supported
  • custom error types (#​1657)
  • a #[middleware] macro to add per-server-function middleware from the Tower or Actix ecosystems (#​1461)

Note: The additional included encodings (serde_lite, rkyv, multipart form data) are all enabled by additive features on the server_fn crate. If you want to use them you can just add that crate as a dependency and enable the required features.

Example: You can find a comprehensive example of these new features in the new server_fns_axum example.

Full Changelog: leptos-rs/leptos@v0.5.7...0.6.2

v0.6.1: 0.6.1

Compare Source

This is release for our new server functions rewrite and Axum 0.7 support.
This should be a relatively feature-rich release, with limited breaking changes.

Migration

Actix
  • You can remove any explicit .handle_server_fns() call in your main.rs, as server functions are now handled in .leptos_routes()
  • The current extract function has been removed, and replaced with a new extract that has the same API as the current extractor. I think this API is strictly better, but please share feedback if you disagree.
Axum
  • This release supports Axum 0.7, so you'll need to migrate from Axum 0.6. The easiest way to do this is probably to consult the diff on one of the examples.
  • You can remove any explicit .handle_server_fns() call in your main.rs, as server functions are now handled in .leptos_routes()
  • The current extract function has been removed, and replaced with a new extract that has the same API as the current extractor. I think this API is strictly better, but please share feedback if you disagree.
  • RequestParts has been removed, as http::request::Parts now implements Clone: any use_context::<RequestParts>() should be updated to use Parts directly instead.
ServerFnError::new()

The addition of custom error types means that constructing ServerFnError inside server functions can cause type inference errors:

let oops = Err(ServerFnError::ServerError("No server state".to_string()));
return oops;  // this is fine
oops? // this is not: cannot infer type of the type parameter `E` declared on the enum `ServerFnError`

As a result, we've added a helper ServerFnError::new which simply constructs a ServerFnError::<NoCustomError>::ServerError:

let oops = Err(ServerFnError::new("No server state"));
return oops;  // this is fine
oops? // this is also fine now

This has the benefit of being more concise than the earlier pattern in any case.

Features

A rewritten server function system that is backwards-compatible, but reduces binary size and increases flexibility, specifically by allowing

  • automatic setup of server fn handlers with .leptos_routes() from the integrations
  • a variety of additional built-in encodings (rkyv, multipart forms/file uploads) in addition to the current set (GET URL, POST URL, CBOR, Rkyv) (#​1868, #​1989)
  • support for streaming responses from server functions (#​1284)
  • ability to create custom user encodings for input and output by deriving IntoReq, FromReq, IntoRes, and/or FromRes traits
  • ability to mix and match encodings easily: This server function should be a JSON POST request and a ByteStream response, this one shoul

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.

  • If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

@snapiz snapiz force-pushed the renovate/all-minor-patch branch from b96c4dd to 79c7cda Compare November 6, 2023 09:12
@snapiz snapiz changed the title chore(deps): update all non-major to 0.5.2 chore(deps): update all non-major Nov 6, 2023
@snapiz snapiz force-pushed the renovate/all-minor-patch branch from 79c7cda to 9dfde6e Compare November 13, 2023 09:11
@snapiz snapiz force-pushed the renovate/all-minor-patch branch 2 times, most recently from 13aa70c to bb0e4e6 Compare November 27, 2023 09:12
@snapiz snapiz force-pushed the renovate/all-minor-patch branch from bb0e4e6 to f98e344 Compare December 4, 2023 09:12
@snapiz snapiz force-pushed the renovate/all-minor-patch branch 2 times, most recently from 567179c to 75310ef Compare December 18, 2023 09:12
@snapiz snapiz force-pushed the renovate/all-minor-patch branch from 75310ef to 8bd98d6 Compare December 25, 2023 09:11
@snapiz snapiz force-pushed the renovate/all-minor-patch branch from 8bd98d6 to d1bee72 Compare January 1, 2024 09:11
@snapiz snapiz force-pushed the renovate/all-minor-patch branch from d1bee72 to 4db3e21 Compare January 8, 2024 09:11
@snapiz snapiz force-pushed the renovate/all-minor-patch branch from 4db3e21 to 76543dc Compare January 15, 2024 09:12
@snapiz snapiz force-pushed the renovate/all-minor-patch branch 2 times, most recently from 9ef12bb to 578b52c Compare January 29, 2024 09:11
@snapiz snapiz force-pushed the renovate/all-minor-patch branch from 578b52c to 3e79aeb Compare February 12, 2024 09:12
@snapiz snapiz force-pushed the renovate/all-minor-patch branch from 3e79aeb to c24830c Compare February 26, 2024 09:12
@snapiz snapiz force-pushed the renovate/all-minor-patch branch 2 times, most recently from cbf42e2 to bf672f9 Compare March 11, 2024 09:12
@snapiz snapiz force-pushed the renovate/all-minor-patch branch 2 times, most recently from 01754a8 to 7753376 Compare March 25, 2024 09:11
@snapiz snapiz force-pushed the renovate/all-minor-patch branch 2 times, most recently from 23dfd42 to 9b36084 Compare April 8, 2024 09:12
@snapiz snapiz force-pushed the renovate/all-minor-patch branch from 9b36084 to 32c83f3 Compare April 15, 2024 09:10
@snapiz snapiz force-pushed the renovate/all-minor-patch branch from 32c83f3 to 68cbb9b Compare April 22, 2024 09:12
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
2 participants
@snapiz @renovate-bot