Move the workflow actions onto their Node 24 majors - #27
Merged
Merged
Conversation
Five actions released a major at once, and all five majors are the same change: the action's own runtime moves from Node 20 to Node 24. GitHub is deprecating Node 20 on its runners, so this is the direction the pins have to go anyway, and `ubuntu-latest` already runs a runner new enough for it. What the release notes call breaking, checked against what these workflows actually pass: - `setup-buildx-action` v4 drops its deprecated inputs. Both call sites use the action bare, with no `with:` block at all. - `metadata-action` v6 changes how `#` is read inside a list input: it now survives in a value and only starts a comment on its own line. Neither the `tags:` nor the `labels:` list here contains one. - `login-action` v4 and `action-gh-release` v3 are the runtime bump alone; the inputs used here -- registry, username, password, and draft, prerelease, files, body -- are untouched. - `setup-uv` v7 additionally stops overwriting `UV_CACHE_DIR` when the workflow already set it, which `ci.yml` does, and warns instead. That is the behaviour the workflow wanted in the first place. Only the `setup-uv` pin sits in `ci.yml`, so it is the only one a pull request proves. The other four live in `edge.yml` and `release.yml`, which run on a push to main and on a `v*` tag and never on a pull request -- a green check on this change says nothing about them, and the first real evidence is the next edge build.
basecubedev
force-pushed
the
deps/workflow-action-majors
branch
from
September 20, 2026 14:09
6515425 to
51f36db
Compare
basecubedev
added a commit
that referenced
this pull request
Sep 20, 2026
Move the workflow actions onto their Node 24 majors
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.
Five actions released a major at once, and all five majors are the same change: the action's own runtime moves from Node 20 to Node 24. GitHub is deprecating Node 20 on its runners, so this is the direction the pins have to go anyway, and
ubuntu-latestalready runs a runner new enough for it.What the release notes call breaking, checked against what these workflows actually pass:
setup-buildx-actionv4 drops its deprecated inputs. Both call sites use the action bare, with nowith:block at all.metadata-actionv6 changes how#is read inside a list input: it now survives in a value and only starts a comment on its own line. Neither thetags:nor thelabels:list here contains one.login-actionv4 andaction-gh-releasev3 are the runtime bump alone; the inputs used here -- registry, username, password, and draft, prerelease, files, body -- are untouched.setup-uvv7 additionally stops overwritingUV_CACHE_DIRwhen the workflow already set it, whichci.ymldoes, and warns instead. That is the behaviour the workflow wanted in the first place.Only the
setup-uvpin sits inci.yml, so it is the only one a pull request proves. The other four live inedge.ymlandrelease.yml, which run on a push to main and on av*tag and never on a pull request -- a green check on this change says nothing about them, and the first real evidence is the next edge build.