Bump the all-updates group across 1 directory with 2 updates - #1066
Bump the all-updates group across 1 directory with 2 updates#1066dependabot[bot] wants to merge 1 commit into
Conversation
Bumps the all-updates group with 2 updates in the / directory: [github.com/docker/cli](https://github.com/docker/cli) and [github.com/moby/buildkit](https://github.com/moby/buildkit). Updates `github.com/docker/cli` from 29.5.2+incompatible to 29.5.3+incompatible - [Commits](docker/cli@v29.5.2...v29.5.3) Updates `github.com/moby/buildkit` from 0.28.1 to 0.30.0 - [Release notes](https://github.com/moby/buildkit/releases) - [Commits](moby/buildkit@v0.28.1...v0.30.0) --- updated-dependencies: - dependency-name: github.com/docker/cli dependency-version: 29.5.3+incompatible dependency-type: direct:production update-type: version-update:semver-patch dependency-group: all-updates - dependency-name: github.com/moby/buildkit dependency-version: 0.30.0 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: all-updates ... Signed-off-by: dependabot[bot] <support@github.com>
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 8eef3a807c
ℹ️ About Codex in GitHub
Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".
| github.com/lestrrat-go/structinfo v0.0.0-20210312050401-7f8bd69d6acb // indirect | ||
| github.com/mitchellh/go-ps v1.0.0 | ||
| github.com/moby/buildkit v0.28.1 | ||
| github.com/moby/buildkit v0.30.0 |
There was a problem hiding this comment.
Adapt Dockerfile2LLB call for BuildKit 0.30
Bumping BuildKit to v0.30.0 changes dockerfile2llb.Dockerfile2LLB to return only (*Result, error) (with the LLB state at Result.State), but pkg/parser/dockerfile/dockerfile.go:30 still assigns five return values from that call. Any build or test that compiles the Dockerfile parser will now fail with an assignment mismatch, so this dependency update needs the call site updated or the bump held back.
Useful? React with 👍 / 👎.
|
Looks like these dependencies are updatable in another way, so this is no longer needed. |
Bumps the all-updates group with 2 updates in the / directory: github.com/docker/cli and github.com/moby/buildkit.
Updates
github.com/docker/clifrom 29.5.2+incompatible to 29.5.3+incompatibleCommits
d1c06efMerge pull request #7022 from mickael-docker/docs-request-field7dd053bMerge pull request #7003 from thaJeztah/logs_links37c3d31Merge pull request #7024 from thaJeztah/add_zizmor45f10f2Merge pull request #7025 from vvoland/update-gob458dc9update to go1.26.41953194gha: apply zizmor fixesac0419egha: add zizmor workflow1aa0416docs: recommend default deny and clarify requesturi field3a85952Merge pull request #7020 from thaJeztah/full_semver8d3fbdfMerge pull request #7019 from thaJeztah/dependabot_labelsUpdates
github.com/moby/buildkitfrom 0.28.1 to 0.30.0Release notes
Sourced from github.com/moby/buildkit's releases.
... (truncated)
Commits
dd2170eMerge pull request #6770 from crazy-max/v0.30-picks-0.30.0e4b9769test: gate merge diff tests through worker capabilitiesd5956a1skip pin race test on workers without merge diff support505ab37solver: fix race in walkProvenancef2e48d2Merge pull request #6762 from jsternberg/add-error-detailsf7a40a0Merge pull request #6758 from tonistiigi/fix-provenance-data-race80e934dremotecache: propagate details field from registry when includeda7c8749Merge pull request #6761 from moby/dependabot/github_actions/github/codeql-ac...df37b67build(deps): bump github/codeql-action from 4.35.3 to 4.35.4c7ba941Merge pull request #6759 from moby/dependabot/github_actions/docker/github-bu...Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore <dependency name> major versionwill close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)@dependabot ignore <dependency name> minor versionwill close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)@dependabot ignore <dependency name>will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)@dependabot unignore <dependency name>will remove all of the ignore conditions of the specified dependency@dependabot unignore <dependency name> <ignore condition>will remove the ignore condition of the specified dependency and ignore conditions