Update docker/build-push-action action to v6

[renovate]

This PR contains the following updates:

Package	Type	Update	Change
docker/build-push-action	action	major	v5.4.0 -> v6.18.0

---

Release Notes

docker/build-push-action (docker/build-push-action)

v6.18.0

Compare Source

• Bump @​docker/actions-toolkit from 0.61.0 to 0.62.1 in #​1381

[!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

Compare Source

• Bump @​docker/actions-toolkit from 0.59.0 to 0.61.0 by @​crazy-max in #​1364

[!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

Compare Source

• Handle no default attestations env var by @​crazy-max in #​1343
• Only print secret keys in build summary output by @​crazy-max in #​1353
• Bump @​docker/actions-toolkit from 0.56.0 to 0.59.0 in #​1352

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

v6.15.0

Compare Source

• Bump @​docker/actions-toolkit from 0.55.0 to 0.56.0 in #​1330

Full Changelog: docker/build-push-action@v6.14.0...v6.15.0

v6.14.0

Compare Source

• Bump @​docker/actions-toolkit from 0.53.0 to 0.55.0 in #​1324

Full Changelog: docker/build-push-action@v6.13.0...v6.14.0

v6.13.0

Compare Source

• Bump @​docker/actions-toolkit from 0.51.0 to 0.53.0 in #​1308

Full Changelog: docker/build-push-action@v6.12.0...v6.13.0

v6.12.0

Compare Source

• Bump @​docker/actions-toolkit from 0.49.0 to 0.51.0 in #​1300

Full Changelog: docker/build-push-action@v6.11.0...v6.12.0

v6.11.0

Compare Source

• Handlebar defaultContext support for build-contexts input by @​crazy-max in #​1283
• Bump @​docker/actions-toolkit from 0.46.0 to 0.49.0 in #​1281

Full Changelog: docker/build-push-action@v6.10.0...v6.11.0

v6.10.0

Compare Source

• Add call input to set method for evaluating build by @​crazy-max in #​1265
• Bump @​actions/core from 1.10.1 to 1.11.1 in #​1238
• Bump @​docker/actions-toolkit from 0.39.0 to 0.46.0 in #​1268
• Bump cross-spawn from 7.0.3 to 7.0.6 in #​1261

Full Changelog: docker/build-push-action@v6.9.0...v6.10.0

v6.9.0

Compare Source

• Bump @​docker/actions-toolkit from 0.38.0 to 0.39.0 in #​1234
• Bump path-to-regexp from 6.2.2 to 6.3.0 in #​1232

Full Changelog: docker/build-push-action@v6.8.0...v6.9.0

v6.8.0

Compare Source

• Bump @​docker/actions-toolkit from 0.37.1 to 0.38.0 in #​1230

Full Changelog: docker/build-push-action@v6.7.0...v6.8.0

v6.7.0

Compare Source

• Print info message for build summary support checks by @​crazy-max in #​1211

Full Changelog: docker/build-push-action@v6.6.1...v6.7.0

v6.6.1

Compare Source

• Bump @​docker/actions-toolkit from 0.37.0 to 0.37.1 in #​1205

Full Changelog: docker/build-push-action@v6.6.0...v6.6.1

v6.6.0

Compare Source

• Generate GitHub annotations for build checks by @​crazy-max in #​1197
• Bump @​docker/actions-toolkit from 0.35.0 to 0.37.0 in #​1196 #​1198

Full Changelog: docker/build-push-action@v6.5.0...v6.6.0

v6.5.0

Compare Source

• Bump @​docker/actions-toolkit from 0.33.0 to 0.35.0 in #​1186 #​1191

Full Changelog: docker/build-push-action@v6.4.1...v6.5.0

v6.4.1

Compare Source

• revert "Set repository and ghtoken attributes for GitHub Actions cache backend" by @​crazy-max in #​1183

Full Changelog: docker/build-push-action@v6.4.0...v6.4.1

v6.4.0

Compare Source

• Set repository and ghtoken attributes for GitHub Actions cache backend by @​crazy-max in #​1133
• Bump @​docker/actions-toolkit from 0.31.0 to 0.33.0 in #​1179

Full Changelog: docker/build-push-action@v6.3.0...v6.4.0

v6.3.0

Compare Source

• DOCKER_BUILD_RECORD_UPLOAD environment variable to enable/disable build record upload by @​crazy-max in #​1172
• DOCKER_BUILD_NO_SUMMARY has been deprecated. Set DOCKER_BUILD_SUMMARY to false instead by @​crazy-max in #​1170 #​1173
• Bump @​docker/actions-toolkit from 0.28.0 to 0.31.0 in #​1171 #​1159 #​1169

Full Changelog: docker/build-push-action@v6.2.0...v6.3.0

v6.2.0

Compare Source

• Use default retention days for build export artifact by @​crazy-max in #​1153
• Bump @​docker/actions-toolkit from 0.27.0 to 0.28.0 in #​1158

Full Changelog: docker/build-push-action@v6.1.0...v6.2.0

v6.1.0

Compare Source

• Bump @​docker/actions-toolkit from 0.26.2 to 0.27.0 in #​1149

Full Changelog: docker/build-push-action@v6.0.2...v6.1.0

v6.0.2

Compare Source

• Bump @​docker/actions-toolkit from 0.26.1 to 0.26.2 in #​1147

Full Changelog: docker/build-push-action@v6.0.1...v6.0.2

v6.0.1

Compare Source

• Bump @​docker/actions-toolkit from 0.26.0 to 0.26.1 in #​1142

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

v6.0.0

Compare Source

• Export build record and generate build summary by @​crazy-max in #​1120
• Bump @​docker/actions-toolkit from 0.24.0 to 0.26.0 in #​1132 #​1136 #​1138
• Bump braces from 3.0.2 to 3.0.3 in #​1137

[!NOTE]
This major release adds support for generating Build summary and exporting build record for your build. You can disable this feature by setting DOCKER_BUILD_SUMMARY: false environment variable in your workflow.

Full Changelog: docker/build-push-action@v5.4.0...v6.0.0

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[coderabbitai]

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

---

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

Support

Need help? Join our Discord community for assistance with any issues or questions.

CodeRabbit Commands (Invoked using PR/Issue comments)

Type @coderabbitai help to get the list of available commands.

Other keywords and placeholders

• Add @coderabbitai ignore or @coderabbit ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Status, Documentation and Community

• Visit our Status Page to check the current availability of CodeRabbit.
• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.