[dependabot]

Bumps the python group with 1 update in the / directory: dagger-io.

Updates dagger-io from 0.21.9 to 0.21.10

Release notes

Sourced from dagger-io's releases.

helm/chart/v0.21.10 - 2026-09-30

Dependencies

• Bump Engine to v0.21.10 by @​matipan in dagger/dagger#14422

What to do next?

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

sdk/elixir/v0.21.10 - 2026-09-30

This SDK uses 🚙 Engine + 🚗 CLI version v0.21.10. See what changed in that release.

🧪 https://hex.pm/packages/dagger 📖 https://hexdocs.pm/dagger/Dagger.html

Dependencies

• Bump Engine to v0.21.10 by @​matipan in dagger/dagger#14422

What to do next

• Join our Discord server
• Follow us on Twitter

sdk/go/v0.21.10 - 2026-09-30

This SDK uses 🚙 Engine + 🚗 CLI version v0.21.10. See what changed in that release.

🐹 https://pkg.go.dev/dagger.io/dagger@v0.21.10

Dependencies

• Bump Engine to v0.21.10 by @​matipan in dagger/dagger#14422

What to do next

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

sdk/php/v0.21.10 - 2026-09-30

This SDK uses 🚙 Engine + 🚗 CLI version v0.21.10. See what changed in that release.

🐘 https://packagist.org/packages/dagger/dagger#v0.21.10

Dependencies

• Bump Engine to v0.21.10 by @​matipan in dagger/dagger#14422

What to do next

• Join our Discord server
• Follow us on Twitter

... (truncated)

Changelog

Sourced from dagger-io's changelog.

v0.21.10 - 2026-09-30

Added

• Add opt-in engine CPU and memory telemetry from cgroup v2 by @​matipan in dagger/dagger#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 dagger/dagger#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

Commits

• 02b2558 chore: prep for v0.21.10 (#14422)
• e606f62 sdk/python: cap codegen's graphql-core below 3.3
• f264524 chore: post-release during v0.21.9 (#13980)
• See full diff in compare view

[dependabot]

Labels

The following labels could not be found: python. Please create it before Dependabot can add it to a pull request.

Please fix the above issues or remove invalid values from dependabot.yml.