chore(deps): update all dependencies - autoclosed #15
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.970.1.85->0.1.874.5.26->4.5.310.15.0->0.16.0Release Notes
dtolnay/anyhow (anyhow)
v1.0.97Compare Source
v1.0.96Compare Source
dtolnay/async-trait (async-trait)
v0.1.87Compare Source
v0.1.86Compare Source
clap-rs/clap (clap)
v4.5.31Compare Source
Features
ValueParserFactoryforSaturating<T>v4.5.30Compare Source
Fixes
num_args(0..=1)to be used withSetTruetakes_valuesassertionsv4.5.29Compare Source
Fixes
ArgMatches::args_presentso not-present flags are considered not-present (matching the documentation)v4.5.28Compare Source
Features
unstable-markdownv4.5.27Compare Source
Documentation
dagger/dagger (dagger-sdk)
v0.16.2Compare Source
Added
Directory.namefield to retrieve current directory name by @TomChv in https://github.com/dagger/dagger/pull/9617Fixed
dagger callordagger functionscalled in directory with no modules - it now errors cleanly by @sipsma in https://github.com/dagger/dagger/pull/9658dagger.jsonby @sipsma in https://github.com/dagger/dagger/pull/9659Dependencies
What to do next?
v0.16.1Compare Source
Fixed
cannot sub-select 1th item from *dagql.PostCallTypedby @sipsma in https://github.com/dagger/dagger/pull/9634What to do next?
v0.16.0Compare Source
🔥 Breaking Changes
To match automatic configuration,
insecure-entitlementsnow includessecurity.insecurewhen 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 modulestep 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 moduletimes for thedagger-dev's module in Dagger's repository under different scenarios:dagger call --helpon new engines with an empty cachedagger call --helpwith no file changes in the repo:dagger call --helpafter 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 moduletimes 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
.daggerand relies on thego.modfile in the parent directory, you would add the following to yourdagger.jsonfile: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").excludesetting existed but has now been superseded by prefixing an include pattern with a!character. However, this is backwards-compatible, so existingexcludesettings will be automatically turned into equivalent!-prefixed include settings when runningdagger develop. No user intervention is needed.The core API's
ModuleSourceandModuletypes 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.initializeno longer needs to be called; the module is initialized on creationResolveFromCallerno longer needs to be called for local module sources; context is automatically loaded and resolved efficiently as needed by other API callsAdded
dag.Hostoperations by @jedevc in https://github.com/dagger/dagger/pull/9610What to do next?
v0.15.4Compare Source
Added
dagger.jsonsdkfield tosdk.sourceby @rajatjindal in https://github.com/dagger/dagger/pull/9454Fixed
What to do next?
v0.15.3Compare Source
Added
Note: the precision of float is limited to float64 inside the engine.
Fixed
Container.WithFilesby @jedevc in https://github.com/dagger/dagger/pull/9457Dependencies
What to do next?
v0.15.2Compare Source
Added
dagger updatecommand to update dependencies indagger.jsonby @rajatjindal in https://github.com/dagger/dagger/pull/8839$schemaproperty indagger.jsonby @JacobLey in https://github.com/dagger/dagger/pull/9069Changed
CacheVolumesare now namespaced between different modules by @rajatjindal in https://github.com/dagger/dagger/pull/8724CACHEDoperations for--progress=plainoutput by @marcosnils in https://github.com/dagger/dagger/pull/9344Fixed
AsServiceby @marcosnils in https://github.com/dagger/dagger/pull/9247Container.terminalby @jedevc in https://github.com/dagger/dagger/pull/9338Container.upbehaves as identically as possible toContainer.AsService.upby @jedevc in https://github.com/dagger/dagger/pull/9231dagger installalways 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 dependencies7abb99d61dto9581d7c3a79581d7c3a7to83e17a19fa83e17a19fatofe6b47ecf1fe6b47ecf1to88f03f6c2888f03f6c28to6ce0fa03526ce0fa0352to4c472e32984c472e3298to6c7134ea606c7134ea60to34168930e334168930e3to1e04fac3621e04fac362to2a4ce623d22a4ce623d2to30a3fe041a30a3fe041ato6732f4de1f6732f4de1fto11ff98b8d811ff98b8d8to71c09f96a371c09f96a3toa5a4cbc437a5a4cbc437toc7dddce1bac7dddce1bato5d657555095d65755509to83f062051d83f062051dto9a39329dc3chore(deps): update all dependenciesto fix(deps): update all dependencies9a39329dc3to434c510dec434c510decto38790179403879017940toe1a7078138e1a7078138toc43eef4d84c43eef4d84toc873253503c873253503tof87916cfebf87916cfebto85d5cb154185d5cb1541to5fe27004215fe2700421to269ee93fee269ee93feeto8bcb14bcf08bcb14bcf0tofae9ab3729fae9ab3729to6dcfd303066dcfd30306tof1b003a278f1b003a278to9b2f89dc1a9b2f89dc1atoaaf68ab39faaf68ab39ftoe565259e71e565259e71to99cb0f28c999cb0f28c9to4e439233734e43923373to4516b9537e4516b9537etoed336d00d0ed336d00d0to709c6ca3e2709c6ca3e2to021b77c846021b77c846to57e3ac9ccc57e3ac9cccto28edb3216528edb32165toe810204400e810204400tob5ca1aa3fcb5ca1aa3fctodfcb52b529dfcb52b529to161a790f39161a790f39to19c59e4558fix(deps): update all dependenciesto chore(deps): update all dependencies19c59e4558to6489b3cf7a6489b3cf7ato2f53a1f3542f53a1f354to0e8297b1d9⚠️ 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
0e8297b1d9toc6ebac5263c6ebac5263to53e2b7546953e2b75469to4f5564a9f3chore(deps): update all dependenciesto chore(deps): update all dependencies - autoclosedPull request closed