chore(deps): update docker/setup-buildx-action action to v4

[renovate-bot-cbcoutinho]

This PR contains the following updates:

Package	Type	Update	Change
docker/setup-buildx-action	action	major	v3.12.0 → v4.0.0

---

Release Notes

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

v4.0.0

Compare Source

• Node 24 as default runtime (requires Actions Runner v2.327.1 or later) by @​crazy-max in #​483
• Remove deprecated inputs/outputs by @​crazy-max in #​464
• Switch to ESM and update config/test wiring by @​crazy-max in #​481
• Bump @​actions/core from 1.11.1 to 3.0.0 in #​475
• Bump @​docker/actions-toolkit from 0.63.0 to 0.79.0 in #​482 #​485
• Bump js-yaml from 4.1.0 to 4.1.1 in #​452
• Bump lodash from 4.17.21 to 4.17.23 in #​472
• Bump minimatch from 3.1.2 to 3.1.5 in #​480

Full Changelog: docker/setup-buildx-action@v3.12.0...v4.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 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 has been generated by Renovate Bot.

[claude]

PR Review: Update docker/setup-buildx-action to v4

This is a straightforward Renovate-generated dependency update. Here's my assessment:

Changes

• Bumps docker/setup-buildx-action from v3.12.0 to v4.0.0
• SHA pin is correctly updated (8d2750c... → 4d04d5d...), maintaining the pinned-SHA security practice used throughout this workflow

Key v4.0.0 changes to be aware of

• Node 24 runtime: Requires Actions Runner v2.327.1+. The workflow uses ubuntu-latest, which GitHub updates regularly and already meets this requirement.
• Removed deprecated inputs/outputs: This is the only breaking change risk. However, the setup-buildx-action step in this workflow uses no inputs (default configuration only), so there is no impact.

No issues found

• No deprecated inputs/outputs are being used
• SHA pinning is preserved
• ubuntu-latest runner is compatible with Node 24
• All other steps in the workflow are unaffected

Verdict: Safe to merge. ✓