search

ossf / scorecard

OpenSSF Scorecard - Security health metrics for Open Source
https://scorecard.dev
Apache License 2.0
4.63k stars 504 forks source link

:seedling: Bump github.com/docker/docker from 26.1.3+incompatible to 26.1.4+incompatible in /tools #4267

Closed dependabot[bot] closed 4 months ago

dependabot[bot] commented 4 months ago

Bumps github.com/docker/docker from 26.1.3+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:

Security

This release updates the Go runtime to 1.21.11 which contains security fixes for:

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

Commits
  • de5c9cf Merge pull request #47912 from thaJeztah/26.1_backport_vendor_containerd_1.7.18
  • c62dcf8 Merge pull request #47911 from thaJeztah/26.1_backport_bump_containerd_binary...
  • 17315a2 vendor: github.com/containerd/containerd v1.7.18
  • cbd9418 update containerd binary to v1.7.18
  • fb9f72a Merge pull request #47904 from thaJeztah/26.1_backport_bump_go1.21.11
  • 3115daa update to go1.21.11
  • 2861734 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_py
  • 3e09e19 Merge pull request #47894 from thaJeztah/26.1_backport_vendor_containerd_v1.7.17
  • 65b679a Merge pull request #47889 from thaJeztah/26.1_backport_platforms_err_handling
  • Additional commits viewable in compare view


Dependabot compatibility score

You can trigger a rebase of this PR by commenting @dependabot rebase.

Dependabot will merge this PR once CI passes on it, as requested by @spencerschrock.

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 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](https://github.com/ossf/scorecard/network/alerts).
dependabot[bot] commented 4 months ago

One of your CI runs failed on this pull request, so Dependabot won't merge it.

Dependabot will still automatically merge this pull request if you amend it and your tests pass.

spencerschrock commented 4 months ago

One of your CI runs failed on this pull request

Note: This e2e test is failing at HEAD right now anyway. I was curious if the commit we used for the e2e test was old enough that GitHub no longer saved the historical status info, but the data is empty even for the latest commit. I wonder if this is a GitHub outage (none were showing on https://githubstatus.com, though a possibly unrelated one is now?)

https://api.github.com/repos/ossf/scorecard/commits/2aa077c4fc2728eb9d70fa4c44ad55be99d73b16/statuses

spencerschrock commented 4 months ago

@dependabot squash and merge

spencerschrock commented 4 months ago

@dependabot rebase