chore(deps): update ⬆️ dagger to v0.15.1 #35
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
v0.14.0
->v0.15.1
Release Notes
dagger/dagger (dagger/dagger)
v0.15.1
Compare Source
Fixed
What to do next?
v0.15.0
Compare Source
🔥 Breaking Changes
Container.asService
now uses the command specified bywithDefaultArgs
instead of the lastwithExec
command by @rajatjindal in https://github.com/dagger/dagger/pull/8865Users can override the args by providing the
args
option toasService
.They can also configure the container to use the container entrypoint by using
useEntrypoint
option.Added
Better TUI errors, new cached/pending states, duration accounting and fewer spans by @vito in https://github.com/dagger/dagger/pull/8442
Custom dagger
engine.json
config file by @jedevc in https://github.com/dagger/dagger/pull/8800This new config file format is intended to eventually replace the old
buildkit-style
engine.toml
file that's currently used for configuration.This file can be either mounted directly into a manually started engine at
/etc/dagger/engine.toml
, or it will automatically mounted from theuser's
~/.config/dagger/engine.json
when the engine is started.Filesync performance is improved by @sipsma in https://github.com/dagger/dagger/pull/8818
The engine now re-uses previously loaded data more reliably and in more
cases, which speeds up repeated reloads of the same or similar (i.e.
overlapping data).
Uncached filesyncs of large amounts of data is also faster and uses less
memory in the engine.
Added
dagger uninstall
command to remove a dependency by @rajatjindal in https://github.com/dagger/dagger/pull/8745Added memory and network telemetry for execs by @cwlbraa in https://github.com/dagger/dagger/pull/8880 https://github.com/dagger/dagger/pull/8902
Added
DAGGER_LEAVE_OLD_ENGINE
environment variable to optionally prevent removal of old engine containers during upgrades by devin in https://github.com/dagger/dagger/pull/8195Fixed
Directory.terminal
API works now by @sipsma in https://github.com/dagger/dagger/pull/8952Container.withExec
expect
to catch exit code 128 by @jedevc in https://github.com/dagger/dagger/pull/9027Directory.digest
by @jedevc in https://github.com/dagger/dagger/pull/8946What to do next?
Configuration
📅 Schedule: Branch creation - "after 4pm on thursday" in timezone America/Los_Angeles, Automerge - At any time (no schedule defined).
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.