CI: Node 20 actions deprecated

[ptheywood]

CLAAssistant
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: FLAMEGPU/contributor-assistant-github-action@ca4a40a. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

The same applies to other workflows, but the CLA bot will need the most effort on our part as it seems upstream has become unmaintained in March...

[ptheywood]

This is about to become an issue, so we may need to adddress this sooner rather than later, although the change of default is now 2026-06-16 so we have a few more weeks.

Editor’s note (May 19, 2026): Updated the migration date to June 16th, 2026.

Most of the changes are simple version bumps, but the CLA bot will be more of an issue with the upstream repository being archived on 2026-03-26, so we'll need to make changes to our fork:

https://github.com/FLAMEGPU/contributor-assistant-github-action/

• Enable CI, removing workflows/steps that depend on 3rd party tools to minimise burden
• Add node 24 to the nodejs.yml matrix, removing 18 and 20.
• update node20 in actionl.yml
• See what gets upset and fix it, probably bumping some dependency versions?

For now, the quickest fix is probably to just version bump other actions (done in a branch off amdgpu somewhere iirc) and then just enable the mitigation for the CLA assistant which will buy us several more months for the more-involved changes described above.