cluster-api-provider-packet
cluster-api-provider-packet copied to clipboard
chore(deps): bump github.com/docker/docker from 25.0.5+incompatible to 26.1.4+incompatible in /test/e2e in the go_modules group across 1 directory
Bumps the go_modules group with 1 update in the /test/e2e directory: github.com/docker/docker.
Updates github.com/docker/docker from 25.0.5+incompatible to 26.1.4+incompatible
Release notes
Sourced from github.com/docker/docker's releases.
v26.1.4
26.1.4
For a full list of pull requests and changes in this release, refer to the relevant GitHub milestones:
- docker/cli, 26.1.4 milestone
- moby/moby, 26.1.4 milestone
- Deprecated and removed features, see Deprecated Features.
- Changes to the Engine API, see API version history.
Security
This release updates the Go runtime to 1.21.11 which contains security fixes for:
- CVE-2024-24789
- CVE-2024-24790
- A symlink time of check to time of use race condition during directory removal reported by Addison Crump (
@addisoncrump).Bug fixes and enhancements
- Fixed an issue where promoting a node immediately after another node was demoted could cause the promotion to fail. moby/moby#47870
- Prevent the daemon log from being spammed with
superfluous response.WriteHeader call ...messages.. moby/moby#47843- Don't show empty hints when plugins return an empty hook message. docker/cli#5083
- Added
ContextType: "moby"to the context list/inspect output to address a compatibility issue with Visual Studio Container Tools. docker/cli#5095- Fix a compatibility issue with Visual Studio Container Tools. docker/cli#5095
Packaging updates
- Update containerd (static binaries only) to v1.7.17. moby/moby#47841
- CVE-2024-24789, CVE-2024-24790: Update Go runtime to 1.21.11. moby/moby#47904
- Update Compose to v2.27.1. docker/docker-ce-packages#1022
- Update Buildx to v0.14.1. docker/docker-ce-packages#1021
v26.1.3
26.1.3
For a full list of pull requests and changes in this release, refer to the relevant GitHub milestones:
- docker/cli, 26.1.3 milestone
- moby/moby, 26.1.3 milestone
- Deprecated and removed features, see Deprecated Features.
- Changes to the Engine API, see API version history.
Bug fixes and enhancements
- Fix a regression that prevented the use of DNS servers within a
--internalnetwork. moby/moby#47832- When the internal DNS server's own address is supplied as an external server address, ignore it to avoid unproductive recursion. moby/moby#47833
Packaging updates
... (truncated)
Commits
de5c9cfMerge pull request #47912 from thaJeztah/26.1_backport_vendor_containerd_1.7.18c62dcf8Merge pull request #47911 from thaJeztah/26.1_backport_bump_containerd_binary...17315a2vendor: github.com/containerd/containerd v1.7.18cbd9418update containerd binary to v1.7.18fb9f72aMerge pull request #47904 from thaJeztah/26.1_backport_bump_go1.21.113115daaupdate to go1.21.112861734Merge pull request #47892 from thaJeztah/26.1_backport_api_docs_network_confi...9c95aeaMerge pull request #47893 from thaJeztah/26.1_backport_bump_docker_py3e09e19Merge pull request #47894 from thaJeztah/26.1_backport_vendor_containerd_v1.7.1765b679aMerge pull request #47889 from thaJeztah/26.1_backport_platforms_err_handling- Additional commits viewable in compare view
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 mergewill merge this PR after your CI passes on it@dependabot squash and mergewill squash and merge this PR after your CI passes on it@dependabot cancel mergewill cancel a previously requested merge and block automerging@dependabot reopenwill reopen this PR if it is closed@dependabot closewill close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@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 You can disable automated security fix PRs for this repo from the Security Alerts page.
[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by: dependabot[bot] Once this PR has been reviewed and has the lgtm label, please assign justinsb for approval. For more information see the Kubernetes Code Review Process.
The full list of commands accepted by this bot can be found here.
Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment
The Kubernetes project currently lacks enough contributors to adequately respond to all PRs.
This bot triages PRs according to the following rules:
- After 90d of inactivity,
lifecycle/staleis applied - After 30d of inactivity since
lifecycle/stalewas applied,lifecycle/rottenis applied - After 30d of inactivity since
lifecycle/rottenwas applied, the PR is closed
You can:
- Mark this PR as fresh with
/remove-lifecycle stale - Close this PR with
/close - Offer to help out with Issue Triage
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale
The Kubernetes project currently lacks enough active contributors to adequately respond to all PRs.
This bot triages PRs according to the following rules:
- After 90d of inactivity,
lifecycle/staleis applied - After 30d of inactivity since
lifecycle/stalewas applied,lifecycle/rottenis applied - After 30d of inactivity since
lifecycle/rottenwas applied, the PR is closed
You can:
- Mark this PR as fresh with
/remove-lifecycle rotten - Close this PR with
/close - Offer to help out with Issue Triage
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle rotten
The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.
This bot triages PRs according to the following rules:
- After 90d of inactivity,
lifecycle/staleis applied - After 30d of inactivity since
lifecycle/stalewas applied,lifecycle/rottenis applied - After 30d of inactivity since
lifecycle/rottenwas applied, the PR is closed
You can:
- Reopen this PR with
/reopen - Mark this PR as fresh with
/remove-lifecycle rotten - Offer to help out with Issue Triage
Please send feedback to sig-contributor-experience at kubernetes/community.
/close
@k8s-triage-robot: Closed this PR.
In response to this:
The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.
This bot triages PRs according to the following rules:
- After 90d of inactivity,
lifecycle/staleis applied- After 30d of inactivity since
lifecycle/stalewas applied,lifecycle/rottenis applied- After 30d of inactivity since
lifecycle/rottenwas applied, the PR is closedYou can:
- Reopen this PR with
/reopen- Mark this PR as fresh with
/remove-lifecycle rotten- Offer to help out with Issue Triage
Please send feedback to sig-contributor-experience at kubernetes/community.
/close
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.
This pull request was built based on a group rule. Closing it will not ignore any of these versions in future pull requests.
To ignore these dependencies, configure ignore rules in dependabot.yml