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.97
0.1.85
->0.1.88
4.5.27
->4.5.36
0.13.7
->0.18.0
1.43.0
->1.44.2
Release Notes
dtolnay/anyhow (anyhow)
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.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.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?
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.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
⚠️ 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
1905c7d654
toffc96e592f
Checkout
From your project repository, check out a new branch and test the changes.