chore(deps): update dependency dagger/dagger to v0.15.1 #53
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:
0.14.0->0.15.1Release Notes
dagger/dagger (dagger/dagger)
v0.15.1Compare Source
Fixed
What to do next?
v0.15.0Compare Source
🔥 Breaking Changes
Container.asServicenow uses the command specified bywithDefaultArgsinstead of the lastwithExeccommand by @rajatjindal in https://github.com/dagger/dagger/pull/8865Users can override the args by providing the
argsoption toasService.They can also configure the container to use the container entrypoint by using
useEntrypointoption.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.jsonconfig 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.tomlfile 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.jsonwhen 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 uninstallcommand 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_ENGINEenvironment variable to optionally prevent removal of old engine containers during upgrades by devin in https://github.com/dagger/dagger/pull/8195Fixed
Directory.terminalAPI works now by @sipsma in https://github.com/dagger/dagger/pull/8952Container.withExecexpectto catch exit code 128 by @jedevc in https://github.com/dagger/dagger/pull/9027Directory.digestby @jedevc in https://github.com/dagger/dagger/pull/8946What 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 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.