[PR #1657] [CLOSED] Bump docker/build-push-action from 6.1.0 to 6.2.0 #1699

New issue

Closed

opened 2026-03-03 12:35:48 +03:00 by kerem · 0 comments

kerem commented

2026-03-03 12:35:48 +03:00

Owner

📋 Pull Request Information

Original PR: https://github.com/fsouza/fake-gcs-server/pull/1657
Author: @dependabot[bot]
Created: 6/26/2024
Status: ❌ Closed

Base: main ← Head: dependabot/github_actions/docker/build-push-action-6.2.0

📝 Commits (1)

9aea86c Bump docker/build-push-action from 6.1.0 to 6.2.0

📊 Changes

2 files changed (+2 additions, -2 deletions)

View changed files

📝 .github/workflows/docker-push.yml (+1 -1)
📝 .github/workflows/docker-tests.yml (+1 -1)

📄 Description

Bumps docker/build-push-action from 6.1.0 to 6.2.0.

Release notes

Sourced from docker/build-push-action's releases.

v6.2.0

Use default retention days for build export artifact by @crazy-max in docker/build-push-action#1153

Bump @docker/actions-toolkit from 0.27.0 to 0.28.0 in docker/build-push-action#1158

Full Changelog: https://github.com/docker/build-push-action/compare/v6.1.0...v6.2.0

Commits

1556069 Merge pull request #1158 from docker/dependabot/npm_and_yarn/docker/actions-t...
57e1d34 chore: update generated content
309982e chore(deps): Bump @docker/actions-toolkit from 0.27.0 to 0.28.0
9476c25 Merge pull request #1153 from crazy-max/export-retention
97be5a4 chore: update generated content
9cac6c8 use default retention days for build export artifact
See full diff 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 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)

_{🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.}

## 📋 Pull Request Information **Original PR:** https://github.com/fsouza/fake-gcs-server/pull/1657 **Author:** [@dependabot[bot]](https://github.com/apps/dependabot) **Created:** 6/26/2024 **Status:** ❌ Closed **Base:** `main` ← **Head:** `dependabot/github_actions/docker/build-push-action-6.2.0` --- ### 📝 Commits (1) - [`9aea86c`](https://github.com/fsouza/fake-gcs-server/commit/9aea86cb04487f78512571e743598d4ec5c1158a) Bump docker/build-push-action from 6.1.0 to 6.2.0 ### 📊 Changes **2 files changed** (+2 additions, -2 deletions) <details> <summary>View changed files</summary> 📝 `.github/workflows/docker-push.yml` (+1 -1) 📝 `.github/workflows/docker-tests.yml` (+1 -1) </details> ### 📄 Description Bumps [docker/build-push-action](https://github.com/docker/build-push-action) from 6.1.0 to 6.2.0. <details> <summary>Release notes</summary> Sourced from <a href="https://github.com/docker/build-push-action/releases">docker/build-push-action's releases</a>. <blockquote> <h2>v6.2.0</h2> <ul> <li>Use default retention days for build export artifact by <a href="https://github.com/crazy-max"><code>@crazy-max</code></a> in <a href="https://redirect.github.com/docker/build-push-action/pull/1153">docker/build-push-action#1153</a></li> <li>Bump <code>@docker/actions-toolkit</code> from 0.27.0 to 0.28.0 in <a href="https://redirect.github.com/docker/build-push-action/pull/1158">docker/build-push-action#1158</a></li> </ul> Full Changelog: <a href="https://github.com/docker/build-push-action/compare/v6.1.0...v6.2.0">https://github.com/docker/build-push-action/compare/v6.1.0...v6.2.0</a> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/docker/build-push-action/commit/15560696de535e4014efeff63c48f16952e52dd1"><code>1556069</code></a> Merge pull request <a href="https://redirect.github.com/docker/build-push-action/issues/1158">#1158</a> from docker/dependabot/npm_and_yarn/docker/actions-t...</li> <li><a href="https://github.com/docker/build-push-action/commit/57e1d34ac3097d9f17c4d3cdbcb8609bf1838864"><code>57e1d34</code></a> chore: update generated content</li> <li><a href="https://github.com/docker/build-push-action/commit/309982ebc95a96ea0ab37ce98b3b2a9e1a2497b4"><code>309982e</code></a> chore(deps): Bump <code>@docker/actions-toolkit</code> from 0.27.0 to 0.28.0</li> <li><a href="https://github.com/docker/build-push-action/commit/9476c25b2a7a4ab5171cd8f4658468d19b69d7ae"><code>9476c25</code></a> Merge pull request <a href="https://redirect.github.com/docker/build-push-action/issues/1153">#1153</a> from crazy-max/export-retention</li> <li><a href="https://github.com/docker/build-push-action/commit/97be5a4928e7b54d4f6440c616a9180d0193e9c4"><code>97be5a4</code></a> chore: update generated content</li> <li><a href="https://github.com/docker/build-push-action/commit/9cac6c8ea04b693525a33651136a4114582823b6"><code>9cac6c8</code></a> use default retention days for build export artifact</li> <li>See full diff in <a href="https://github.com/docker/build-push-action/compare/v6.1.0...v6.2.0">compare view</a></li> </ul> </details> [![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=docker/build-push-action&package-manager=github_actions&previous-version=6.1.0&new-version=6.2.0)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) 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-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> 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) </details> --- 🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.