Skip to content

fix(deps): update rust crate leptos to v0.8.22 - #77

Merged
dezren39 merged 1 commit into
mainfrom
renovate/leptos-0.x
Oct 23, 2026
Merged

fix(deps): update rust crate leptos to v0.8.22#77
dezren39 merged 1 commit into
mainfrom
renovate/leptos-0.x

Conversation

@renovate

@renovate renovate Bot commented Nov 8, 2023 •
edited
Loading

Copy link
Copy Markdown
Contributor

Note

This PR body was truncated due to platform limits.

This PR contains the following updates:

Package Type Update Change
leptos (source) dependencies minor 0.4.5 → 0.8.0
leptos (source) dependencies minor 0.4 → 0.8

Release Notes

leptos-rs/leptos (leptos)

v0.8.22

Compare Source

What's Changed

Full Changelog: leptos-rs/leptos@v0.8.21...v0.8.22

v0.8.21

What's Changed
New Contributors

Full Changelog: leptos-rs/leptos@v0.8.19...v0.8.20

v0.8.19

Compare Source

A patch release, mostly of bugfixes.

Note: one of these includes a behavior change, which is that the primary server function encodings now respect the Axum/Actix request body size limits, rather than ignoring them. If you are accustomed to sending very large data (for example, a POST request > 2mb) via server functions, you may need to increase the request body size limit via Actix PayloadConfig or Axum DefaultBodyLimit (see docs for each server framework.)

Multipart data (file uploads) are not affected.

What's Changed

New Contributors

Full Changelog: leptos-rs/leptos@v0.8.18...v0.8.19

v0.8.17

Compare Source

What's Changed

New Contributors

Full Changelog: leptos-rs/leptos@v0.8.16...v0.8.17

v0.8.16

Compare Source

What's Changed

New Contributors

Full Changelog: leptos-rs/leptos@v0.8.15...v0.8.16

v0.8.15

Compare Source

What's Changed

New Contributors

Full Changelog: leptos-rs/leptos@v0.8.14...v0.8.15

v0.8.14

Compare Source

What's Changed

Full Changelog: leptos-rs/leptos@v0.8.13...v0.8.14

v0.8.13

Compare Source

What's Changed

New Contributors

Full Changelog: leptos-rs/leptos@v0.8.12...v0.8.13

v0.8.12

Compare Source

What's Changed

Full Changelog: leptos-rs/leptos@v0.8.11...v0.8.12

v0.8.11

Compare Source

What's Changed
New Contributors

Full Changelog: leptos-rs/leptos@v0.8.10...v0.8.11

v0.8.10

Compare Source

What's Changed
New Contributors

Full Changelog: leptos-rs/leptos@v0.8.9...v0.8.10

v0.8.9

Compare Source

This includes patch releases to the reactive_graph, tachys, wasm_split_macros, server_fn, leptos, and router crates.

What's Changed

Full Changelog: leptos-rs/leptos@v0.8.8...v0.8.9

v0.8.8

What's Changed

New Contributors

Full Changelog: leptos-rs/leptos@v0.8.6...v0.8.8

v0.8.6

Compare Source

Just a patch release, mostly to support #[server] #[lazy] for lazy server functions.

Going forward, patch releases for various crates will have version numbers that are not coupled to one another, and will only be bumped when they've actually changed; so this release is 0.8.6 for leptos, leptos_macro, and server_fn_macro, but does not arbitrarily bump other packages that haven't changed.

See 0.8.5 for notes on WASM splitting.

What's Changed

Full Changelog: leptos-rs/leptos@v0.8.5...v0.8.6

v0.8.5: : WASM code splitting released!

Compare Source

This release includes WASM code-splitting/lazy-loading support, in tandem with the latest cargo-leptos release.

You can use the lazy_routes example to understand what this means!

Essentially, though, there are two patterns:

  1. Use the #[lazy] macro to make any given function lazy
  2. Use the #[lazy_route] to designate a route with a lazy-loaded view, which is loaded concurrently with the route's data

#[lazy] converts a (sync or async) function into a lazy-loaded async function

