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.40
0.17.1
->0.18.0
1.0.139
->1.0.140
1.43.0
->1.45.1
0.8.20
->0.8.23
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.40
Compare Source
Features
arg!()
macro (e.g.arg!("check-config": ...)
)v4.5.39
Compare Source
Fixes
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.12
Compare Source
Changed
OrbStack users were by default ending up with a custom CA in their engine and automatically installed in each container, adding overhead. We now ignore that CA cert by default to improve performance in the default case.
Fixed
What to do next?
v0.18.11
Compare Source
🔥 Breaking Changes
value) for SDKs that support enum members (see SDK-specific release notes).
This may break loading modules (including in compat mode) that were
previously setting enum default values in function signatures, if those values
weren't valid - these would only trigger an error on calling that function,
while now it's triggered during module initialization.
namespace
argument fromCacheVolume
by @sipsma in https://github.com/dagger/dagger/pull/10586This arg was only ever meant for internal usage within the API's
implementation, but previously couldn't be hidden from the public API. Now it
is properly internal-only and thus not accessible to external clients. Any use
of the arg should just be removed.
sweep
engine option name tosweepSize
by @jedevc in https://github.com/dagger/dagger/pull/10560This option was previously incorrectly named - the docs were correct, but the
code was not properly updated.
Added
New top-level
cloud
API for getting information about the dagger cloud session by @marcosnils in https://github.com/dagger/dagger/pull/10580This includes the
cloud.traceURL
field for getting the current trace URL.Allow
--no-mod
/-M
flag in more places to disable automatic module loading by @jedevc in https://github.com/dagger/dagger/pull/10595Propagate exit codes properly in shell by @helderco in https://github.com/dagger/dagger/pull/10438
The
.exit
builtin was added.The
.wait
builtin now accepts a list of job ids to wait for. For example:The above example should exit with status code 1 because
.wait
returnsthe exit of the first command that failed. This is different from Bash
which returns the exit status of the last command in the list, even if
it succeeded when others have failed.
Add
httpAuthUsername
parameter togit
to allow basic auth with usernames by @grouville in https://github.com/dagger/dagger/pull/10605Additionally this field is populated from the client's git credential helper,
similarly to passwords.
You can now set
$DAGGER_PROGRESS
to configure your preferred progress format globally, instead of passing the--progress
flag every time by @vito in https://github.com/dagger/dagger/pull/10617Added a new
dots
progress format, which is a much quieter alternative toplain
suitable for use in CI by @vito in https://github.com/dagger/dagger/pull/10617This format focuses on printing logs and reduces everything else to just
green dots and red Xes for success/failure, similar to test runners like RSpec.
Demo
Changed
.help <module>
by @helderco in https://github.com/dagger/dagger/pull/10487ExecError
so you can see the stdout/stderr and exit code programmatically by @vito in https://github.com/dagger/dagger/pull/10585Fixed
In one scenario this reduced heap usage from 14GB to 7GB.
In the same scenario as the high log volume fix, this further reduced heap usage from 7GB to 1.4GB.
plain
progress format being way more verbose than intended by @vito in https://github.com/dagger/dagger/pull/10636Directory.withSymlink
accidentally escaping from the selected sub-directory by @alexcb in https://github.com/dagger/dagger/pull/10563What to do next?
v0.18.10
Compare Source
Added
Improved TUI progress visualizer by @vito in https://github.com/dagger/dagger/pull/10468
Added
E
hotkey in TUI for-E
/--no-exit
at runtime by @vito in https://github.com/dagger/dagger/pull/10511Add support for using engine-wide default GC policy when triggering manual local cache prunes by @sipsma in https://github.com/dagger/dagger/pull/10505
The manual prune API now supports an optional arg to enable honoring the engine-wide default automatic GC configuration. e.g.
dagger core engine local-cache prune --use-default-policy
New
container.WithSymlink
anddirectory.WithSymlink
API for creating symbolic links by @alexcb in https://github.com/dagger/dagger/pull/10435Unbundle the SDK interface to support partial implementation by @TomChv in https://github.com/dagger/dagger/pull/10525
When you implement a custom SDK, you can now choose to just implement part of the
SDK
interface depending on your needs.That means:
dagger develop
no longer fails if your SDK just implement theRuntime
interface, it will simply not callCodegen
if not defined.dagger call
anddagger functions
give a clear error message if it's not supported by the SDK.See https://github.com/dagger/dagger/issues/7707 for more information.
Fixed
Dependencies
What to do next?
v0.18.9
Compare Source
Added
gc.sweepSize
setting forengine.json
by @jedevc in https://github.com/dagger/dagger/pull/10420This setting allows controlling how much data to clear in a single GC sweep.
Changed
noCache
arg toHost.directory
to auto reload contextual directories in persistent shell/prompt sessions by @cwlbraa in https://github.com/dagger/dagger/pull/10342Fixed
_
prefix not being reserved for interpreter builtins by @helderco in https://github.com/dagger/dagger/pull/10452What to do next?
v0.18.8
Compare Source
Fixed
What to do next?
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
Changed
OrbStack users were by default ending up with a custom CA in their engine and automatically installed in each container, adding overhead. We now ignore that CA cert by default to improve performance in the default case.
Fixed
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.1
: Tokio v1.45.1Compare Source
1.45.1 (May 24th, 2025)
This fixes a regression on the wasm32-unknown-unknown target, where code that previously did not panic due to calls to
Instant::now()
started failing. This is due to the stabilization of the first time-based metric.Fixed
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.23
Compare Source
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
d2a3e6ce7f
tod982c41e18
d982c41e18
toad571f15b4
ad571f15b4
to2012f43f27
2012f43f27
tob46c2d8d3e
b46c2d8d3e
to776118eed0
776118eed0
to7a92ef4282
7a92ef4282
to16e905f2e7
16e905f2e7
to03d0445cfc
03d0445cfc
to02cbe5ecea
02cbe5ecea
tod34f569c57
d34f569c57
toc1d25534cd
c1d25534cd
tobd56187527
bd56187527
to96a02f3945
96a02f3945
to2719cb8714
2719cb8714
to1b4f870032
1b4f870032
to305453e736
305453e736
to078185df04
078185df04
to860a951c90
860a951c90
tob4eff8d1c5
b4eff8d1c5
to9d93c98e00
9d93c98e00
to887e587afe
887e587afe
to135e2abfcb
135e2abfcb
to9343300c34
9343300c34
to152c078528
152c078528
toc18a300135
c18a300135
to8c049ce83f
8c049ce83f
to52887d9123
52887d9123
to88e8e94cfa
88e8e94cfa
tod769441962
d769441962
to8e246e2a1d
8e246e2a1d
tof7db60a0e7
f7db60a0e7
to4895b5395d
4895b5395d
toefaf7a4fe7
efaf7a4fe7
tob7feb3c1bf
b7feb3c1bf
to93c8c3eac5
93c8c3eac5
tocb949cbb1e
cb949cbb1e
tob9bc72707e
b9bc72707e
to7561a2fd4a
7561a2fd4a
toeedf1264e5
eedf1264e5
to68441af163
68441af163
to6596884dca
6596884dca
toe85ae1f477
e85ae1f477
to3802323f23
3802323f23
to450938fc41
450938fc41
to9d7cca0178
9d7cca0178
to734382d2bf
734382d2bf
to9fdb61d56b
9fdb61d56b
to410552ed67
410552ed67
tod6e0eac3cd
d6e0eac3cd
to911b62536e
911b62536e
to2db9093776
2db9093776
toe833b231b8
e833b231b8
toc2cc8d69d3
c2cc8d69d3
to205933cb61
205933cb61
to0d58749a61
0d58749a61
to7ca55ca9e3
7ca55ca9e3
tobedd675160
bedd675160
to5090c1af69
5090c1af69
toe8080bfc65
e8080bfc65
to34a18d74ae
34a18d74ae
tof61530f41d
f61530f41d
to16683588f7
16683588f7
to760414aaf8
760414aaf8
to3bad2b16ab
3bad2b16ab
to6b6273eea6
6b6273eea6
tob9b346d62f
b9b346d62f
to6951f4eeda
6951f4eeda
to0de76f60e5
0de76f60e5
toee086896c2
ee086896c2
tobacb0a6c67
bacb0a6c67
toc9f2d9caad
c9f2d9caad
to3e42c02158
3e42c02158
to3ddee2e210
3ddee2e210
to5936f7663c
5936f7663c
to01afefb3cc
01afefb3cc
tof37a63ed1d
f37a63ed1d
to7a682139e9
7a682139e9
toafb11b196e
afb11b196e
toac500cfed3
ac500cfed3
toad2ef01830
ad2ef01830
to1b34afe884
1b34afe884
to7652a48f34
7652a48f34
to3584ca52f5
3584ca52f5
to5b60f6afb2
5b60f6afb2
tof20d981d31
f20d981d31
tob073f4586e
Checkout
From your project repository, check out a new branch and test the changes.