Skip to content

Bump docker/build-push-action from 6 to 7#226

Open
dependabot[bot] wants to merge 1 commit intodevelopfrom
dependabot/github_actions/develop/docker/build-push-action-7
Open

Bump docker/build-push-action from 6 to 7#226
dependabot[bot] wants to merge 1 commit intodevelopfrom
dependabot/github_actions/develop/docker/build-push-action-7

Conversation

@dependabot
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Mar 8, 2026

Bumps docker/build-push-action from 6 to 7.

Release notes

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

v7.0.0

Full Changelog: docker/build-push-action@v6.19.2...v7.0.0

v6.19.2

Full Changelog: docker/build-push-action@v6.19.1...v6.19.2

v6.19.1

Full Changelog: docker/build-push-action@v6.19.0...v6.19.1

v6.19.0

Full Changelog: docker/build-push-action@v6.18.0...v6.19.0

v6.18.0

[!NOTE] Build summary is now supported with Docker Build Cloud.

Full Changelog: docker/build-push-action@v6.17.0...v6.18.0

v6.17.0

[!NOTE] Build record is now exported using the buildx history export command instead of the legacy export-build tool.

Full Changelog: docker/build-push-action@v6.16.0...v6.17.0

v6.16.0

... (truncated)

Commits
  • d08e5c3 Merge pull request #1479 from docker/dependabot/npm_and_yarn/docker/actions-t...
  • cbd2dff chore: update generated content
  • f76f51f chore(deps): Bump @​docker/actions-toolkit from 0.78.0 to 0.79.0
  • 7d03e66 Merge pull request #1473 from crazy-max/rm-deprecated-envs
  • 98f853d chore: update generated content
  • cadccf6 remove deprecated envs
  • 03fe877 Merge pull request #1478 from docker/dependabot/github_actions/docker/setup-b...
  • 827e366 chore(deps): Bump docker/setup-buildx-action from 3 to 4
  • e25db87 Merge pull request #1474 from crazy-max/rm-export-build-tool
  • 1ac2573 Merge pull request #1470 from crazy-max/node24
  • Additional commits viewable in compare view

Dependabot compatibility score

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 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)

Bumps [docker/build-push-action](https://github.com/docker/build-push-action) from 6 to 7.
- [Release notes](https://github.com/docker/build-push-action/releases)
- [Commits](docker/build-push-action@v6...v7)

---
updated-dependencies:
- dependency-name: docker/build-push-action
  dependency-version: '7'
  dependency-type: direct:production
  update-type: version-update:semver-major
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot bot added dependencies Pull requests that update a dependency file maintenance Any maintenance task on the project labels Mar 8, 2026
@dependabot dependabot bot requested a review from a team as a code owner March 8, 2026 19:32
@dependabot dependabot bot added maintenance Any maintenance task on the project dependencies Pull requests that update a dependency file labels Mar 8, 2026
@github-actions
Copy link
Contributor

github-actions bot commented Mar 8, 2026

The primary change in this commit is updating the Docker action version within the GitHub workflow from version 6 to version 7. This version change affects the automation process of building and pushing Docker images for both the backend and frontend components.

Walkthrough

  • Chore: Updated the docker/build-push-action from version 6 to version 7. This ensures the workflow uses the latest features and improvements of the Docker build and push action, potentially increasing efficiency or compatibility, although there are no direct user-visible changes due to this adjustment.

Model: gpt-4o-2024-08-06 | Prompt Tokens: 354 | Completion Tokens: 112

Copy link
Contributor

@github-actions github-actions bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Here's a supportive code review enhanced by AI assistance. Please note that some observations are suggestions based on patterns rather than definitive requirements, so trust your judgment on what fits your project best. You remain in full control of all decisions—AI simply offers additional perspective to help inform your choices.


Always critique what AI says. Do not let AI replace YOUR I.
Model: claude-sonnet-4-20250514 | Prompt Tokens: 949 | Completion Tokens: 378


- name: 🐳 Build and push Backend Docker image
uses: docker/build-push-action@v6
uses: docker/build-push-action@v7
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good update to use the latest version of the docker/build-push-action. However, consider pinning to a specific commit SHA for better security and reproducibility:

uses: docker/build-push-action@4f58ea79222b3b9dc2c8bbdd6debcef730109a75 # v7.6.0

This prevents potential supply chain attacks and ensures the workflow behaves consistently across different runs. You can find the commit SHA for v7 releases on the GitHub repository.


- name: 🐳 Build and push Frontend Docker image
uses: docker/build-push-action@v6
uses: docker/build-push-action@v7
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Same recommendation as above - consider pinning to a specific commit SHA for enhanced security:

uses: docker/build-push-action@4f58ea79222b3b9dc2c8bbdd6debcef730109a75 # v7.6.0

This ensures both Docker build steps use the same secure, pinned version of the action.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Pull requests that update a dependency file maintenance Any maintenance task on the project

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants