Update docker/build-push-action action to v6.10.0

[renovate-bot]

This PR contains the following updates:

Package	Type	Update	Change
docker/build-push-action	action	minor	v6.3.0 -> v6.10.0

---

Release Notes

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

v6.10.0

Compare Source

v6.9.0

Compare Source

• Bump @​docker/actions-toolkit from 0.38.0 to 0.39.0 in https://github.com/docker/build-push-action/pull/1234
• Bump path-to-regexp from 6.2.2 to 6.3.0 in https://github.com/docker/build-push-action/pull/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 https://github.com/docker/build-push-action/pull/1230

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

v6.7.0

Compare Source

v6.6.1

Compare Source

• Bump @​docker/actions-toolkit from 0.37.0 to 0.37.1 in https://github.com/docker/build-push-action/pull/1205

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

v6.6.0

Compare Source

v6.5.0

Compare Source

v6.4.1

Compare Source

v6.4.0

Compare Source

• Set repository and ghtoken attributes for GitHub Actions cache backend by @​crazy-max in https://github.com/docker/build-push-action/pull/1133
• Bump @​docker/actions-toolkit from 0.31.0 to 0.33.0 in https://github.com/docker/build-push-action/pull/1179

Full Changelog: docker/build-push-action@v6.3.0...v6.4.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 becomes conflicted, 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]

Walkthrough

The project has updated the docker/build-push-action version in the GitHub Actions workflow for Docker image publishing. The version has been upgraded from v6.3.0 to v6.10.0, reflecting a move to a newer release that may include improvements, bug fixes, or new features. The overall structure of the workflow remains unchanged.

Changes

File	Change Summary
.github/workflows/docker-publish.yml	Updated docker/build-push-action version from v6.3.0 to v6.10.0

Poem

In the garden of code where we play,
New versions hop in a joyful ballet.
With Docker builds that leap and bound,
Bugs and troubles are nowhere found.
Each update brings a springtime cheer,
Hopping forward, we have no fear!
🐇✨🚀

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Reviewing files that changed from the base of the PR and between 0ea97e3 and 2836c83.

📒 Files selected for processing (1)

• .github/workflows/docker-publish.yml (1 hunks)

🔇 Additional comments (1)

.github/workflows/docker-publish.yml (1)

76-76: LGTM! Version update looks safe.

The update from v6.3.0 to v6.10.0 is a minor version bump with dependency updates. The commit hash is correctly pinned for security.

Let's verify that the commit hash matches the tagged version:

✅ Verification successful

✅ Commit hash verification successful

The commit hash 48aba3b46d1b1fec4febb7c5d0c644b249a11355 in the workflow file exactly matches the official v6.10.0 tag of docker/build-push-action repository.

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Verify that the commit hash matches the v6.10.0 tag
# Expected: The commit hash should match the v6.10.0 tag

# Fetch the commit hash for v6.10.0 tag from the docker/build-push-action repository
gh api repos/docker/build-push-action/git/refs/tags/v6.10.0 | jq -r '.object.sha'

# Note: After merging, monitor the workflow runs to ensure the build process 
# continues to work as expected with the new version.

Length of output: 122

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 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.
  • Generate unit testing code for this file.
  • 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. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• 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 src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai 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

Documentation and Community

• 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.

[coderabbitai]

Actionable comments posted: 0

Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between 6bbe0ee and a6faa48.

Files selected for processing (1)

• .github/workflows/docker-publish.yml (1 hunks)

Files skipped from review due to trivial changes (1)

• .github/workflows/docker-publish.yml

[coderabbitai]

Actionable comments posted: 0

Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between a6faa48 and 6c00f49.

Files selected for processing (1)

• .github/workflows/docker-publish.yml (1 hunks)

Files skipped from review as they are similar to previous changes (1)

• .github/workflows/docker-publish.yml

[coderabbitai]

Actionable comments posted: 0

Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between 6c00f49 and f2a6d63.

Files selected for processing (1)

• .github/workflows/docker-publish.yml (1 hunks)

Files skipped from review as they are similar to previous changes (1)

• .github/workflows/docker-publish.yml