Back to Dagger

V0.21.9

.changes/v0.21.9.md

0.21.91.9 KB
Original Source

v0.21.9 - 2026-08-25

Added

Fixed

  • Container.withDirectory and Directory.withDirectory no longer restore by @sipsma in https://github.com/dagger/dagger/pull/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 https://github.com/dagger/dagger/pull/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 https://github.com/dagger/dagger/pull/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 https://github.com/dagger/dagger/pull/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 https://github.com/dagger/dagger/pull/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 https://github.com/dagger/dagger/pull/13901

What to do next?