chore(deps): update dependency dagger/dagger to v0.21.9 - #1079
Merged
Conversation
![renovate-approve[bot]](https://avatars.githubusercontent.com/in/7394?s=60&v=4){kind=small}
mnencia
approved these changes
Aug 27, 2026
| datasource | package | from | to | | ----------- | ------------- | ------- | ------- | | github-tags | dagger/dagger | v0.21.8 | v0.21.9 | Signed-off-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
renovate
Bot
force-pushed
the
renovate/dagger-dagger-0.x
branch
from
August 27, 2026 12:59
746e0e0 to
891f315
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.21.8→0.21.9Release Notes
dagger/dagger (dagger/dagger)
v0.21.9Compare Source
v0.21.9 - 2026-08-25
Added
Fixed
Container.withDirectoryandDirectory.withDirectoryno longer restore by @sipsma in #13848deleted nested files after execs remove and recreate an ancestor
directory.
initialization or teardown, preventing Cloud keeper heartbeats from stalling
and live engines from being suspended.
preventing shutdown responses from timing out while the engine releases
session-owned cache results.
usage by pruning cold persisted results when the structural estimate exceeds
its configured limit. This may mitigate metadata growth at scale while
preserving active and engine-lifetime cache roots.
when image pulls or publishes succeed, while genuine registry failures remain
visible.
Container.fromby @sipsma in #13901What to do next?
Configuration
📅 Schedule: (UTC)
🚦 Automerge: Enabled.
♻ Rebasing: Never, 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.