fix: run bundled Docker actions on the Node 24 runtime (v1 maintenance) - #8
Merged
Conversation
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
|
🎉 This PR is included in version 1.5.3 🎉 The release is available on:
Your semantic-release bot 📦🚀 |
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.
Maintenance release for the v1 line. Ships the Node 24 runtime to everyone pinned to the floating
@v1tag without any interface change, so customer workflows stop emitting the deprecated-Node warning with zero action on their side.What changed
build-pushv6->v7,metadatav5->v6,setup-qemuv3->v4,setup-buildxv3->v4.buildx_installinput preserved.setup-buildxv4 removed itsinstallinput, so the composite reproduces that behavior with an explicitdocker buildx installstep gated onbuildx_install. All inputs/outputs are otherwise identical to v1.5.2.codfish/semantic-release-actionwith SHA-pinnedcycjimmy/semantic-release-action@v6.0.0, and enabled releases on the1.xmaintenance branch.Result
Merging cuts a patch release on the v1 line (
v1.5.3) and moves the floatingv1/v1.5tags to this Node 24 build. Consumers on@v1pick it up on their next run. The clean-interface line continues atv2.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 installshim.Overview
v1 maintenance so consumers on
@v1get Node 24–compatible bundled Docker actions without changing the public interface.The composite action bumps inner steps to their Node 24 majors (
setup-qemuv4,setup-buildxv4,metadatav6,build-pushv7). Becausesetup-buildxv4 dropped theinstallinput, the action adds a conditionaldocker buildx installstep whenbuildx_installistrue, preserving the previous alias behavior.CI and release wiring now target
1.xalongsidemain: test/release workflows run on both branches,.releaserc.jsonincludes1.x, checkout uses v7, and release replacescodfish/semantic-release-actionwith SHA-pinnedcycjimmy/semantic-release-actionv6 andextra_pluginsforsemantic-release-github-actions-tags.Reviewed by Cursor Bugbot for commit 856499b. Bugbot is set up for automated code reviews on this repo. Configure here.