Skip to content

ci: move all actions to Node 24 runtimes - #7

Merged
DawnofGenX merged 1 commit into
mainfrom
ci/chase-action-versions
Oct 7, 2026
Merged

DawnofGenX merged 1 commit into
mainfrom
ci/chase-action-versions

Conversation

@DawnofGenX

Copy link
Copy Markdown
Owner

Silences the Node.js 20 is deprecated annotation on every run. Each action pinned to its latest Node 24 release; breaking-change notes reviewed (see commit message). The PR's own CI run is the verification — all five job shapes exercise these pinned versions.

The Actions runners are deprecating Node.js 20: every run of this
workflow annotates checkout@v4 and setup-python@v5 as forced onto
Node 24, and upload-artifact@v4 plus action-gh-release@v2 are next in
line. Rather than wait for the forced migration, pin each action to its
current latest Node 24 release:

- actions/checkout        v4    -> v7.0.1
- actions/setup-python    v5    -> v7.0.0
- actions/upload-artifact v4    -> v7.0.2
- softprops/action-gh-release v2 -> v3.0.3

Checked before bumping: upload-artifact v5-v7 are additive over v4
(opt-in direct upload, better 429 retries); our usage pins 'name' and
'path', both required-valid since v4. action-gh-release v3 moves only
the runtime to Node 24 - inputs unchanged. All jobs run on hosted
runners, so the 'self-hosted fleet needs runner >= 2.327.1' note does
not apply.

Separate from the Oct 19 ubuntu-latest migration: that label moves to
Ubuntu 26 runners. This repo pins nothing Ubuntu-specific, so that
migration is expected to be transparent; this commit only kills the
Node deprecation annotations.
@DawnofGenX
DawnofGenX merged commit a098486 into main Oct 7, 2026
5 checks passed
@DawnofGenX
DawnofGenX deleted the ci/chase-action-versions branch October 7, 2026 19:21
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant