Skip to content

fix: run bundled Docker actions on the Node 24 runtime (v1 maintenance) - #8

Merged
hisco merged 1 commit into
1.xfrom
1.x-node24
Jul 2, 2026
Merged

fix: run bundled Docker actions on the Node 24 runtime (v1 maintenance)#8
hisco merged 1 commit into
1.xfrom
1.x-node24

Conversation

@hisco

@hisco hisco commented Jul 2, 2026

Copy link
Copy Markdown
Contributor

Maintenance release for the v1 line. Ships the Node 24 runtime to everyone pinned to the floating @v1 tag without any interface change, so customer workflows stop emitting the deprecated-Node warning with zero action on their side.

What changed

  • Inner actions bumped to their Node 24 majors: build-push v6->v7, metadata v5->v6, setup-qemu v3->v4, setup-buildx v3->v4.
  • buildx_install input preserved. setup-buildx v4 removed its install input, so the composite reproduces that behavior with an explicit docker buildx install step gated on buildx_install. All inputs/outputs are otherwise identical to v1.5.2.
  • Release workflow: replaced the disabled codfish/semantic-release-action with SHA-pinned cycjimmy/semantic-release-action@v6.0.0, and enabled releases on the 1.x maintenance branch.

Result

Merging cuts a patch release on the v1 line (v1.5.3) and moves the floating v1 / v1.5 tags to this Node 24 build. Consumers on @v1 pick it up on their next run. The clean-interface line continues at v2.

https://claude.ai/code/session_011T9ASy4VmRoYrnuTsLd9oU


Note

Medium Risk
Touches the core Docker build path and release automation; behavior is intended to stay compatible but depends on upstream major action changes and the manual buildx install shim.

Overview
v1 maintenance so consumers on @v1 get Node 24–compatible bundled Docker actions without changing the public interface.

The composite action bumps inner steps to their Node 24 majors (setup-qemu v4, setup-buildx v4, metadata v6, build-push v7). Because setup-buildx v4 dropped the install input, the action adds a conditional docker buildx install step when buildx_install is true, preserving the previous alias behavior.

CI and release wiring now target 1.x alongside main: test/release workflows run on both branches, .releaserc.json includes 1.x, checkout uses v7, and release replaces codfish/semantic-release-action with SHA-pinned cycjimmy/semantic-release-action v6 and extra_plugins for semantic-release-github-actions-tags.

Reviewed by Cursor Bugbot for commit 856499b. Bugbot is set up for automated code reviews on this repo. Configure here.

Bump the inner actions to their Node 24 majors so consumers on the floating v1 tag stop hitting the deprecated-Node runtime warning: build-push v6->v7, metadata v5->v6, setup-qemu v3->v4, setup-buildx v3->v4.

The public buildx_install input is preserved. setup-buildx v4 removed its install input, so the composite now reproduces that behavior with an explicit 'docker buildx install' step gated on buildx_install. No interface change: all existing inputs and outputs are unchanged.

Release workflow: replace the disabled codfish/semantic-release-action with SHA-pinned cycjimmy/semantic-release-action@v6.0.0 and enable releases on the 1.x maintenance branch.

Claude-Session: https://claude.ai/code/session_011T9ASy4VmRoYrnuTsLd9oU
@hisco
hisco merged commit 526d49e into 1.x Jul 2, 2026
8 of 12 checks passed
@hisco
hisco deleted the 1.x-node24 branch July 2, 2026 08:32
@github-actions

github-actions Bot commented Jul 2, 2026

Copy link
Copy Markdown

🎉 This PR is included in version 1.5.3 🎉

The release is available on:

Your semantic-release bot 📦🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant