fix(deps): update all dependencies #15
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.98
0.1.85
->0.1.88
4.5.27
->4.5.40
0.13.7
->0.18.0
1.43.0
->1.46.1
Release Notes
dtolnay/anyhow (anyhow)
v1.0.98
Compare Source
self.into_boxed_dyn_error()
andself.reallocate_into_boxed_dyn_error_without_backtrace()
methods for anyhow::Error (#415)v1.0.97
Compare Source
v1.0.96
Compare Source
dtolnay/async-trait (async-trait)
v0.1.88
Compare Source
v0.1.87
Compare Source
v0.1.86
Compare Source
clap-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
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
assertionsv4.5.29
Compare Source
Fixes
ArgMatches::args_present
so not-present flags are considered not-present (matching the documentation)v4.5.28
Compare Source
Features
unstable-markdown
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?
v0.17.1
Compare Source
dag.Llm
. To fix, simply change todag.LLM
What to do next?
v0.17.0
Compare Source
Added
Stabilized Dagger Shell by @helderco in https://github.com/dagger/dagger/pull/9896
Find out more at https://docs.dagger.io/features/shell/
New top-level
LLM
API to allow integrating LLMs with native Dagger types in https://github.com/dagger/dagger/pull/9628Find out more at https://docs.dagger.io/ai-agents/
Changed
/run/dagger/engine.sock
by @sipsma in https://github.com/dagger/dagger/pull/9866The previous socket path still exists for backwards compatibility but may be removed in a future version.
Directory.glob
andDirectory.entries
now return a trailing slash to distinguish from regular files by @jedevc in https://github.com/dagger/dagger/pull/9118What to do next?
v0.16.3
Compare Source
Added
Directory.asGit
API for converting a directory into a git repository by @jedevc in https://github.com/dagger/dagger/pull/9730dagger call
forGitRepository
andGitRef
types by @jedevc in https://github.com/dagger/dagger/pull/9844Container.asTarball
by @jedevc in https://github.com/dagger/dagger/pull/9395Changed
Dependencies
What to do next?
v0.16.2
Compare Source
Added
Directory.name
field to retrieve current directory name by @TomChv in https://github.com/dagger/dagger/pull/9617Fixed
dagger call
ordagger functions
called in directory with no modules - it now errors cleanly by @sipsma in https://github.com/dagger/dagger/pull/9658dagger.json
by @sipsma in https://github.com/dagger/dagger/pull/9659Dependencies
What to do next?
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?
tokio-rs/tokio (tokio)
v1.46.1
: Tokio v1.46.1Compare Source
1.46.1 (July 4th, 2025)
This release fixes incorrect spawn locations in runtime task hooks for tasks
spawned using
tokio::spawn
rather thanRuntime::spawn
. This issue onlyeffected the spawn location in
TaskMeta::spawned_at
, and did not effect tasklocations in Tracing events.
Unstable
TaskMeta::spawn_location
tracking where a task was spawned(#7440)
v1.46.0
: Tokio v1.46.0Compare Source
1.46.0 (July 2nd, 2025)
Fixed
TcpStream::shutdown
incorrectly returning an error on macOS (#7290)Added
mpsc::OwnedPermit::{same_channel, same_channel_as_sender}
methods (#7389)biased
option forjoin!
andtry_join!
, similar toselect!
(#7307)pope::OpenOptions::read_write
on Android (#7426)Clone
implementation fornet::unix::SocketAddr
(#7422)Changed
queue::Local<T>
(#7340)LocalSet::{poll,drop}
(#7372)Unstable
TaskMeta::spawn_location
tracking where a task was spawned (#7417)LocalOptions
parameter toruntime::Builder::build_local
(#7346)Documented
start_seek
is not used (#7366)AsyncWriteExt::flush
(#7364)recv_buffer_size
method (#7336)RawFd
inTcpSocket
docs (#7416)AsRawFd
doc link to current Rust stdlib location (#7429)on_*_task_poll
is unstable (#7311)time::advance
(#7394)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
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.
fix(deps): update rust crate dagger-sdk to 0.15.0to fix(deps): update all dependenciesa31238c9db
toab0e65d9f6
ab0e65d9f6
to8b6f3808c4
8b6f3808c4
to9fd9a657c2
9fd9a657c2
to6cd9ec3de6
6cd9ec3de6
tof3a6c12a46
f3a6c12a46
to3488e222fa
3488e222fa
to061cfca40a
061cfca40a
toef8aa39b17
ef8aa39b17
tob7796179b1
b7796179b1
tobfcb16c4e7
bfcb16c4e7
to13abeb3b81
fix(deps): update all dependenciesto chore(deps): update all dependencies13abeb3b81
toe5bae2893a
e5bae2893a
to02d70fbc0a
02d70fbc0a
toe1b3e7faa7
e1b3e7faa7
to3ba9e44587
3ba9e44587
to9432f8596d
9432f8596d
to57a2f60d0e
chore(deps): update all dependenciesto fix(deps): update all dependencies57a2f60d0e
to0ebe91a5ad
0ebe91a5ad
to67ca681ca7
67ca681ca7
to6eed479582
6eed479582
tob08ab388bb
b08ab388bb
toa5334b23d9
a5334b23d9
to3330d45803
3330d45803
to58720a0fba
58720a0fba
to456aa85f54
456aa85f54
to1905c7d654
1905c7d654
toffc96e592f
ffc96e592f
toeb54fda419
eb54fda419
to5bcc0de987
5bcc0de987
tob24ef08cc9
b24ef08cc9
tob0779c826e
b0779c826e
to6fd8bd606d
6fd8bd606d
to1034885a1b
1034885a1b
to1f7c2e9b71
1f7c2e9b71
to84418f0c69
84418f0c69
tobaba3e15d6
baba3e15d6
tob27135c508
b27135c508
to018d20b89b
018d20b89b
to2a13658a2e
2a13658a2e
toad2ab24a1a
ad2ab24a1a
to337f6d668d
337f6d668d
todf83f15373
df83f15373
to49d9849566
49d9849566
toeac93e9e14
eac93e9e14
toebc69d727d
⚠️ Artifact update problem
Renovate failed to update artifacts 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
File name: Cargo.lock
Checkout
From your project repository, check out a new branch and test the changes.