Dagger Release Notes

core: give each entrypoint call a fresh call digest

After a function's TTL expired, the exec that the entrypoint keyed on the unchanged call digest answered from cache, so the function returned its old result without running.

Signed-off-by: Yves Brissaud [email protected]

core: give only explicit-TTL calls a fresh digest

A fresh digest on every evaluation re-ran the user's code each time dagql evaluated a call again, such as after a prune, even when the function sets no explicit TTL.

Signed-off-by: Yves Brissaud [email protected]

core: reduce ModuleFunction.Call complexity

Signed-off-by: Yves Brissaud [email protected]

Signed-off-by: Yves Brissaud [email protected]

v0.21.10 - 2026-09-30

Added

• Add opt-in engine CPU and memory telemetry from cgroup v2 by @matipan in #14285
  • Enable telemetry.resourceMetrics in /etc/dagger/engine.json and set OTEL_EXPORTER_OTLP_METRICS_ENDPOINT in the engine environment. The new resource metrics use a separate OTLP export path. Client telemetry is unchanged, and engine resource telemetry is disabled by default.

Fixed

• Container.withServiceBinding now works for a service whose custom hostname by @Zaba505 in #13751 was scoped to another module's DNS domain. A service created with withHostname is namespaced into the domain of whichever module first starts it, so a module that started its own service before handing it to a caller left that caller's withExec failing at hosts-file setup with lookup <hostname> ... no such host. Binding the service explicitly now resolves it by the name it actually registered under. Reaching a module's custom hostname by bare DNS remains scoped to that module.
• dag.CurrentModule().Source() and dag.CurrentModule().GeneratedContextDirectory() by @marcosnils in https://github.com/dagger/dagger/pull/ no longer re-resolve the running module's declared dependencies. The module's already-loaded dependency DAG is reused for codegen, so these APIs now work in modules whose dependencies point at private git repositories even when the runtime caller does not hold the author's credentials.

Contributors

Special thanks to our external contributors this release!

• @Zaba505

What to do next?

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