build: update all github actions away from deprecated node.js 20

[nbogie]

To ensure the continued smooth running of the site's CI systems, all used github actions that currently run on node 20 should be updated to versions which run on node 24.

Why?

As per this notice from github blog,
"Node20 will reach end-of-life (EOL) in April of 2026. As a result we have started the deprecation process of Node20 for GitHub Actions."

More info:

When website build-deploy job runs (for example) the following warning is issued:

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-node@v4, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24.

Testing

Properly resolving this issue will be 2% code change and 98% doing thorough testing of the affected CI flows.

See also

#1233

See also

There is a similar task to update the CI actions for the p5.js repo:
processing/p5.js#8674

[nbogie]

I'd like to work on this.

Update:
Moving setup_node and checkout actions to version 5 tests out fine. However, beta_deploy gets a warning for cloudflare/wrangler-action@v3 running on node 20, and that action doesn't have a more up-to-date version.

Wrangler issue here has some movement.

The warning also gives updated timelines:

Warning: Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: cloudflare/wrangler-action@v3. 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.

[ulgens]

@nbogie I checked #1282 but it looks like an automation solution is not a part of the PR (yet). If that sounds useful, I can help to add a Renovate (or dependabot) config with it, so manual work needed for similar updates can be minimized.

[nbogie]

Hi, @ulgens! That's something I'll leave the maintainers to comment on. Perhaps @limzykenneth

[limzykenneth]

If dependabot can do it that would be great as it already raises NPM dependency PRs for us.

[ulgens]

@limzykenneth I couldn't find the dependabot config in the repo and commented on #823

[limzykenneth]

@ulgens Dependabot don't need a config for security updates so we don't have a config file yet. You can create one for the version update and we'll toggle it on once it is merged.

[ulgens]

@limzykenneth I see. In that case, how do you feel about renovatebot? Dependabot development has been staggering for years and I don't trust it with any of the projects I contribute to. I was thinking of expanding dependabot config so a smaller diff will handle it but if there is no config for any of the tools yet, I think renovate is a feasible option.

[limzykenneth]

We'll need to review it in this case and will get back to you on whether we'll continue to dependabot or renovatebot.