fix(deps): update all dependencies #21
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "renovate/all"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
This PR contains the following updates:
1.0.86
->1.0.95
0.7.5
->0.7.9
0.4.38
->0.4.39
0.6.12
->0.7.2
0.6.12
->0.7.2
0.6.12
->0.7.2
0.6.12
->0.7.2
0.6.12
->0.7.2
1.0.120
->1.0.134
1
->2
1.38.0
->1.42.0
0.4.13
->0.5.0
0.5.2
->0.6.0
1.9.1
->1.11.0
Release Notes
dtolnay/anyhow (anyhow)
v1.0.95
Compare Source
Error::from_boxed
(#401, #402)v1.0.94
Compare Source
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)tokio-rs/axum (axum)
v0.7.9
: axum - v0.7.9Compare Source
v0.7.8
: axum - v0.7.8Compare Source
serde_json::RawValue
inEvent::json_data
(#2992)method_not_allowed_fallback
to set a fallback when a path matches but there is no handler for the given HTTP method (#2903)MethodFilter::CONNECT
,routing::connect[_service]
and
MethodRouter::connect[_service]
(#2961)NoContent
as a self-described shortcut forStatusCode::NO_CONTENT
(#2978)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)chronotope/chrono (chrono)
v0.4.39
: 0.4.39Compare Source
What's Changed
from_timestamp_nanos()
by @sgoll in https://github.com/chronotope/chrono/pull/1591NaiveWeek
methods by @bragov4ik in https://github.com/chronotope/chrono/pull/1600PartialEq
,Eq
,Hash
,Copy
andClone
onNaiveWeek
by @DSeeLP in https://github.com/chronotope/chrono/pull/1618#[inline]
tonum_days
by @CommanderStorm in https://github.com/chronotope/chrono/pull/1627leptos-rs/leptos (leptos)
v0.7.2
Compare Source
If you're migrating from 0.6 to 0.7, please see the 0.7.0 release notes here.
This is a small patch release including a couple of bugfixes, importantly to the hydration of static text nodes on
nightly
.What's Changed
popovertarget
andpopovertargetaction
for the<button>
element by @Figments in https://github.com/leptos-rs/leptos/pull/3379From<ArcStore<T>>
forStore<T, S>
by @mscofield0 in https://github.com/leptos-rs/leptos/pull/3389let:
syntax (closes #3387) by @gbj in https://github.com/leptos-rs/leptos/pull/3391nightly
(closes #3395) by @gbj in https://github.com/leptos-rs/leptos/pull/3396New Contributors
Full Changelog: https://github.com/leptos-rs/leptos/compare/v0.7.1...v0.7.2
v0.7.1
Compare Source
If you're migrating from 0.6 to 0.7, please see the 0.7.0 release notes here.
This is just a small patch release, two weeks after the 0.7.0 release, geared toward fixing in bugs and filling in API holes since then.
What's Changed
Vec<_>
in the DOM (closes #3321) by @gbj in https://github.com/leptos-rs/leptos/pull/3324!Send
Actix APIs in server functions by @gbj in https://github.com/leptos-rs/leptos/pull/3326scroll
prop to<A/>
component to control scrolling behavior (closes #2666) by @gbj in https://github.com/leptos-rs/leptos/pull/3333either!
macro by @bicarlsen in https://github.com/leptos-rs/leptos/pull/3337<noscript>
(closes #3360) by @gbj in https://github.com/leptos-rs/leptos/pull/3363ToChildren::to_children
docs. by @bicarlsen in https://github.com/leptos-rs/leptos/pull/3352usize
by @marcuswhybrow in https://github.com/leptos-rs/leptos/pull/3346Signal::derive()
behavior by @gbj in https://github.com/leptos-rs/leptos/pull/3351InertElement
(closes #3368) by @gbj in https://github.com/leptos-rs/leptos/pull/3370cargo-semver-checks
on PRs by @gbj in https://github.com/leptos-rs/leptos/pull/3375New Contributors
Full Changelog: https://github.com/leptos-rs/leptos/compare/v0.7.0...v0.7.1
v0.7.0
Compare Source
At long last, as the culmination of more than a year of work, the 0.7 release has arrived!
0.7 is a nearly-complete rewrite of the internals of the framework, with the following goals:
Getting Started
0.7 works with the current
cargo-leptos
version. If you want to start exploring, there are starter templates for Axum and Actix. Each template is only three files. They show some of the boilerplate differences; for more details, see below.Axum:
cargo leptos new --git https://github.com/leptos-rs/start-axum
(repo)Actix:
cargo leptos new --git https://github.com/leptos-rs/start-actix
(repo)New Features
.await
on resources andasync
in<Suspense/>
Currently,
create_resource
allows you to synchronously access the value of some async data as eitherNone
orSome(_)
. However, it requires that you always access it this way. This has some drawbacks:Now, you can
.await
a resource, and you can useasync
blocks within a<Suspense/>
via theSuspend
wrapper, which makes it easier to chain two resources:Reference-counted signal types
One of the awkward edge cases of current Leptos is that our
Copy
arena for signals makes it possible to leak memory if you have a collection of nested signals and do not dispose them. (See 0.6 example.) 0.7 exposesArcRwSignal
,ArcReadSignal
, etc., which areClone
but notCopy
and manage their memory via reference counting, but can easily be converted into the copyableRwSignal
etc. This makes working with nested signal correctly much easier, without sacrificing ergonomics meaningfully. See the 0.7counters
example for more..read()
and.write()
on signalsYou can now use
.read()
and.write()
to get immutable and mutable guards for the value of a signal, which will track/update appropriately: these work like.with()
and.update()
but without the extra closure, or like.get()
but without cloning.Custom HTML shell
The HTML document "shell" for server rendering is currently hardcoded as part of the server integrations, limiting your ability to customize it. Now you simply include it as part of your application, which also means that you can customize things like teh
<title>
without needing to useleptos_meta
.Enhanced attribute spreading
Any valid attribute can now be spread onto any component, allowing you to extend the UI created by a component however you want. This works through multiple components: for example, if you spread attributes onto a
Suspense
they will be passed through to whatever it returns.Improved
<ProtectedRoute/>
The current
ProtectedRoute
component is not great: it checks the condition once, synchronously, on navigation, and so it doesn't respond to changes and can't easily be used with async data. The newProtectedRoute
is reactive and uses Suspense so you can use resources or reactive data. There are examples of this now inrouter
andssr_modes_axum
.Two-way binding with
bind:
syntaxTwo-way binding allows you to pass signals directly to inputs, rather than separately managing
prop:value
andon:input
to sync the signals to the inputs.Reactive Stores
Stores are a new reactive primitive that allow you to reactively access deeply-nested fields in a struct without needing to create signals inside signals; rather, you can use plain data types, annotated with
#[derive(Store)]
, and then access fields with reactive getters/setters.Updating one subfield of a
Store
does not trigger effects only listening to a sibling field; listening to one field of a store does not track the sibling fields.Stores are most useful for nested data structures, so a succinct example is difficult, but the
stores
example shows a complete use case.Support the View Transition API for router animations
The
Routes
/FlatRoutes
component now have atransition
prop. Setting this totrue
will cause the router to use the browser's View Transition API during navigation. You can control animations during navigation using CSS classes. Which animations are used can be controlled using classes that the router will set on the<html>
element:.routing-progress
while navigating,.router-back
during a back navigation, and.router-outlet-{n}
for the depth of the outlet that is being changed (0
for the root page changing,1
for the firstOutlet
, etc.) Therouter
example uses this API.Breaking Changes
Imports
I'm reorganizing the module structure to improve docs and discoverability. We will still have a prelude that can be used for glob imports of almost everything that's currently exported from the root.
Likewise, the router exposes things via
leptos_router::components
andleptos_router::hooks
. rust-analyzer can help fix imports fairly well.I'm hoping for feedback on the new module structure, whether it makes sense, and any improvements. I have not done too much work to sort through the reexports, look at how docs look, etc. yet.
Naming
We're migrating away from
create_
naming toward more idiomatic Rust naming patterns:create_signal
tosignal
(likechannel
)create_rw_signal
toRwSignal::new()
I've left some of the current functions in, marked deprecated; others may have been missed, but should be easy to find via docs.rs.
Type erasure and view types
One of the major changes in this release is replacing the
View
enum with statically-typed views, which is where most of the binary size savings come from. If you need to branch and return one of several types, you can either use one of theEither
enums inleptos::either
, or you can use.into_any()
to erase the type. Generally speaking the compiler can do its job better if you maintain more type information so theEither
types should be preferred, butAnyView
is not bad to use when needed.Boilerplate
There have been changes to the SSR and hydration boilerplate, which include (but aren't limited to)
get_configuration
is sync (remove the.await
).leptos_routes
no longer takesLeptosOptions
as an argumentleptos::mount::hydrate_body
(hydration) instead ofleptos::mount::mount_to_body
(which is now CSR-specific)Check the starter templates for a good setup.
Route definitions
The patterns for route definition have changed in several ways.
fallback
is now a required prop on<Routes/>
, rather than an optional prop on<Router/>
<FlatRoutes/>
component that optimizes for this case<ParentRoute/>
path="foo"
becomespath=StaticSegment("foo")
, and there arepath=":id"
becomespath=ParamSegment("id")
,path="posts/:id"
becomespath=(StaticSegment("posts"), ParamSegment("id"))
, and so on. There is apath!()
macro that will do this for you: i.e., it will expandpath!("/foo/:id")
topath=(StaticSegment("foo"), ParamSegment("id"))
.See the
router
andhackernews
examples.Send
/Sync
signalsBy default, the data held in reactive primitives (signals, memos, effects) must be safe to send across threads. For non-threadsafe types, there is a "storage" generic on signal types. This defaults to
SyncStorage
, but you can optionally specifyLocalStorage
instead. Many APIs have_local()
alternatives to enable this.Custom
IntoView
andIntoAttribute
implementationsIf you currently have implementations of
IntoView
orIntoAttribute
for custom data types, in a way that allows you to use them directly in the view, you should replace those with implementations ofIntoRender
andIntoAttributeValue
, respectively. See this PR for examples.Minor Breaking Changes
Await
component now takes a plainFuture
for itsfuture
prop rather than aFn() -> Future
, because it uses an optimized resource implementationIntoRender
rather thanIntoView
(see discussion in #3062)ParamsMap
supports multiple values per key (which is supported by query strings), so the API now differentiates between inserting a new value for the same key and replacing the value, and between getting one value and getting all values for a keyStylesheet
component no longer automatically works with the file hashing feature ofcargo-leptos
. You can useHashedStylesheet
and pass it the appropriate props instead.<A>
component with aclass
prop that set theclass
on the<a>
element.) These have been replaced by the new attribute-spreading API, to reduce complexity of the components themselves.LeptosOptions
now usesArc<str>
for its fields that were formerlyString
, so that it is less expensive to clone. In practice, this usually only means using&field
orfield.as_ref()
in a few places that require&str
, and so on.experimental-islands
feature renamed toislands
batch
function no longer exists: all updates now exhibit the batching behavior that was previously opt-in viabatch
.into_any()
at the end of the component that you are going to use recursively.Signal<T>
no longer directly implementsFrom<Fn() -> T>
, which allows it to implementFrom<T>
and therefore to be a more useful replacement forMaybeSignal<T>
, for a prop that is "someT
or any signal that returnsT
." To convert a closure into aSignal<_>
you can callSignal::derive()
explicitly. I know this makes the ergonomics of using theSignal<_>
wrapper slightly worse, but it adds additional expressiveness by supporting plainT
. (If you want to keep the old behavior, consider takingimpl Fn() -> T
as a prop if you are using nightly, where all the signals as well as closures implement this trait.)Miscellaneous
I'm sure there are a bunch of small and larger changes I have not mentioned above. By the time of final release, help compiling a total list of breaking changes/migration guide would be much appreciated. At present, the starter templates and the
examples
directory in the PR can provide a pretty comprehensive set of changes.On storing views in signals...
There's a pattern I've seen many use that I do not particularly like, but accidentally enabled through the way APIs happened to be (or needed to be) designed in Leptos 0.1-0.6, in which a user stores some view in a signal and then reads it somewhere else. This was possible because
View
needed to beClone
for internal reasons. Some users used this to create custom control flow: for example, you could create a global "header view" signal, and then update it from leaf components by storing a new view in it.I'd consider this a bit of an antipattern, for a couple reasons:
Clone
but in a surprising way: you can clone the reference to a DOM node, but that is a shallow, not a deep clone, and if you use it in multiple places by.get()
ing the signal more than once, it will only appear in the last locationIn the statically-typed view tree, views are not necessarily cloneable (including the
AnyView
type), so they can't easily be stored in a signal.However, it is possible to achieve a similar goal by using a "reactive channel" pattern instead:
Send the views through a channel means they do not need to be cloned, and won't be used in more than once place (avoiding the edge cases of 2 above.) Each time you send a view through the channel, simply trigger the trigger.
v0.6.15
Compare Source
Belated release notes for 0.6.15. This was a quick patch release to incorporate two changes, one to improve rust-analyzer support and the other to switch from the unmaintained
proc-macro-error
toproc-macro-error2
per RUSTSEC.What's Changed
proc-macro-error2
to address unmaintained security advisory. by @azriel91 in https://github.com/leptos-rs/leptos/pull/2935Full Changelog: https://github.com/leptos-rs/leptos/compare/v0.6.14...v0.6.15
v0.6.14
Compare Source
Hello everyone, The biggest change in this update is to handle wasm-bindgen 0.2.93 and web_sys 0.3.70 Thanks to @sabify and @maccesch for those PRs. As always, let us know if there's issues.
What's Changed
wasm-bindgen
andweb-sys
for leptos 0.6 by @sabify in https://github.com/leptos-rs/leptos/pull/2830New Contributors
Full Changelog: https://github.com/leptos-rs/leptos/compare/v0.6.13...v0.6.14
v0.6.13
Compare Source
This release mostly includes a series of small bugfixes (see below), but also includes a fix for the annoying issues we'd been having with rust-analyzer (#2527).
What's Changed
rkyv
feature interaction with Axum integration by @gbj in https://github.com/leptos-rs/leptos/pull/2631ToChildren
by @spencewenski in https://github.com/leptos-rs/leptos/pull/2643New Contributors
Full Changelog: https://github.com/leptos-rs/leptos/compare/v0.6.12...v0.6.13
serde-rs/json (serde_json)
v1.0.134
Compare Source
RawValue
associated constants for literalnull
,true
,false
(#1221, thanks @bheylin)v1.0.133
Compare Source
v1.0.132
Compare Source
v1.0.131
Compare Source
Map<String, Value>
and&Map<String, Value>
(#1135, thanks @swlynch99)v1.0.130
Compare Source
Number
from i128 and u128 (#1141, thanks @druide)v1.0.129
Compare Source
serde_json::Map::sort_keys
andserde_json::Value::sort_all_objects
(#1199)v1.0.128
Compare Source
v1.0.127
Compare Source
v1.0.126
Compare Source
v1.0.125
Compare Source
v1.0.124
Compare Source
v1.0.123
Compare Source
v1.0.122
Compare Source
json!
in no-std crates (#1166)v1.0.121
Compare Source
dtolnay/thiserror (thiserror)
v2.0.9
Compare Source
missing_inline_in_public_items
clippy restriction being triggered in macro-generated code (#404)v2.0.8
Compare Source
derive(Error)
call sites (#399)v2.0.7
Compare Source
v2.0.6
Compare Source
v2.0.5
Compare Source
v2.0.4
Compare Source
From
impls (#391, thanks @matt-phylum)v2.0.3
Compare Source
v2.0.2
Compare Source
v2.0.1
Compare Source
v2.0.0
Compare Source
Breaking changes
Referencing keyword-named fields by a raw identifier like
{r#type}
inside a format string is no longer accepted; simply use the unraw name like{type}
(#347)This aligns thiserror with the standard library's formatting macros, which gained support for implicit argument capture later than the release of this feature in thiserror 1.x.
Trait bounds are no longer inferred on fields whose value is shadowed by an explicit named argument in a format message (#345)
Tuple structs and tuple variants can no longer use numerical
{0}
{1}
access at the same time as supplying extra positional arguments for a format message, as this makes it ambiguous whether the number refers to a tuple field vs a different positional arg (#354)Code containing invocations of thiserror's
derive(Error)
must now have a direct dependency on thethiserror
crate regardless of the error data structure's contents (#368, #369, #370, #372)Features
Support disabling thiserror's standard library dependency by disabling the default "std" Cargo feature:
thiserror = { version = "2", default-features = false }
(#373)Support using
r#source
as field name to opt out of a field named "source" being treated as an error'sError::source()
(#350)Infinite recursion in a generated Display impl now produces an
unconditional_recursion
warning (#359)A new attribute
#[error(fmt = path::to::myfmt)]
can be used to write formatting logic for an enum variant out-of-line (#367)Enums with an enum-level format message are now able to have individual variants that are
transparent
to supersede the enum-level message (#366)v1.0.69
Compare Source
v1.0.68
Compare Source
v1.0.67
Compare Source
v1.0.66
Compare Source
v1.0.65
Compare Source
v1.0.64
Compare Source
v1.0.63
Compare Source
v1.0.62
Compare Source
#[error("…", …)]
attribute (#309)tokio-rs/tokio (tokio)
v1.42.0
: Tokio v1.42.0Compare Source
1.42.0 (Dec 3rd, 2024)
Added
AsyncFd::{try_io, try_io_mut}
(#6967)Fixed
ptr->ref->ptr
roundtrip in RegistrationSet (#6929)yield_now
insideblock_in_place
(#6999)Changes
Documented
tokio::net::unix::{pid_t, gid_t, uid_t}
(#6791)Instant
docs (#6982)v1.41.1
: Tokio v1.41.1Compare Source
1.41.1 (Nov 7th, 2024)
Fixed
net
requirement fornet::UdpSocket
in docs (#6938)TcpStream
internal comment (#6944)v1.41.0
: Tokio v1.41.0Compare Source
1.41.0 (Oct 22th, 2024)
Added
global_queue_depth
(#6854, #6918)SocketAddr
(#6868)watch::Sender::sender_count
(#6836)mpsc::Receiver::blocking_recv_many
(#6867)Id
apis (#6793, #6891)Added (unstable)
LocalRuntime
(#6808)Changed
#[must_use]
toNotified
(#6828)watch
cooperative (#6846)broadcast::Receiver
cooperative (#6870)cfg_fs
forwasi
target (#6822)Fixed
Documented
OwnedFd
withAsyncFd
(#6821)AsyncFd
methods (#6890)join
andtry_join
(#6814, #6841)TcpSocket::set_nodelay
andTcpSocket::nodelay
(#6840)v1.40.0
: Tokio v1.40.0Compare Source
1.40.0 (August 30th, 2024)
Added
util::SimplexStream
(#6589)Command::process_group
(#6731){TrySendError,SendTimeoutError}::into_inner
(#6755)JoinSet::join_all
(#6784)Added (unstable)
Builder::{on_task_spawn, on_task_terminate}
(#6742)Changed
write_all_buf
when possible (#6724)UnwindSafe
(#6783)Sleep
andBatchSemaphore
instrumentation explicit roots (#6727)NonZeroU64
fortask::Id
(#6733)JoinError
(#6753)#[must_use]
toJoinHandle::abort_handle
(#6762)Documented
[build]
section doesn't go in Cargo.toml (#6728)select!
(#6774)v1.39.3
: Tokio v1.39.3Compare Source
1.39.3 (August 17th, 2024)
This release fixes a regression where the unix socket api stopped accepting the abstract socket namespace. (#6772)
v1.39.2
: Tokio v1.39.2Compare Source
1.39.2 (July 27th, 2024)
This release fixes a regression where the
select!
macro stopped accepting expressions that make use of temporary lifetime extension. (#6722)v1.39.1
: Tokio v1.39.1Compare Source
1.39.1 (July 23rd, 2024)
This release reverts "time: avoid traversing entries in the time wheel twice" because it contains a bug. (#6715)
v1.39.0
: Tokio v1.39.0Compare Source
1.39.0 (July 23rd, 2024)
Added
AsyncSeek
forEmpty
(#6663)num_alive_tasks
(#6619, #6667)Command::as_std_mut
(#6608)watch::Sender::same_channel
(#6637){Receiver,UnboundedReceiver}::{sender_strong_count,sender_weak_count}
(#6661)Default
forwatch::Sender
(#6626)Clone
forAbortHandle
(#6621)consume_budget
(#6622)Changed
ReadBuf::put_slice()
(#6629)copy_bidirectional
andcopy
(#6532)num_cpus
withavailable_parallelism
(#6709)block_on
(#6692)IntoFuture
withtimeout
(#6666)IntoFuture
withjoin!
andselect!
(#6710)Fixed
Interval
(#6612)Added (unstable)
unhandled_panic
behavior for#[tokio::main]
and#[tokio::test]
(#6593)spawned_tasks_count
(#6114)worker_park_unpark_count
(#6696)Documented
tokio::io::stdout
documentation (#6674)join.rs
andtry_join.rs
(#6641)unhandled_panic
(#6660)JoinSet::try_join_next
when all tasks are running (#6671)v1.38.1
: Tokio v1.38.1Compare Source
1.38.1 (July 16th, 2024)
This release fixes the bug identified as (#6682), which caused timers not
to fire when they should.
Fixed
wake_up
while holding all the locks of sharded time wheels (#6683)tower-rs/tower (tower)
v0.5.2
: tower 0.5.2Compare Source
Added
BoxCloneSyncService
which is aClone + Send + Sync
boxedService
(#777)BoxCloneSyncServiceLayer
which is aClone + Send + Sync
boxedLayer
(#802)v0.5.1
: tower 0.5.1Compare Source
tower-layer
dependency (#787)v0.5.0
: tower 0.5.0Compare Source
Fixed
BoxService
is nowSync
(#702)Changed
ServiceExt::ready_and
method andReadyAnd
future (#652)
retry::Policy::retry
now accepts&mut Req
and&mut Res
instead of the previous mutable versions. Thisincreases the flexibility of the retry policy. To update, update your method signature to include
mut
for both parameters. (#584)Reconnect::new
(#755)Clone
for Change (#701)Clone
forAsyncFilterLayer
(#731)tower-rs/tower-http (tower-http)
v0.6.2
Compare Source
Changed:
CompressionBody<B>
now propagatesB
's size hint in itshttp_body::Body
implementation, if compression is disabled (#531)
content-length
to be included in an HTTP message with thisbody for those cases
New Contributors
Full Changelog: https://github.com/tower-rs/tower-http/compare/tower-http-0.6.1...tower-http-0.6.2
v0.6.1
: v0.6.1Compare Source
Fixed
New Contributors
v0.6.0
: v0.6.0Compare Source
Changed:
body
module is disabled except forcatch-panic
,decompression-*
,fs
, orlimit
features (BREAKING) (#477)tower
0.5 (#503)Fixed
uuid-rs/uuid (uuid)
v1.11.0
Compare Source
What's Changed
New Contributors
Full Changelog: https://github.com/uuid-rs/uuid/compare/1.10.0...1.11.0
v1.10.0
Compare Source
Deprecations
This release deprecates and renames the following functions:
Builder::from_rfc4122_timestamp
->Builder::from_gregorian_timestamp
Builder::from_sorted_rfc4122_timestamp
->Builder::from_sorted_gregorian_timestamp
Timestamp::from_rfc4122
->Timestamp::from_gregorian
Timestamp::to_rfc4122
->Timestamp::to_gregorian
What's Changed
New Contributors
Full Changelog: https://github.com/uuid-rs/uuid/compare/1.9.1...1.10.0
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Enabled.
♻ 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 has been generated by Renovate Bot.
582a54742e
to015c678056
015c678056
toc3495ba899
c3495ba899
to46b3a4df99
46b3a4df99
to40fe7b8130
40fe7b8130
to5c941d649a
5c941d649a
toa5426e1abb
a5426e1abb
tod3bd47bd0b
d3bd47bd0b
to09230833e8
09230833e8
todfa6d1dbb1
dfa6d1dbb1
to354dab77a8
354dab77a8
to07c12ac894
07c12ac894
to7f12f8ab9e
7f12f8ab9e
to6a7c3adea5
6a7c3adea5
toa0ee22de08
a0ee22de08
to30dfab299e
30dfab299e
to16038e4dd8
16038e4dd8
to919a226980
919a226980
to13f5eee250
13f5eee250
toa6b99677c3
a6b99677c3
to2fd917ab57
2fd917ab57
toe1d8bec029
e1d8bec029
toeadb3f1561
eadb3f1561
toe5e3d0f193
e5e3d0f193
toe56e283bbb
e56e283bbb
to296e1362ea
296e1362ea
toa979ce5433
a979ce5433
to648034060e
648034060e
tod700343117
d700343117
to3a146195cb
3a146195cb
to977501fca5
977501fca5
toe3ece89a82
e3ece89a82
to12d9d44feb
12d9d44feb
to75e08c6829
75e08c6829
to81de5f1fb6
⚠️ Artifact update problem
Renovate failed to update an artifact 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:
The artifact failure details are included below:
File name: Cargo.lock
81de5f1fb6
to46947b78bf
46947b78bf
to4e35906107
4e35906107
toc3916e6cdd
c3916e6cdd
tob69f6d6040
b69f6d6040
tob78ddf47c4
b78ddf47c4
to88577417bd
Checkout
From your project repository, check out a new branch and test the changes.