fix(deps): update all dependencies #69
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:
0.1.86
->0.1.88
0.4.40
->0.4.41
4.5.31
->4.5.38
0.17.1
->0.18.0
1.0.139
->1.0.140
1.43.0
->1.45.0
0.8.20
->0.8.22
Release Notes
dtolnay/async-trait (async-trait)
v0.1.88
Compare Source
v0.1.87
Compare Source
chronotope/chrono (chrono)
v0.4.41
Compare Source
What's Changed
subsec_micros
andsubsec_millis
methods toTimeDelta
by @ggoetz in https://github.com/chronotope/chrono/pull/1668NaiveDateTime::UNIX_EPOCH
by @robertbastian in https://github.com/chronotope/chrono/pull/1670as_seconds_f32
andas_seconds_f64
forTimeDelta
by @ggoetz in https://github.com/chronotope/chrono/pull/1671num_days_in_month
method toDatelike
trait by @aslilac in https://github.com/chronotope/chrono/pull/1673WeekdaySet
, a collection ofWeekday
that isCopy
by @Kinrany in https://github.com/chronotope/chrono/pull/1676clap-rs/clap (clap)
v4.5.38
Compare Source
Fixes
--
or-
v4.5.37
Compare Source
Features
ArgMatches::try_clear_id()
v4.5.36
Compare Source
Fixes
v4.5.35
Compare Source
Fixes
help_heading
v4.5.34
Compare Source
Fixes
flatten_help(true)
and subcommands without argumentsv4.5.33
Compare Source
Fixes
v4.5.32
Compare Source
Features
Error::remove
Documentation
humantime
tojiff
Internal
pulldown-cmark
dagger/dagger (dagger-sdk)
v0.18.7
Compare Source
Fixed
git
API calls consistently respect proxy settings by @jedevc in https://github.com/dagger/dagger/pull/10352Added
Query.http
by @jedevc in https://github.com/dagger/dagger/pull/10317name
allows overriding the filename to downloadpermissions
allows setting the permissions on the resulting fileauthHeader
allows passing a secret in theAuthorization
HTTP headerWhat to do next?
v0.18.6
Compare Source
🔥 Breaking Changes
Cache URI-based secrets based on their plaintext value rather than the URI by @sipsma in https://github.com/dagger/dagger/pull/10311
Previously, the "cache key" for URI-based secrets (e.g.
env://FOO
,file:///some/path
, etc.) was the URI string. This meant that operations including the secret (e.g. as an environment variable in a Container) would be cached based on the URI value. If two secrets from different clients had the same URI but different plaintext values, cache for operations that include them would be shared.In many cases, even when URIs were the same, the plaintext of secrets could be meaningfully different, which made this behavior surprising and lead to unexpected results.
Now, URI-based secrets are cached based on secure hashes of their plaintext value. Two secrets that have the same URI but different plaintext values will be cached separately, and operations that include them will not share cache.
However, there are cases where users do want secrets with different plaintexts to share cache, e.g. secrets that rotate in plaintext value frequently but aren't meaningfully different and thus shouldn't bust the cache of operations that include them.
To continue supporting those use cases, there is a new optional
cacheKey
argument toSecret
that can be used to specify a custom cache key. If provided, the cache key will be used instead of the default plaintext-based cache key, allowing any secrets sharing that cache-key to be cached together.SDKs can provide this as an optional argument to the
Secret
constructor. Other example usages:dagger shell:
dagger shell -c "some-function --secret-arg $(secret env://FOO --cache-key my-cache-key)"
dagger call (supports a special syntax that sets the cache key via a query param in the URI):
dagger call some-function --secret-arg env://FOO?cacheKey=my-cache-key
Added
GitRepository.branches
API by @jedevc in https://github.com/dagger/dagger/pull/10250File
top-level field added to allow easier creation ofFile
objects by @jedevc in https://github.com/dagger/dagger/pull/10290Fixed
GitRepository.tags
patterns
arg is now respected for local git repositories by @jedevc in https://github.com/dagger/dagger/pull/10250dagger call
by @helderco in https://github.com/dagger/dagger/pull/10305Container.build
with a Dockerfile that isFROM scratch
by @sipsma in https://github.com/dagger/dagger/pull/10332What to do next?
v0.18.5
Compare Source
Added
depth
arg toGitRef.tree
to control the depth of a clone by @jedevc in https://github.com/dagger/dagger/pull/9980GitRef.ref
field for resolving the full ref string for a reference by @jedevc in https://github.com/dagger/dagger/pull/9980Fixed
Git.tree
checkouts by @jedevc in https://github.com/dagger/dagger/pull/9980withExec
when secrets created bySetSecret
in function calls are included by @sipsma in https://github.com/dagger/dagger/pull/10260What to do next?
v0.18.4
Compare Source
Fixed
Directory
andFile
flags by @helderco in https://github.com/dagger/dagger/pull/10169CurrentModule
API during SDK module initialization by @sipsma in https://github.com/dagger/dagger/pull/10213llm.withModel
from a module function by @sipsma in https://github.com/dagger/dagger/pull/10230.plaintext
on a URI-based secret from a module w/ cache hit by @sipsma in https://github.com/dagger/dagger/pull/10223setSecret
provided empty plaintext value and passed between function calls by @sipsma in https://github.com/dagger/dagger/pull/10223Experimental
What to do next?
v0.18.3
Compare Source
Added
--recursive
flag fordagger develop
by @jedevc in https://github.com/dagger/dagger/pull/9860Container.build
andDirectory.dockerBuild
by @sipsma in https://github.com/dagger/dagger/pull/10088ttl
for local secret caching for vault by @rajatjindal in https://github.com/dagger/dagger/pull/9997Fixed
Experimental
What to do next?
v0.18.2
Compare Source
Changed
with-exec
positional arguments by @helderco in https://github.com/dagger/dagger/pull/10063Fixed
What to do next?
v0.18.1
Compare Source
What to do next?
v0.18.0
Compare Source
Changed
Fixed
What to do next?
v0.17.2
Compare Source
Added
Directory.filter
API for improved ergonomics by @rajatjindal in https://github.com/dagger/dagger/pull/9976This was previously possible by doing
Query.directory.withDirectory("", dir)
, but this breaks the chain.Changed
What to do next?
serde-rs/json (serde_json)
v1.0.140
Compare Source
tokio-rs/tokio (tokio)
v1.45.0
: Tokio v1.45.0Compare Source
Added
worker_total_busy_duration
,worker_park_count
, andworker_unpark_count
(#6899, #7276)Command::spawn_with
(#7249)Changed
Unpin
for some trait impls (#7204)runtime::Handle
as unwind safe (#7230)Unstable
v1.44.2
: Tokio v1.44.2Compare Source
This release fixes a soundness issue in the broadcast channel. The channel
accepts values that are
Send
but!Sync
. Previously, the channel calledclone()
on these values without synchronizing. This release fixes the channelby synchronizing calls to
.clone()
(Thanks Austin Bonander for finding andreporting the issue).
Fixed
clone()
call in broadcast channel (#7232)v1.44.1
: Tokio v1.44.1Compare Source
1.44.1 (March 13th, 2025)
Fixed
block_in_place
context (#7216)v1.44.0
: Tokio v1.44.0Compare Source
1.44.0 (March 7th, 2025)
This release changes the
from_std
method on sockets to panic if a blocking socket is provided. We determined this change is not a breaking change as Tokio is not intended to operate using blocking sockets. Doing so results in runtime hangs and should be considered a bug. Accidentally passing a blocking socket to Tokio is one of the most common user mistakes. If this change causes an issue for you, please comment on #7172.Added
task::coop
module (#7116)Command::get_kill_on_drop()
(#7086)broadcast::Sender::closed
(#6685, #7090)broadcast::WeakSender
(#7100)oneshot::Receiver::is_empty()
(#7153)oneshot::Receiver::is_terminated()
(#7152)Fixed
File
should not start a background read (#7139)start_kill
on exited child should not fail (#7160)CTRL_CLOSE
,CTRL_LOGOFF
,CTRL_SHUTDOWN
on windows (#7122)Changes
select!
budget-aware (#7164)from_std
(#7166)Changes to unstable APIs
Documented
select!
alternatives (#7110)send_to
(#7146)Child
stdout (#7141)Child::kill
behavior (#7162)ChildStdin
struct doc comment (#7192)worker_threads
instead ofcore_threads
(#7186)v1.43.1
Compare Source
toml-rs/toml (toml)
v0.8.22
Compare Source
v0.8.21
Compare Source
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR is behind base branch, 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.
0a3667bf78
to3cdde7ab4a
3cdde7ab4a
toe26990818a
e26990818a
to704b47d12c
704b47d12c
toe4f996572c
e4f996572c
tod93f08e3f3
d93f08e3f3
toacc9c407a9
acc9c407a9
tofc06c9b024
chore(deps): update all dependenciesto fix(deps): update all dependenciesfc06c9b024
to218f41c443
218f41c443
tod88effc1b6
d88effc1b6
to5e72dca282
5e72dca282
to0a6447ca19
0a6447ca19
to8dc9ea8a0a
8dc9ea8a0a
to175d195512
175d195512
to56b98c1970
56b98c1970
toa1f1cddf63
a1f1cddf63
to4ca0d402af
4ca0d402af
to13bfc6eeca
13bfc6eeca
to5014bfc9cd
5014bfc9cd
toea70cef092
ea70cef092
tofd835dc875
fd835dc875
to5bba4d6155
5bba4d6155
to22b4a0bd99
22b4a0bd99
to5413b0b989
5413b0b989
to9ebf8d8d9f
9ebf8d8d9f
toed9177e11f
ed9177e11f
to2283b0b1d2
2283b0b1d2
to356a6499a4
356a6499a4
to9908f4e459
9908f4e459
to6a9834253a
6a9834253a
to1570391225
1570391225
to8fb312140f
8fb312140f
toce78e944a2
ce78e944a2
to0009a5d569
0009a5d569
tof7c51be48d
f7c51be48d
tofd21b3b68c
fd21b3b68c
toba6c1e86b4
ba6c1e86b4
tob341ce66de
b341ce66de
to6689ac7202
6689ac7202
tod50e6ae0e1
d50e6ae0e1
toa90b35c031
a90b35c031
to5a82e1bc17
5a82e1bc17
todfe1e941d4
dfe1e941d4
toebcb6fbe18
ebcb6fbe18
toedeec6c447
edeec6c447
tod2a3e6ce7f
Checkout
From your project repository, check out a new branch and test the changes.