deps: bump docker/setup-buildx-action from 4.2.0 to 4.3.0

[dependabot]

Bumps docker/setup-buildx-action from 4.2.0 to 4.3.0.

Release notes

Sourced from docker/setup-buildx-action's releases.

v4.3.0

• Bump @​docker/actions-toolkit from 0.92.0 to 0.95.0 in docker/setup-buildx-action#595
• Bump brace-expansion from 1.1.13 to 1.1.18 in docker/setup-buildx-action#600
• Bump js-yaml from 5.2.0 to 5.3.0 in docker/setup-buildx-action#585
• Bump postcss from 8.5.10 to 8.5.25 in docker/setup-buildx-action#598
• Bump undici from 6.27.0 to 6.28.0 in docker/setup-buildx-action#601

Full Changelog: docker/setup-buildx-action@v4.2.0...v4.3.0

Commits

• 37fe631 Merge pull request #595 from docker/dependabot/npm_and_yarn/docker/actions-to...
• b5c4f91 [dependabot skip] chore: update generated content
• 3e93b63 build(deps): bump @​docker/actions-toolkit from 0.92.0 to 0.95.0
• e527031 Merge pull request #600 from docker/dependabot/npm_and_yarn/brace-expansion-1...
• c68814b [dependabot skip] chore: update generated content
• 3f891b0 build(deps): bump brace-expansion from 1.1.13 to 1.1.18
• 787db26 Merge pull request #585 from docker/dependabot/npm_and_yarn/js-yaml-5.2.1
• f779368 [dependabot skip] chore: update generated content
• 7d5e604 build(deps): bump js-yaml from 5.2.0 to 5.3.0
• 292c2fb Merge pull request #590 from docker/dependabot/github_actions/actions/setup-n...
• Additional commits viewable 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 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)

[codacy-production]

Up to standards ✅

🟢 Issues 0 issues

Results:
0 new issues

View in Codacy

_{NEW Get contextual insights on your PRs based on Codacy's metrics, along with PR and Jira context, without leaving GitHub. Enable AI reviewer
TIP This summary will be updated as you push new changes.}

[vyruss]

@coderabbitai assess risk and feasibility

[coderabbitai]

🧩 Analysis chain

🏁 Script executed:

#!/bin/bash
set -euo pipefail

repo="docker/setup-buildx-action"

printf '%s\n' '== tags =='
gh api "repos/$repo/git/ref/tags/v4.2.0" --jq '.object | {type, sha}'
gh api "repos/$repo/git/ref/tags/v4.3.0" --jq '.object | {type, sha}'

printf '%s\n' '== release v4.3.0 =='
gh api "repos/$repo/releases/tags/v4.3.0" \
  --jq '{name, published_at, target_commitish, body}'

printf '%s\n' '== compare v4.2.0...v4.3.0 =='
gh api "repos/$repo/compare/v4.2.0...v4.3.0" \
  --jq '{status, ahead_by, total_commits, files: [.files[] | {filename, status, additions, deletions}]}'

Length of output: 2700

---

@vyruss, this update is feasible and has low risk.

• Both pinned SHAs match the upstream tags:
  • bb05f3f...edd6d2c is v4.2.0.
  • 37fe631...f7f0e is v4.3.0.
• The v4.3.0 release contains dependency updates only. It does not declare action input, output, or workflow behavior changes.
• The workflow configuration remains valid. Both jobs use docker/setup-buildx-action without action-specific inputs.
• The SHA pinning remains intact. This preserves the supply-chain control used by the workflow.

Residual risk is limited to the regenerated action bundle, dist/index.cjs, which incorporates the updated dependencies. The upgrade affects both the build and manifest jobs in the same way.

No workflow changes or extra validation are required. A manual smoke run with push=false can provide additional runtime confirmation before a publishing run.

_{You are interacting with an AI system.}