chore(deps): update dependency dagger/dagger to v0.21.3#154
Open
renovate[bot] wants to merge 1 commit into
Open
chore(deps): update dependency dagger/dagger to v0.21.3#154renovate[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.0 | v0.21.3 | Signed-off-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
cc3a1ff to
16035f1
Compare
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.0→v0.21.3Release Notes
dagger/dagger (dagger/dagger)
v0.21.3Compare Source
Fixed
What to do next?
v0.21.2Compare Source
Fixed
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.1Compare Source
Added
Dagger now exposes objects through the standard
Nodeinterface andIDscalar, enabling APIs to accept generic Dagger objects while preserving SDK compatibility through legacyFooIDandloadFooFromIDviews for older clients.Fixed
go.modandgo.sumfiles by @sipsma in #13244withRegistryAuthcredentials are not incorrectly skipped and authenticated publishes keep working after anonymous pulls to the same registry by @marcosnils + @sipsma in #13255 #13256withDirectoryandwithFileoperations preserve expected layer boundaries instead of being squashed into a few large layers by @sipsma in #13242RUN --mount=type=bindconversion when the bind source selector points to a regular file, improving compatibility with file and directory bind mounts by @sipsma in #13273missing shared resulterrors after cache persistence or engine restarts by @sipsma in #13243op://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 #13249RemovePathsentries cannot remove files outside the selected export root through backslash or absolute-path interpretation by @marcosnils in #13222dagger --x-releasefor 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 #13259What 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 was generated by Mend Renovate. View the repository job log.