Repository navigation
chore(deps): update dependency dagger to v0.21.11 - #358
Open
botty-mcbottington[bot] wants to merge 1 commit into
Open
botty-mcbottington[bot] wants to merge 1 commit into
botty-mcbottington[bot] wants to merge 1 commit into
Conversation
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #358 +/- ##
=======================================
Coverage 45.16% 45.16%
=======================================
Files 53 53
Lines 4886 4886
=======================================
Hits 2207 2207
Misses 2523 2523
Partials 156 156 ☔ View full report in Codecov by Harness. |
botty-mcbottington
Bot
force-pushed
the
renovate/dagger-0.x
branch
from
October 1, 2026 01:03
160034f to
474b4f1
Compare
botty-mcbottington
Bot
changed the title
botty-mcbottington
Bot
force-pushed
the
renovate/dagger-0.x
branch
from
October 22, 2026 00:46
474b4f1 to
e3b8fea
Compare
botty-mcbottington
Bot
changed the title
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:
v0.21.4→0.21.11Release Notes
dagger/dagger (dagger)
v0.21.11Compare Source
v0.21.11 - 2026-10-21
Fixed
import cycle not allowedin OpenTelemetry packages by @sipsma in #14646Generated modules now pin
github.com/dagger/otel-goandgo.opentelemetry.io/otel/sdkinstead of resolving them to their latest versions, which pulled
go.opentelemetry.io/otelv1.47.0 into a cycle with the pinnedotel/logv0.16.0.Cached results, types, module resolvers and module dependency schemas no longer keep
session schema servers alive, so long-running engines stop accumulating heap until OOM-killed.
What to do next?
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?
v0.21.9Compare Source
v0.21.9 - 2026-08-25
Added
Fixed
Container.withDirectoryandDirectory.withDirectoryno longer restore by @sipsma in #13848deleted nested files after execs remove and recreate an ancestor
directory.
initialization or teardown, preventing Cloud keeper heartbeats from stalling
and live engines from being suspended.
preventing shutdown responses from timing out while the engine releases
session-owned cache results.
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.
when image pulls or publishes succeed, while genuine registry failures remain
visible.
Container.fromby @sipsma in #13901What to do next?
v0.21.8Compare Source
v0.21.8 - 2026-07-29
Changed
#13615
Fixed
COPY-ed directories now get a content-based cache identity, re-keying downstream steps only when copied contentactually changes. by @marcosnils in #13765
--x-releaseCLI re-exec so_EXPERIMENTAL_DAGGER_RUNNER_HOSTis 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
DAGGER_SILENTis now honored as the equivalent of--silent. by @sipsma in#13762
What to do next?
v0.21.7Compare Source
Changed
JSONnamespace (with a deprecated top-leveltoJSON) and picking up constructor scope and nullable input fixes. by @vito in #13482Fixed
.envfile handling so non-matching variables are kept as hidden expansion context instead of being dropped, allowing later variables to expand against them. by @marcosnils in #13490foo/ignored with!foo/bar.txt) no longer fails withno such file or directory; ignored parent dirs are now created on demand for visible descendants. by @grouville in #13439concurrent map iteration and map writecrashes. by @sipsma in #13474containerdriver to honor the privileged option by granting all capabilities (--cap-add ALL), so the engine can bind-mount/etc/resolv.confon startup withcontainer1.0.0's reduced default capability set. by @eunomie in #13460@cache(and other directive) arguments resolve against the declaring type's file scope, fixingFunctionCachePolicy not found in enverrors in multi-file modules. by @vito in #13455What to do next?
v0.21.6Compare Source
Added
registryServiceoptions toContainer.fromandContainer.publish, allowing containers to pull from and publish to a registry provided by a DaggerService. This supports local ephemeral registries without starting unrelated services attached to the container. by @grouville in #13305Fixed
add explicit dependency: dep result <id> missing from cacheafter implementation-scoped module results were reused across sessions. by @sipsma in #13412Mapfields so map values are restored correctly between calls instead of failing withexpected module type, got dang.MapType. by @vito in #13421.envuser defaults for module constructors so passing one constructor argument explicitly no longer drops defaults for the other arguments. by @marcosnils in #13424invalid immutable referrors. by @sipsma in #13429What to do next?
v0.21.5Compare Source
Added
Changed
Fixed
What to do next?
Configuration
📅 Schedule: (UTC)
🚦 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.
This PR has been generated by Mend Renovate CLI.