chore(deps): update all dependencies - autoclosed #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.87
4.5.26
->4.5.31
0.15.0
->0.16.0
Release Notes
dtolnay/anyhow (anyhow)
v1.0.97
Compare Source
v1.0.96
Compare Source
dtolnay/async-trait (async-trait)
v0.1.87
Compare Source
v0.1.86
Compare Source
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
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
v4.5.27
Compare Source
Documentation
dagger/dagger (dagger-sdk)
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?
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.
fix(deps): update rust crate dagger-sdk to v0.15.2to chore(deps): update all dependencies7abb99d61d
to9581d7c3a7
9581d7c3a7
to83e17a19fa
83e17a19fa
tofe6b47ecf1
fe6b47ecf1
to88f03f6c28
88f03f6c28
to6ce0fa0352
6ce0fa0352
to4c472e3298
4c472e3298
to6c7134ea60
6c7134ea60
to34168930e3
34168930e3
to1e04fac362
1e04fac362
to2a4ce623d2
2a4ce623d2
to30a3fe041a
30a3fe041a
to6732f4de1f
6732f4de1f
to11ff98b8d8
11ff98b8d8
to71c09f96a3
71c09f96a3
toa5a4cbc437
a5a4cbc437
toc7dddce1ba
c7dddce1ba
to5d65755509
5d65755509
to83f062051d
83f062051d
to9a39329dc3
chore(deps): update all dependenciesto fix(deps): update all dependencies9a39329dc3
to434c510dec
434c510dec
to3879017940
3879017940
toe1a7078138
e1a7078138
toc43eef4d84
c43eef4d84
toc873253503
c873253503
tof87916cfeb
f87916cfeb
to85d5cb1541
85d5cb1541
to5fe2700421
5fe2700421
to269ee93fee
269ee93fee
to8bcb14bcf0
8bcb14bcf0
tofae9ab3729
fae9ab3729
to6dcfd30306
6dcfd30306
tof1b003a278
f1b003a278
to9b2f89dc1a
9b2f89dc1a
toaaf68ab39f
aaf68ab39f
toe565259e71
e565259e71
to99cb0f28c9
99cb0f28c9
to4e43923373
4e43923373
to4516b9537e
4516b9537e
toed336d00d0
ed336d00d0
to709c6ca3e2
709c6ca3e2
to021b77c846
021b77c846
to57e3ac9ccc
57e3ac9ccc
to28edb32165
28edb32165
toe810204400
e810204400
tob5ca1aa3fc
b5ca1aa3fc
todfcb52b529
dfcb52b529
to161a790f39
161a790f39
to19c59e4558
fix(deps): update all dependenciesto chore(deps): update all dependencies19c59e4558
to6489b3cf7a
6489b3cf7a
to2f53a1f354
2f53a1f354
to0e8297b1d9
⚠️ 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
0e8297b1d9
toc6ebac5263
c6ebac5263
to53e2b75469
53e2b75469
to4f5564a9f3
chore(deps): update all dependenciesto chore(deps): update all dependencies - autoclosedPull request closed