#[lazy]
fn deserialize_comments(data: &str) -> Vec<Comment> {
    serde_json::from_str(data).unwrap()
}

#[lazy_route] lets you split routes into a "data" half and a "view" half, which will be concurrently loaded by the router. This works with nested routing: so if you have ViewD and ViewE, then the router will concurrently load D's data, D's (lazy) view, E's data, and E's (lazy) view, before navigating to the page.

struct ViewD {
    data: Resource<Result<Vec<i32>, ServerFnError>>,
}

#[lazy_route]
impl LazyRoute for ViewD {
    fn data() -> Self {
        Self {
            data: Resource::new(|| (), |_| d_data()),
        }
    }

    fn view(this: Self) -> AnyView {
        let items = move || {
            Suspend::new(async move {
                this.data
                    .await
                    .unwrap_or_default()
                    .into_iter()
                    .map(|item| view! { <li>{item}</li> })
                    .collect::<Vec<_>>()
            })
        };
        view! {
            <p id="page">"View D"</p>
            <hr/>
            <Suspense fallback=|| view! { <p id="loading">"Loading..."</p> }>
                <ul>{items}</ul>
            </Suspense>
            <Outlet/>
        }
        .into_any()
    }
}

#[server]
async fn d_data() -> Result<Vec<i32>, ServerFnError> {
    tokio::time::sleep(std::time::Duration::from_millis(250)).await;
    Ok(vec![1, 1, 2, 3, 5, 8, 13])
}

Our whole July stream was dedicated to the topic, if you want more in depth discussion.

What's Changed

Full Changelog: leptos-rs/leptos@v0.8.4...v0.8.5

v0.8.4

Compare Source

There are some small bugfixes in here, as well as improvements to the hot-reloading code. This is mostly intended to be a sort of "last patch" before merging the code-splitting changes in #​3988, so that there is a patch people can pin to in case those inadvertently introduce any regressions.

What's Changed

[!IMPORTANT]
✂ PR body was truncated to here.

Configuration

📅 Schedule: (UTC)

  • 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 these updates again.

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

This PR was generated by Mend Renovate. View the repository job log.

@renovate
renovate Bot requested review from a team and dezren39 as code owners November 8, 2023 00:45
@renovate renovate Bot changed the title Update Rust crate leptos to v0.5.2 Update Rust crate leptos to v0.5.3 Nov 28, 2023
@renovate
renovate Bot force-pushed the renovate/leptos-0.x branch 2 times, most recently from 870317b to a271c7a Compare November 29, 2023 06:32
@renovate renovate Bot changed the title Update Rust crate leptos to v0.5.3 Update Rust crate leptos to v0.5.4 Nov 29, 2023
@renovate
renovate Bot force-pushed the renovate/leptos-0.x branch from a271c7a to 9f78c49 Compare January 16, 2024 00:15
@renovate renovate Bot changed the title Update Rust crate leptos to v0.5.4 Update Rust crate leptos to v0.5.5 Jan 16, 2024
@renovate

renovate Bot commented Jan 16, 2024 •
edited
Loading

Copy link
Copy Markdown
Contributor Author

⚠ Artifact update problem

Renovate failed to update artifacts related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

  • any of the package files in this branch needs updating, or
  • the branch becomes conflicted, or
  • you click the rebase/retry checkbox if found above, or
  • you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: sources/web-gen/Cargo.lock
Command failed: cargo update --config net.git-fetch-with-cli=true --manifest-path sources/web-gen/Cargo.toml --package leptos@0.4.5 --precise 0.6.11
    Updating crates.io index
error: failed to select a version for the requirement `leptos = "^0.4.5"`
candidate versions found which didn't match: 0.6.11
location searched: crates.io index
required by package `leptos_router v0.4.5`
    ... which satisfies dependency `leptos_router = "^0.4.5"` (locked to 0.4.5) of package `web-gen v0.1.0 (/tmp/renovate/repos/github/developing-today/code/sources/web-gen)`
perhaps a crate was updated and forgotten to be re-vendored?
File name: sources/web-gen-api/Cargo.lock
Command failed: cargo update --config net.git-fetch-with-cli=true --manifest-path sources/web-gen-api/Cargo.toml --package leptos@0.4.5 --precise 0.6.11
    Updating crates.io index
