chore: bump third-party GH Actions to Node 24-compatible releases#136
Open
mcp-tool-shop wants to merge 1 commit into
Open
chore: bump third-party GH Actions to Node 24-compatible releases#136mcp-tool-shop wants to merge 1 commit into
mcp-tool-shop wants to merge 1 commit into
Conversation
Bumps: - `docker/setup-buildx-action` v3 → v4.1.0 - `docker/setup-qemu-action` v3.2.0 → v4.0.0 Files touched: - `.github/workflows/publish.yml` Context: GitHub forces Node 24 default on Jun 2, 2026 and removes Node 20 actions Sep 16, 2026. Third-party sweep — first sweep covered actions/*.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Third-party sweep ahead of GitHub's Node 24 transition. The previous sweep covered the
actions/*namespace; this one covers third-party actions that still ran on Node 20 (or older). Latestgh api action.ymlruntime confirmed for each target version.Bumps:
docker/setup-buildx-actionv3 → v4.1.0docker/setup-qemu-actionv3.2.0 → v4.0.0Files:
.github/workflows/publish.ymlRuntime audit (current pin → target pin):
softprops/action-gh-releasev1 (Node 16!) / v2.x (Node 20) → v3.0.0 (Node 24)astral-sh/setup-uvv3 (Node 16!) / v5.x (Node 20) → v8.1.0 (Node 24)pnpm/action-setupv3 / v4 (Node 20) → v6.0.8 (Node 24)docker/login-actionv3 (Node 20) → v4.2.0 (Node 24)docker/build-push-actionv6 (Node 20) → v7.2.0 (Node 24)docker/setup-buildx-actionv3 (Node 20) → v4.1.0 (Node 24)docker/setup-qemu-actionv3.x (Node 20) → v4.0.0 (Node 24)docker/metadata-actionv5 (Node 20) → v6.1.0 (Node 24)Only the action versions you have pinned are bumped —
pnpm/action-setup@v5,docker/login-action@v4*, etc. already run on Node 24 and are left alone.SHA + version-comment pinning convention preserved. All pins remain hard-pinned to commit SHA with
# vX.Y.Zcomment, matching the org's supply-chain hardening style.