chore(deps): update all dependencies #72
Loading…
x
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.95
->1.0.96
0.4.4
->1.0.0
4.5.29
->4.5.31
0.9.8
->0.16.0
0.13.0
->0.14.0
1.10.5
->1.11.1
0.12.5
->0.12.12
1.0.120
->1.0.139
0.7.4
->0.8.0
0.5.2
->0.6.0
1.9.1
->1.15.1
Release Notes
dtolnay/anyhow (anyhow)
v1.0.96
Compare Source
Xuanwo/backon (backon)
v1.4.0
Compare Source
What's Changed
futures-timer
by @NumberFour8 in https://github.com/Xuanwo/backon/pull/154New Contributors
Full Changelog: https://github.com/Xuanwo/backon/compare/v1.3.0...v1.4.0
v1.3.0
Compare Source
What's Changed
adaptable
by @Xuanwo in https://github.com/Xuanwo/backon/pull/155with_max_times
by @shikhar in https://github.com/Xuanwo/backon/pull/161New Contributors
Full Changelog: https://github.com/Xuanwo/backon/compare/v1.2.0...v1.3.0
v1.2.0
Compare Source
no_std
.What's Changed
New Contributors
Full Changelog: https://github.com/Xuanwo/backon/compare/v1.1.0...v1.2.0
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.31
Compare Source
Features
ValueParserFactory
forSaturating<T>
v4.5.30
Compare Source
Fixes
num_args(0..=1)
to be used withSetTrue
takes_values
assertionsdagger/dagger (dagger-sdk)
v0.16.1
Compare Source
Fixed
cannot sub-select 1th item from *dagql.PostCallTyped
by @sipsma in https://github.com/dagger/dagger/pull/9634What to do next?
v0.16.0
Compare Source
🔥 Breaking Changes
To match automatic configuration,
insecure-entitlements
now includessecurity.insecure
when configuring the engine manually by @jedevc in https://github.com/dagger/dagger/pull/9513Module load performance is improved and related API refactored by @sipsma in https://github.com/dagger/dagger/pull/9505
Loading of modules (the
load module
step shown in progress output) is faster now in many cases. In particular:Users of modules with large numbers of dependencies or in large git repositories are expected to see the most immediate benefit.
For some concrete numbers, here are
load module
times for thedagger-dev
's module in Dagger's repository under different scenarios:dagger call --help
on new engines with an empty cachedagger call --help
with no file changes in the repo:dagger call --help
after making a change to a random source code file in the repo:These improvements in cache utilization are also setup for future improvements not only in
load module
times but function call times more generally.This improvement comes with a few breaking changes that are not expected to impact most users. However, the changes require that users upgrade their CLI to v0.16.0 in order to connect to v0.16.0 engines. Older CLIs will error when connecting to newer engines.
In terms of the breaking changes, impacted users are those who:
They may need to update their dagger.json configuration file to add an explicit
"include"
setting to ensure those extra files or directories are loaded with the module. This is because numerous files previously implicitly loaded are now skipped by default, which contributes to the performance improvements.For example, if your module code is in
.dagger
and relies on thego.mod
file in the parent directory, you would add the following to yourdagger.json
file:The values in the
"include"
array are relative to the directory containingdagger.json
. They can be also be glob patterns (e.g."**/*.txt"
). To explicitly exclude some files matched by a previous include pattern, you can prepend the include pattern with a!
character (e.g."!**/foo.txt"
).exclude
setting existed but has now been superseded by prefixing an include pattern with a!
character. However, this is backwards-compatible, so existingexclude
settings will be automatically turned into equivalent!
-prefixed include settings when runningdagger develop
. No user intervention is needed.The core API's
ModuleSource
andModule
types have also undergone some cleanup that includes breaking changes. Most users do not interact with these APIs, but any that do may need some minor adjustments to their code. In particular:Module.initialize
no longer needs to be called; the module is initialized on creationResolveFromCaller
no longer needs to be called for local module sources; context is automatically loaded and resolved efficiently as needed by other API callsAdded
dag.Host
operations by @jedevc in https://github.com/dagger/dagger/pull/9610What to do next?
v0.15.4
Compare Source
Added
dagger.json
sdk
field tosdk.source
by @rajatjindal in https://github.com/dagger/dagger/pull/9454Fixed
What to do next?
v0.15.3
Compare Source
Added
Note: the precision of float is limited to float64 inside the engine.
Fixed
Container.WithFiles
by @jedevc in https://github.com/dagger/dagger/pull/9457Dependencies
What to do next?
v0.15.2
Compare Source
Added
dagger update
command to update dependencies indagger.json
by @rajatjindal in https://github.com/dagger/dagger/pull/8839$schema
property indagger.json
by @JacobLey in https://github.com/dagger/dagger/pull/9069Changed
CacheVolumes
are now namespaced between different modules by @rajatjindal in https://github.com/dagger/dagger/pull/8724CACHED
operations for--progress=plain
output by @marcosnils in https://github.com/dagger/dagger/pull/9344Fixed
AsService
by @marcosnils in https://github.com/dagger/dagger/pull/9247Container.terminal
by @jedevc in https://github.com/dagger/dagger/pull/9338Container.up
behaves as identically as possible toContainer.AsService.up
by @jedevc in https://github.com/dagger/dagger/pull/9231dagger install
always inserts dependencies in the right order by @jedevc in https://github.com/dagger/dagger/pull/9052What to do next?
v0.15.1
Compare Source
Fixed
What to do next?
v0.13.7
Added
expect
arg forContainer.withExec
by @jedevc in https://github.com/dagger/dagger/pull/8466This enum arg allows specifying valid return statuses for which the command
can return without failing immediately.
Container.exitCode
field to get the exit code of the lastwithExec
by @jedevc in https://github.com/dagger/dagger/pull/8466Changed
The new policies attempt to co-operate with other applications using the disk
and will adjust its cache usage accordingly.
Previously, when a function chain in
dagger call
ended in an object, we'dprint all functions that return a simple value and don't have any arguments.
Now, only object fields will be included, not all functions.
Fixed
withExec
s using theExperimentalPrivilegedNesting
flag by @sipsma in https://github.com/dagger/dagger/pull/8776What to do next?
v0.11.9
Compare Source
Fixed
What to do next?
rust-itertools/itertools (itertools)
v0.14.0
Compare Source
Breaking
cons_tuples
(#988)Added
array_combinations
(#991)k_smallest_relaxed
and variants (#925)next_array
andcollect_array
(#560)DoubleEndedIterator
forFilterOk
(#948)DoubleEndedIterator
forFilterMapOk
(#950)Changed
Q: ?Sized
inItertools::contains
(#971)chain!
(#943)into_group_map_by
documentation (#1000)tree_reduce
documentation (#955)merge_join_by
(#966)take_while_inclusive
(#972)find_or_last
andfind_or_first
(#984)tuple_combinations
(#945)track_caller
attr forasser_equal
(#976)Notable Internal Changes
default_features
inCargo.toml
todefault-features
(#985)rust-lang/regex (regex)
v1.11.1
Compare Source
===================
This is a new patch release of
regex
that fixes compilation on nightlyRust when the unstable
pattern
crate feature is enabled. Users on nightlyRust without this feature enabled are unaffected.
Bug fixes:
Fix the
Pattern
trait implementation as a result of nightly API breakage.v1.11.0
Compare Source
===================
This is a new minor release of
regex
that brings in an update to theUnicode Character Database. Specifically, this updates the Unicode data
used by
regex
internally to the version 16 release.New features:
Add new
regex::SetMatches::matched_all
method.Update to Unicode Character Database (UCD) version 16.
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.12
Compare Source
tokio/time
on WASM.v0.12.11
Compare Source
v0.12.10
Compare Source
ClientBuilder::connector_layer()
to allow customizing the connector stack.ClientBuilder::http2_max_header_list_size()
option.content-length
) information when wrapping bodies.v0.12.9
Compare Source
tls::CertificateRevocationLists
support.connection_verbose()
to output read logs.multipart::Part::file()
to automatically include content-length.v0.12.8
Compare Source
multipart::Form::file()
method for adding files easily.Body::wrap()
to wrap anyhttp_body::Body
type.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 precedence overALL_PROXY
.blocking::RequestBuilder::header()
from unsettingsensitive
on passed header values.serde-rs/json (serde_json)
v1.0.139
Compare Source
v1.0.138
Compare Source
v1.0.137
Compare Source
v1.0.136
Compare Source
v1.0.135
Compare Source
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
launchbadge/sqlx (sqlx)
v0.8.3
Compare Source
41 pull requests were merged this release cycle.
Added
Uuid
anduuid::fmt::Hyphenated
[[@abonander]]Changed
.pgpass
file warning to a debug message. [[@denschub]]PgListener::try_recv
[[@swlynch99]]UNION ALL
instead ofUNION
in nullable check [[@Suficio]]Fixed
no-transaction
flag in down migrations [[@manifest]]sqlformat
[[@tbar4]]query_as
[[@xuehaonan27]]INTERVAL[]
[[@Ddystopia]]EXPLAIN
in nullability check for QuestDB [[@Suficio]]v0.8.2
Compare Source
10 pull requests were merged this release cycle.
This release addresses a few regressions that have occurred, and refines SQLx's MSRV policy (see the FAQ).
Added
Changed
Cargo.toml
files in examples [[@carschandler]]Fixed
#[sqlx(no_pg_array)]
being forbidden on#[derive(Type)]
structs.PgListener
,PgStream::recv()
[[@abonander]]unknown message: "\\0"
errorv0.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
MySqlConnectOptions::no_engine_substitution()
[[@kolinfluence]]MySqlConnectOptions::no_engine_subsitution()
(oops) in favor of the correctly spelled version.Changed
spec_error
module [[@abonander]]Use at your own risk.
libsqlite3-sys=0.30.1
to support sqlite 3.46 [[@CommanderStorm]]ring
(the existing implementation),and
aws-lc-rs
which has optional FIPS certification.runtime-tokio-rustls
,runtime-async-std-rustls
,tls-rustls
)enable the
ring
provider of RusTLS to match the existing behavior so this should not be a breaking change.tls-rustls-aws-lc-rs
feature to use theaws-lc-rs
provider.runtime-tokio-rustls
orruntime-async-std-rustls
,this will necessitate switching to the appropriate non-legacy runtime feature:
runtime-tokio
orruntime-async-std
Fixed
sqlx::Type
[[@alu]]node12
inSQLx
action [[@hamirmahal]]v0.18.1
to avoid yankedv0.14.3
[[@CommanderStorm]]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
#[sqlx::test]
usages are applied in the correct order now.MigrateError
.-- no-transaction
to the beginning.Migration
i64
as intermediate when decoding [[@abonander]]#[derive(sqlx::Type)]
in Postgres [[@abonander]]#[sqlx(no_pg_array)]
where conflicts occur.PgTypeInfo::with_name()
infers types that start with_
to be arrays of the un-prefixed type. Wrap type names in quotes to bypass this behavior.FromRow
, returnError::ColumnDecode
forTryFrom
errors [[@abonander]]#[sqlx(try_from = "T")]
now returnError::ColumnDecode
instead ofError::ColumnNotFound
.#[sqlx(default)]
on an individual field or the struct itself would have previously suppressed the error.This doesn't seem like good behavior as it could result in some potentially very difficult bugs.
From
and apply the default explicitly.#[sqlx(rename)]
and#[sqlx(rename_all)]
to match the expected behavior (rename
wins).ConnectOptions::to_url_lossy()
to match what parsing expects.Added
MySqlTime
, auditmysql::types
for panics [[@abonander]]NonZero*
scalar types [[@AlphaKeks]]Changed
Send
trait bound from argument binding [[@bobozaur]]libsqlite3-sys
are not considered breaking changes as per our semver guarantees.MySqlConnection
to reduce sizes of futures [[@stepantubanov]]sqlx migrate add ...
[[@CommanderStorm]]Fixed
ConnectionHandleRaw
type [[@abonander]]docker compose
instead ofdocker-compose
[[@abonander]]path
ownership problems when usingsqlx_macros_unstable
[[@lily-mosquitoes]]sqlx_postgres::any
[[@Zarathustra2]]migrate
error message. (#3275) [[@nk9]]persistent
query setting when preparing queries with theAny
driver [[@etorreborre]]select_input_type!()
being unhygenic [[@CommanderStorm]]M
orC
Notice fields are not UTF-8 [[@YgorSouza]]json
-feature should activatesqlx-postgres?/json
as well [[@CommanderStorm]]clock
andstd
features ofworkspace.dependencies.chrono
.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.15.1
Compare Source
What's Changed
Full Changelog: https://github.com/uuid-rs/uuid/compare/v1.15.0...v1.15.1
v1.15.0
Compare Source
What's Changed
Debug
implementation for NonNilUUid by @rick-de-water in https://github.com/uuid-rs/uuid/pull/808New Contributors
Full Changelog: https://github.com/uuid-rs/uuid/compare/v1.14.0...v1.15.0
v1.14.0
Compare Source
What's Changed
New Contributors
Full Changelog: https://github.com/uuid-rs/uuid/compare/v1.13.2...v1.14.0
v1.13.2
Compare Source
What's Changed
Full Changelog: https://github.com/uuid-rs/uuid/compare/1.13.1...v1.13.2
v1.13.1
Compare Source
What's Changed
wasm32
withatomics
by @bushrat011899 in https://github.com/uuid-rs/uuid/pull/797New Contributors
Full Changelog: https://github.com/uuid-rs/uuid/compare/1.13.0...1.13.1
v1.13.0
Compare Source
⚠️ Potential Breakage
This release updates our version of
getrandom
to0.3
andrand
to0.9
. It is a potentially breaking change for the following users:no-std users who enable the
rng
featureuuid
still usesgetrandom
by default on these platforms. Upgrade your version ofgetrandom
and follow its new docs on configuring a custom backend.wasm32-unknown-unknown
users who enable therng
feature without thejs
featureUpgrade your version of
getrandom
and follow its new docs on configuring a backend.You'll also need to enable the
rng-getrandom
orrng-rand
feature ofuuid
to force it to usegetrandom
as its backend:If you're on
wasm32-unknown-unknown
and using thejs
feature ofuuid
you shouldn't see any breakage. We've kept this behavior by vendoring ingetrandom
's web-based backend when thejs
feature is enabled.What's Changed
getrandom
to0.3
andrand
to0.9
by @KodrAus in https://github.com/uuid-rs/uuid/pull/793getrandom
onwasm32-unknown-unknown
without JavaScript by @KodrAus in https://github.com/uuid-rs/uuid/pull/794Full Changelog: https://github.com/uuid-rs/uuid/compare/1.12.1...1.13.0
v1.12.1
Compare Source
What's Changed
New Contributors
Full Changelog: https://github.com/uuid-rs/uuid/compare/1.12.0...1.12.1
v1.12.0
Compare Source
⚠️ Possible Breakage
This release includes additional
PartialEq
implementations onUuid
, which can break inference in some cases.What's Changed
NonZeroUuid
type for optimizedOption<Uuid>
representation by @ab22593k in https://github.com/uuid-rs/uuid/pull/779NonNilUuid
by @KodrAus in https://github.com/uuid-rs/uuid/pull/783New Contributors
Full Changelog: https://github.com/uuid-rs/uuid/compare/1.11.1...1.12.0
v1.11.1
Compare Source
What's Changed
New Contributors
Full Changelog: https://github.com/uuid-rs/uuid/compare/1.11.0...1.11.1
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.
d799b4b7a1
to8209e16737
8209e16737
to8968c6000c
8968c6000c
toadd2ded683
fix(deps): update all dependenciesto chore(deps): update all dependenciesadd2ded683
to980bb18635
980bb18635
to2ac1aad84b
2ac1aad84b
toa294e01c90
a294e01c90
to76b75a57dc
76b75a57dc
to1767310c7b
1767310c7b
to6b587e6b0e