error: failed to select a version for the requirement `leptos = "^0.4.5"`
candidate versions found which didn't match: 0.6.11
location searched: crates.io index
required by package `leptos_actix v0.4.5`
    ... which satisfies dependency `leptos_actix = "^0.4"` (locked to 0.4.5) of package `leptos_start v0.1.0 (/tmp/renovate/repos/github/developing-today/code/sources/web-gen-api)`
perhaps a crate was updated and forgotten to be re-vendored?

@renovate
renovate Bot force-pushed the renovate/leptos-0.x branch from 9f78c49 to 5b42fef Compare January 17, 2024 03:23
@renovate renovate Bot changed the title Update Rust crate leptos to v0.5.5 Update Rust crate leptos to v0.5.6 Jan 17, 2024
@renovate
renovate Bot force-pushed the renovate/leptos-0.x branch from 5b42fef to 5855aa9 Compare January 19, 2024 18:04
@renovate renovate Bot changed the title Update Rust crate leptos to v0.5.6 Update Rust crate leptos to v0.5.7 Jan 19, 2024
@renovate
renovate Bot force-pushed the renovate/leptos-0.x branch from 5855aa9 to 0127136 Compare January 26, 2024 20:50
@renovate renovate Bot changed the title Update Rust crate leptos to v0.5.7 Update Rust crate leptos to v0.6.1 Jan 26, 2024
@renovate
renovate Bot force-pushed the renovate/leptos-0.x branch from 0127136 to 84f9fac Compare January 27, 2024 02:57
@renovate renovate Bot changed the title Update Rust crate leptos to v0.6.1 Update Rust crate leptos to v0.6.3 Jan 27, 2024
@renovate
renovate Bot force-pushed the renovate/leptos-0.x branch from 84f9fac to 8850635 Compare January 30, 2024 14:43
@renovate renovate Bot changed the title Update Rust crate leptos to v0.6.3 Update Rust crate leptos to v0.6.4 Jan 30, 2024
@renovate
renovate Bot force-pushed the renovate/leptos-0.x branch from 8850635 to c30000f Compare February 1, 2024 01:33
@renovate renovate Bot changed the title Update Rust crate leptos to v0.6.4 Update Rust crate leptos to v0.6.5 Feb 1, 2024
@renovate
renovate Bot force-pushed the renovate/leptos-0.x branch from c30000f to f76325e Compare February 19, 2024 22:34
@renovate renovate Bot changed the title Update Rust crate leptos to v0.6.5 Update Rust crate leptos to v0.6.6 Feb 19, 2024
@renovate
renovate Bot force-pushed the renovate/leptos-0.x branch from f76325e to 7061aa2 Compare February 29, 2024 22:49
@renovate renovate Bot changed the title Update Rust crate leptos to v0.6.6 Update Rust crate leptos to v0.6.7 Feb 29, 2024
@renovate
renovate Bot force-pushed the renovate/leptos-0.x branch from 7061aa2 to e8f09a8 Compare March 3, 2024 03:39
@renovate renovate Bot changed the title Update Rust crate leptos to v0.6.7 Update Rust crate leptos to v0.6.8 Mar 3, 2024
@renovate
renovate Bot force-pushed the renovate/leptos-0.x branch from e8f09a8 to 83c35ca Compare March 4, 2024 01:34
@renovate renovate Bot changed the title Update Rust crate leptos to v0.6.8 Update Rust crate leptos to v0.6.9 Mar 4, 2024
This was referenced Oct 28, 2026
Closed
Closed
Open
Closed
Open
Closed
Open
Open
Open
Open
Open
Open
Closed
Open
Closed
Closed
Closed
Closed
Closed
Closed
Open
Open
Closed
Open
Closed
Closed
Open
Open
Closed
@dezren39 dezren39 mentioned this pull request Nov 5, 2026
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@coderabbitai coderabbitai[bot] coderabbitai[bot] left review comments
@dezren39 dezren39 Awaiting requested review from dezren39 dezren39 is a code owner

Assignees

@dezren39 dezren39

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

1 participant

@dezren39