Bump docker/setup-qemu-action from 3 to 4#336
Conversation
🤖 Cursor Dependency AnalysisThe action is used in exactly one place in this repo. Let me verify the upstream action's interface hasn't changed in a breaking way.Here is my review: 1. Usage sites The dependency is used in exactly one place: uses: docker/setup-qemu-action@v4
with:
platforms: riscv64The PR has already updated the tag from 2. API compatibility The The major version bump is driven by:
None of these affect the action's public interface or behavior. 3. Risks / unknowns
4. Recommendation: merge This is a safe, straightforward major bump driven entirely by Node runtime and internal tooling upgrades. The action's public API is identical, the single usage site is simple, and GitHub-hosted runners already support Node 24. No caveats needed. |
|
@dependabot sign your commits |
|
@dependabot recreate |
Bumps [docker/setup-qemu-action](https://github.com/docker/setup-qemu-action) from 3 to 4. - [Release notes](https://github.com/docker/setup-qemu-action/releases) - [Commits](docker/setup-qemu-action@v3...v4) --- updated-dependencies: - dependency-name: docker/setup-qemu-action dependency-version: '4' dependency-type: direct:production update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com>
3086fee to
f7c9719
Compare
🤖 Cursor Dependency AnalysisSupply-Chain Malware ReviewVerifying how the action is referenced in the repository to ground the review. Verdict: benign Why
Actionable note: If a job ever failed only on very old self-hosted runners below v2.327.1, upgrading the runner would be required — that’s an environment requirement from upstream, not malware. Scanner vs interpretation: The heuristics flag benign noise in minified deps and lockfile strings; they do not contradict a benign conclusion. Compatibility AnalysisSearching the repo for 1) Where it’s usedSingle real usage: Other hits are only under 2) Overlap with v4 changesFrom release notes and This workflow only sets Conclusion: Your usage does not depend on APIs that were called out as changed in a breaking way for consumers; it’s a minimal, stable pattern. 3) Risks / unknowns
4) RecommendationMerge — appropriate for this repo as configured: one workflow, hosted runners, standard If you introduce self-hosted runners for this job without upgrading them, revisit runner version first; otherwise no need to hold the PR. Malware Scan Summary
Top findings
|
Bumps docker/setup-qemu-action from 3 to 4.
Release notes
Sourced from docker/setup-qemu-action's releases.
... (truncated)
Commits
ce36039Merge pull request #245 from crazy-max/node246386344node 24 as default runtime1ea3db7Merge pull request #243 from docker/dependabot/npm_and_yarn/docker/actions-to...b56a002chore: update generated contentc43f02dbuild(deps): bump@docker/actions-toolkitfrom 0.67.0 to 0.77.0ce10c58Merge pull request #244 from docker/dependabot/npm_and_yarn/actions/core-3.0.0429fc9dchore: update generated content060e5f8build(deps): bump@actions/corefrom 1.11.1 to 3.0.044be13eMerge pull request #231 from docker/dependabot/npm_and_yarn/js-yaml-3.14.21897438chore: update generated contentDependabot 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 rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill 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 versionwill 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 dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)Note
Low Risk
Low risk CI-only change that updates the QEMU setup GitHub Action; potential impact is limited to the riscv64 build workflow if the new major version behaves differently.
Overview
Updates the riscv64 GitHub Actions workflow to use
docker/setup-qemu-action@v4instead of@v3for QEMU setup, keeping the rest of the build/test steps unchanged.Written by Cursor Bugbot for commit f7c9719. This will update automatically on new commits. Configure here.