chore(deps): update dependency dagger/dagger to v0.21.9

[renovate]

This PR contains the following updates:

Package	Update	Change
dagger/dagger	patch	0.21.7 → 0.21.9

---

Release Notes

dagger/dagger (dagger/dagger)

v0.21.9

Compare Source

v0.21.9 - 2026-08-25

Added

• Added SSHFS-backed volumes, allowing remote filesystems to be mounted into containers without copying their contents into Dagger's content store by @​sipsma in #​13462

Fixed

• Container.withDirectory and Directory.withDirectory no longer restore by @​sipsma in #​13848
  deleted nested files after execs remove and recreate an ancestor
  directory.
• Engine client enumeration no longer blocks behind another session's by @​sipsma in #​13542
  initialization or teardown, preventing Cloud keeper heartbeats from stalling
  and live engines from being suspended.
• Session teardown now runs in the background after the main client disconnects, by @​sipsma in #​13681
  preventing shutdown responses from timing out while the engine releases
  session-owned cache results.
• The engine now bounds retained DAGQL cache metadata independently of disk by @​sipsma in #​13846
  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.
• Registry protocol probes no longer appear as scary errors in progress output by @​vito in #​13410
  when image pulls or publishes succeed, while genuine registry failures remain
  visible.
• Registry authentication no longer invalidates downstream container cache reuse across sessions when applied before or after Container.from by @​sipsma in #​13901

What to do next?

• Read the documentation
• Join our Discord server
• Follow us on Twitter

v0.21.8

Compare Source

v0.21.8 - 2026-07-29

Changed

• Changeset diffs are now computed from filesystem metadata instead of full-content comparison, significantly speeding up diff computation for large directories. by @​marcosnils in
  #​13615

Fixed

• Dockerfile build layer caching so unrelated build-context changes no longer bust the cache: COPY-ed directories now get a content-based cache identity, re-keying downstream steps only when copied content
  actually changes. by @​marcosnils in #​13765
• The --x-release CLI re-exec so _EXPERIMENTAL_DAGGER_RUNNER_HOST is preserved (with a warning) instead of being stripped, and clarified its startup message to avoid implying it runs from any build. by
  @​tiborvass in #​13752
• Silent SDK sessions no longer retain frontend telemetry in memory while Cloud and OTLP export remain enabled. DAGGER_SILENT is now honored as the equivalent of --silent. by @​sipsma in
  #​13762

What to do next?

• Read the documentation
• Join our Discord server
• Follow us on Twitter

---

Configuration

📅 Schedule: (UTC)

• 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.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.