Update docker/setup-buildx-action action to v3.9.0

[renovate-bot]

This PR contains the following updates:

Package	Type	Update	Change
docker/setup-buildx-action	action	minor	v3.0.0 -> v3.9.0

---

Release Notes

docker/setup-buildx-action (docker/setup-buildx-action)

v3.9.0

Compare Source

v3.8.0

Compare Source

v3.7.1

Compare Source

• Switch back to uuid package by @​crazy-max in https://github.com/docker/setup-buildx-action/pull/369

Full Changelog: docker/setup-buildx-action@v3.7.0...v3.7.1

v3.7.0

Compare Source

• Always set buildkitd-flags if opt-in by @​crazy-max in https://github.com/docker/setup-buildx-action/pull/363
• Remove uuid package and switch to crypto by @​crazy-max in https://github.com/docker/setup-buildx-action/pull/366
• Bump @​docker/actions-toolkit from 0.35.0 to 0.39.0 in https://github.com/docker/setup-buildx-action/pull/362
• Bump path-to-regexp from 6.2.2 to 6.3.0 in https://github.com/docker/setup-buildx-action/pull/354

Full Changelog: docker/setup-buildx-action@v3.6.1...v3.7.0

v3.6.1

Compare Source

• Check for malformed docker context by @​crazy-max in https://github.com/docker/setup-buildx-action/pull/347

Full Changelog: docker/setup-buildx-action@v3.6.0...v3.6.1

v3.6.0

Compare Source

• Create temp docker context if default one has TLS data loaded before creating a container builder by @​crazy-max in https://github.com/docker/setup-buildx-action/pull/341

Full Changelog: docker/setup-buildx-action@v3.5.0...v3.6.0

v3.5.0

Compare Source

v3.4.0

Compare Source

• Throw error message instead of exit code by @​crazy-max in https://github.com/docker/setup-buildx-action/pull/315
• Bump @​docker/actions-toolkit from 0.20.0 to 0.31.0 in https://github.com/docker/setup-buildx-action/pull/321 https://github.com/docker/setup-buildx-action/pull/338
• Bump braces from 3.0.2 to 3.0.3 in https://github.com/docker/setup-buildx-action/pull/329
• Bump undici from 5.28.3 to 5.28.4 in https://github.com/docker/setup-buildx-action/pull/312
• Bump uuid from 9.0.1 to 10.0.0 in https://github.com/docker/setup-buildx-action/pull/326

Full Changelog: docker/setup-buildx-action@v3.3.0...v3.4.0

v3.3.0

Compare Source

v3.2.0

Compare Source

• Rename and align config inputs by @​crazy-max in https://github.com/docker/setup-buildx-action/pull/303
  • config to buildkitd-config
  • config-inline to buildkitd-config-inline
• Bump @​docker/actions-toolkit from 0.17.0 to 0.19.0 in https://github.com/docker/setup-buildx-action/pull/302 https://github.com/docker/setup-buildx-action/pull/306

[!NOTE]
config and config-inline input names are deprecated and will be removed in next major release.

Full Changelog: docker/setup-buildx-action@v3.1.0...v3.2.0

v3.1.0

Compare Source

---

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 primary change involves updating the version of several GitHub Actions in the .github/workflows/docker-publish.yml file. The docker/setup-buildx-action has been upgraded from v3.0.0 to v3.9.0, while the docker/build-push-action has been updated to v6.3.0. The docker/login-action and docker/metadata-action versions remain unchanged. The overall structure of the workflow remains intact, maintaining the same jobs and steps for building and pushing Docker images.

Changes

Files	Change Summary
.github/workflows/docker-publish.yml	Updated docker/setup-buildx-action from v3.0.0 to v3.9.0 and docker/build-push-action to v6.3.0. docker/login-action and docker/metadata-action remain unchanged.

Poem

In the garden of code, we hop with glee,
From v3.0.0 to 3.9.0, oh what a spree!
Docker builds dance, all shiny and new,
With each little fix, our dreams come true.
So let’s celebrate, in our burrow so snug,
For progress is sweet, and we give it a hug! 🐇✨

Tip

🌐 Web search-backed reviews and chat

• We have enabled web search-based reviews and chat for all users. This feature allows CodeRabbit to access the latest documentation and information on the web.
• You can disable this feature by setting web_search: false in the knowledge_base settings.
• Please share any feedback in the Discord discussion.

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 2263d0f and c21ab95.

📒 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

⏰ Context from checks skipped due to timeout of 90000ms (1)

• GitHub Check: gitStream.cm

---

🪧 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 generate docstrings to generate docstrings for this PR. (Beta)
• @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 1fc704f.

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 1fc704f and cbdf181.

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 cbdf181 and 10b3dd5.

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

🧹 Nitpick comments (1)

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

Line range hint 1-99: Workflow maintains stability with proper action versioning

The update to docker/setup-buildx-action maintains compatibility with other Docker actions in the workflow. All actions are correctly pinned to specific SHA commits, and the workflow's security measures (conditional execution, secure credential handling, OIDC token usage) remain intact.

Consider adding a comment in the workflow file documenting the minimum required Docker version for Buildx features, helping future maintainers understand compatibility requirements.

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between c1f2f2b and 2263d0f.

📒 Files selected for processing (1)

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

🔇 Additional comments (1)

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

52-52: LGTM! SHA verification passed for docker/setup-buildx-action@v3.8.0

The update from v3.0.0 to v3.8.0 is properly pinned to the correct SHA commit, following security best practices.

✅ Verification successful

SHA verification successful for docker/setup-buildx-action@v3.8.0

The SHA commit 6524bf65af31da8d45b59e8c27de4bd072b392f5 correctly corresponds to the v3.8.0 tag in the official docker/setup-buildx-action repository, confirming the secure pinning of the action version.

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Verify the SHA corresponds to the v3.8.0 tag
gh api repos/docker/setup-buildx-action/git/refs/tags/v3.8.0 | jq -r '.object.sha' | grep '6524bf65af31da8d45b59e8c27de4bd072b392f5'

Length of output: 171