chore(deps): update dependency dagger/dagger to v0.21.10 - #1138
Open
renovate[bot] wants to merge 1 commit into
Open
renovate[bot] wants to merge 1 commit into
renovate[bot] wants to merge 1 commit into
Conversation
| datasource | package | from | to | | ----------- | ------------- | ------- | -------- | | github-tags | dagger/dagger | v0.21.9 | v0.21.10 | Signed-off-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
This branch has not been deployed
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
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.9→0.21.10Release Notes
dagger/dagger (dagger/dagger)
v0.21.10Compare Source
v0.21.10 - 2026-09-30
Added
Enable
telemetry.resourceMetricsin/etc/dagger/engine.jsonand setOTEL_EXPORTER_OTLP_METRICS_ENDPOINTin the engine environment. The newresource metrics use a separate OTLP export path. Client telemetry is
unchanged, and engine resource telemetry is disabled by default.
Fixed
Container.withServiceBindingnow works for a service whose custom hostname by @Zaba505 in #13751was scoped to another module's DNS domain. A service created with
withHostnameis namespaced into the domain of whichever module first startsit, so a module that started its own service before handing it to a caller
left that caller's
withExecfailing at hosts-file setup withlookup <hostname> ... no such host. Binding the service explicitly nowresolves 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()anddag.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!
What 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.