fix(deps): update all dependencies #36
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:
0.4.4
->1.0.0
4.5.8
->4.5.16
0.9.8
->0.11.0
1.10.5
->1.10.6
0.12.5
->0.12.7
1.0.120
->1.0.127
0.7.4
->0.8.0
1.38.0
->1.40.0
1.9.1
->1.10.0
Release Notes
Xuanwo/backon (backon)
v1.1.0
Compare Source
A Letter to BackON Users
Hello everyone,
Thank you very much for using BackON!
Before releasing version
1.0.0
, I thought it would be better to let users choose their own sleeper implementations, so I didn't enable them by default. However, many users encountered runtime panics. I apologize for not finding a solution that meets all requirements simultaneously: no API breaks, allowing sleeper passing at runtime, and no extra cost.So in version
1.1.0
, I have addedtokio-sleeper
andgloo-timers-sleep
to thedefault
feature. This change will make BackON behave like version0.4.4
, allowing users to upgrade without adding new features. Additionally, I have moved the panic to occur earlier during thepoll
feature instead of during thesleep
call. This makes it easier to catch issues during development rather than at runtime. Furthermore, we will only panic during thedebug
profile and do nothing in therelease
profile. This should protect users from panics even in the worst-case scenarios.Please let me know if you have better solutions! Thanks in advance!
Xuanwo
What's Changed
Full Changelog: https://github.com/Xuanwo/backon/compare/v1.0.2...v1.1.0
v1.0.2
Compare Source
What's Changed
&mut self
function by @Xuanwo in https://github.com/Xuanwo/backon/pull/118Full Changelog: https://github.com/Xuanwo/backon/compare/v1.0.1...v1.0.2
v1.0.1
Compare Source
What's Changed
Full Changelog: https://github.com/Xuanwo/backon/compare/v1.0.0...v1.0.1
v1.0.0
Compare Source
Upgrade
Since 1.0.0, backon Retry doesn't take a reference of builder anymore:
Since version 0.5.0, backon no longer directly depends on
tokio
. Instead, users can now provide their own sleep implementation.For example:
To maintain the same behavior as before, please enable the
tokio-sleep
feature.What's Changed
Full Changelog: https://github.com/Xuanwo/backon/compare/v0.5.0...v1.0.0
v0.5.0
Compare Source
Upgrade
Since version 0.5.0, backon no longer directly depends on
tokio
. Instead, users can now provide their own sleep implementation.For example:
To maintain the same behavior as before, please enable the
tokio-sleep
feature.What's Changed
New Contributors
Full Changelog: https://github.com/Xuanwo/backon/compare/v0.4.4...v0.5.0
clap-rs/clap (clap)
v4.5.16
Compare Source
Fixes
derive
feature is missingv4.5.15
Compare Source
Compatiblity
Arg::remove
changed return typesFixes
Arg::remove
return the removed itemv4.5.14
Compare Source
Features
Arg::add
for attaching arbitrary state, like completion hints, toArg
withoutArg
knowing about itv4.5.13
Compare Source
Fixes
#[flatten]
ing an optional#[group(skip)]
v4.5.12
Compare Source
v4.5.11
Compare Source
v4.5.10
Compare Source
v4.5.9
Compare Source
Fixes
dagger/dagger (dagger-sdk)
v0.11.9
Compare Source
Fixed
What to do next?
rust-lang/regex (regex)
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.seanmonstar/reqwest (reqwest)
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.serde-rs/json (serde_json)
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
launchbadge/sqlx (sqlx)
v0.8.1
Compare Source
16 pull requests were merged this release cycle.
This release contains a fix for RUSTSEC-2024-0363.
Postgres users are advised to upgrade ASAP as a possible exploit has been demonstrated:
#3440 (comment)
MySQL and SQLite do not appear to be exploitable, but upgrading is recommended nonetheless.
Added
Changed
Fixed
v0.8.0
Compare Source
70 pull requests were merged this release cycle.
#2697 was merged the same day as release 0.7.4 and so was missed by the automatic CHANGELOG generation.
Breaking
Added
Changed
Fixed
clock
andstd
features ofworkspace.dependencies.chrono
.tokio-rs/tokio (tokio)
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)uuid-rs/uuid (uuid)
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.
51924085ed
to72325f4638
chore(deps): update all dependenciesto fix(deps): update all dependencies72325f4638
to56a0b94b5b
56a0b94b5b
tocfadd35ffc
cfadd35ffc
to6cdd5b29fe
6cdd5b29fe
to7a16123daa
7a16123daa
todad14c9858