Skip to content

chore(deps): update dependency dagger/dagger to v0.21.4#929

Merged
leonardoce merged 1 commit into
mainfrom
renovate/dagger-dagger-0.x
Jun 4, 2026
Merged

chore(deps): update dependency dagger/dagger to v0.21.4#929
leonardoce merged 1 commit into
mainfrom
renovate/dagger-dagger-0.x

Conversation

@renovate
Copy link
Copy Markdown
Contributor

@renovate renovate Bot commented May 29, 2026

This PR contains the following updates:

Package Update Change
dagger/dagger patch 0.21.00.21.4

Release Notes

dagger/dagger (dagger/dagger)

v0.21.4

Compare Source

Fixed
  • Fix a regression in the 1Password secret provider where secrets with spaces could not be resolved. #​13297
  • Container image tarball export can fail after cache pruning when the export needs layer content that is no longer retained by an owner lease. The observed failure was intermittent during engine builds, especially through Container.asTarball(forcedCompression: Zstd), with errors like a missing local content blob or a content digest not found while ensuring the requested compression type. #​13307
  • When WithFile/WithDirectory writes to a path that traverses a symlinked directory (e.g. ubuntu's /bin -> usr/bin), ensureDir resolved the symlink to the real view path but recursed on the parent of the original destPath instead of the parent of the resolved path. On a fresh overlay layer this skipped materializing intermediate dirs (e.g. usr) in the upperdir, so materializeExistingDir failed with 'mkdir .../usr/bin: no such file or directory'. #​13308
What to do next?

v0.21.3

Compare Source

Fixed
What to do next?

v0.21.2

Compare Source

Fixed
  • Fix dagger release publishing to bust cache of operations that involve external state by @​tiborvass + @​sipsma in #​13279
    The previous v0.21.1 release hit a long-standing bug in our version module tooling where certain operations did not bust cache based on changes in external state. We hit this for the first time because v0.21.0 and our infrastructure have had significant improvements in cache re-use.
What to do next?

v0.21.1

Compare Source

Added
  • Add native GraphQL interfaces and unified object IDs in DagQL by @​vito in #​12041
    Dagger now exposes objects through the standard Node interface and ID scalar, enabling APIs to accept generic Dagger objects while preserving SDK compatibility through legacy FooID and loadFooFromID views for older clients.
Fixed
  • Python SDK: fix unhandled module registration cases and bugs by removing the AST-based module analyzer and returning to runtime introspection by @​eunomie in #​13251
  • Fix Go module generation to avoid unnecessary dependency churn in generated go.mod and go.sum files by @​sipsma in #​13244
  • Fix registry authentication so withRegistryAuth credentials are not incorrectly skipped and authenticated publishes keep working after anonymous pulls to the same registry by @​marcosnils + @​sipsma in #​13255 #​13256
  • Fix published image layer structure so withDirectory and withFile operations preserve expected layer boundaries instead of being squashed into a few large layers by @​sipsma in #​13242
  • Fix Dockerfile RUN --mount=type=bind conversion when the bind source selector points to a regular file, improving compatibility with file and directory bind mounts by @​sipsma in #​13273
  • Fix module source cache dependency retention, including ephemeral missing shared result errors after cache persistence or engine restarts by @​sipsma in #​13243
  • Fix a bug where some cache entries did not have their size calculated during background and shutdown pruning by @​sipsma in #​13225
  • Fix repeated op:// 1Password secret reads by caching resolved 1Password secret values during a run, avoiding provider rate limits when the same secret is mounted or read multiple times by @​matipan in #​13249
  • Fix Windows Changeset exports so RemovePaths entries cannot remove files outside the selected export root through backslash or absolute-path interpretation by @​marcosnils in #​13222
  • Fix dagger --x-release for tagged releases so semver refs download release artifacts instead of looking in the main-build artifact namespace, and prevent local runner override environment from leaking into the re-executed CLI by @​grouville in #​13259
What to do next?

Configuration

📅 Schedule: (UTC)

  • Branch creation
    • At any time (no schedule defined)
  • Automerge
    • At any time (no schedule defined)

🚦 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.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate renovate Bot requested a review from a team as a code owner May 29, 2026 22:53
@dosubot dosubot Bot added the size:XS This PR changes 0-9 lines, ignoring generated files. label Jun 3, 2026
| datasource  | package       | from    | to      |
| ----------- | ------------- | ------- | ------- |
| github-tags | dagger/dagger | v0.21.0 | v0.21.4 |


Signed-off-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
@renovate renovate Bot force-pushed the renovate/dagger-dagger-0.x branch from 148a811 to 8d9dd98 Compare June 4, 2026 10:30
@renovate renovate Bot changed the title chore(deps): update dependency dagger/dagger to v0.21.1 chore(deps): update dependency dagger/dagger to v0.21.4 Jun 4, 2026
@dosubot dosubot Bot added the lgtm This PR has been approved by a maintainer label Jun 4, 2026
@leonardoce leonardoce merged commit c45472e into main Jun 4, 2026
8 checks passed
@leonardoce leonardoce deleted the renovate/dagger-dagger-0.x branch June 4, 2026 11:25
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

automated lgtm This PR has been approved by a maintainer no-issue size:XS This PR changes 0-9 lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant