Skip to content

CI: check out and cache with Node 24 actions - #408

Merged
davidchisnall merged 2 commits into
gnustep:masterfrom
DTW-Thalion:ci/actions-node24
Aug 10, 2026
Merged

CI: check out and cache with Node 24 actions#408
davidchisnall merged 2 commits into
gnustep:masterfrom
DTW-Thalion:ci/actions-node24

Conversation

@DTW-Thalion

Copy link
Copy Markdown
Contributor

Every job logs "Node.js 20 is deprecated" and then runs actions/checkout@v3 on
Node 24 anyway, because the runners no longer carry Node 20.

The releases whose action.yml declares node24 are checkout v5, upload-artifact
v6 and cache v5, so those are the versions used here. msys2/setup-msys2@v2 and
reactivecircus/android-emulator-runner@v2 already declare node24 and are
unchanged. checkout v5 wants a runner of 2.327.1 or later and the hosted
runners are on 2.336.0. v6 moves credentials to a separate file and v7 refuses
a fork checkout for pull_request_target and workflow_run, and neither event is
used by these workflows.

Verified on a run of this branch: no job logs the deprecation, and the logs
carry checkout v5, upload-artifact v6 and cache v5. The windows jobs still fail
on this branch for the reason PR 407 fixes; on a branch carrying both changes
they pass.

Every job logs "Node.js 20 is deprecated" and runs actions/checkout@v3 on
Node 24 anyway, because the runners no longer have Node 20.

The releases that declare node24 in their action.yml are checkout v5,
upload-artifact v6 and cache v5. msys2/setup-msys2@v2 and
reactivecircus/android-emulator-runner@v2 already declare node24.

checkout v5 needs a runner of 2.327.1 or later; the hosted runners are on
2.336.0. v6 moves credentials to a separate file and v7 refuses a fork
checkout for pull_request_target and workflow_run, neither of which these
workflows use.
@DTW-Thalion

Copy link
Copy Markdown
Contributor Author

Needs #407 merged first.

@davidchisnall davidchisnall left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good, but conflicts with the change in the other fix.

@DTW-Thalion

Copy link
Copy Markdown
Contributor Author

rebased on #407 and conflicts resolved - ready to merge.

@davidchisnall

Copy link
Copy Markdown
Member

GitHub disagrees: This branch cannot be rebased due to conflicts.

@DTW-Thalion

Copy link
Copy Markdown
Contributor Author

GitHub is being difficult then... this is what I see:
Screenshot_20260810_074137_Chrome

@davidchisnall

Copy link
Copy Markdown
Member

Oh, it looks like you did a merge not a rebase, rebase-and-merge doesn't like it because it breaks linear history.

@davidchisnall
davidchisnall merged commit 403df0d into gnustep:master Aug 10, 2026
91 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

2 participants