-
Notifications
You must be signed in to change notification settings - Fork 21
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
build(deps): bump github.com/docker/docker from 26.0.0+incompatible to 26.1.4+incompatible #222
Conversation
Bumps [github.com/docker/docker](https://github.com/docker/docker) from 26.0.0+incompatible to 26.1.4+incompatible. - [Release notes](https://github.com/docker/docker/releases) - [Commits](moby/moby@v26.0.0...v26.1.4) --- updated-dependencies: - dependency-name: github.com/docker/docker dependency-type: indirect ... Signed-off-by: dependabot[bot] <[email protected]>
DryRun Security SummaryThe provided GitHub pull request contains a series of changes, including README updates, license file changes, dependency version updates, and configuration file modifications, which do not appear to introduce any significant security concerns, except for the update to the ORAS Go library from version 1 to version 2, which includes the introduction of an experimental Expand for full summarySummary: The provided GitHub pull request contains a series of changes to various files, including README updates, license file changes, dependency version updates, and configuration file modifications. From an application security engineer's perspective, the majority of these changes do not introduce any significant security concerns. The updates to the README, license, and configuration files are primarily non-code changes that do not directly impact the application's security. The dependency version updates, such as the changes to the The most notable change is the update to the ORAS Go library from version 1 to version 2, which includes several architectural and interface changes. While these changes generally seem to improve the library's security and maintainability, the introduction of the experimental Files Changed:
Overall, the changes in this GitHub pull request do not appear to introduce any significant security concerns. However, it's always important to thoroughly review any dependency updates and new features, especially those that may have security implications, to ensure the ongoing security and integrity of the application. Code AnalysisWe ran
Riskiness🟢 Risk threshold not exceeded. |
DryRun Security SummaryWe are currently analyzing this pull request to produce a meaningful summary. Code AnalysisWe ran
Riskiness🟢 Risk threshold not exceeded. |
Vulnerable Libraries (1)
More info on how to fix Vulnerable Libraries in Go. 👉 Go to the dashboard for detailed results. 📥 Happy? Share your feedback with us. |
Superseded by #223. |
Bumps github.com/docker/docker from 26.0.0+incompatible to 26.1.4+incompatible.
Release notes
Sourced from github.com/docker/docker's releases.
... (truncated)
Commits
de5c9cf
Merge pull request #47912 from thaJeztah/26.1_backport_vendor_containerd_1.7.18c62dcf8
Merge pull request #47911 from thaJeztah/26.1_backport_bump_containerd_binary...17315a2
vendor: github.com/containerd/containerd v1.7.18cbd9418
update containerd binary to v1.7.18fb9f72a
Merge pull request #47904 from thaJeztah/26.1_backport_bump_go1.21.113115daa
update to go1.21.112861734
Merge pull request #47892 from thaJeztah/26.1_backport_api_docs_network_confi...9c95aea
Merge pull request #47893 from thaJeztah/26.1_backport_bump_docker_py3e09e19
Merge pull request #47894 from thaJeztah/26.1_backport_vendor_containerd_v1.7.1765b679a
Merge pull request #47889 from thaJeztah/26.1_backport_platforms_err_handlingDependabot 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 rebase
will rebase this PR@dependabot recreate
will recreate this PR, overwriting any edits that have been made to it@dependabot merge
will merge this PR after your CI passes on it@dependabot squash and merge
will squash and merge this PR after your CI passes on it@dependabot cancel merge
will cancel a previously requested merge and block automerging@dependabot reopen
will reopen this PR if it is closed@dependabot close
will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot show <dependency name> ignore conditions
will show all of the ignore conditions of the specified dependency@dependabot ignore this major version
will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor version
will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependency
will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)You can disable automated security fix PRs for this repo from the Security Alerts page.