Looks like the CI job also fails with v4 😢

Tried adding the following to the build_bundle_linux job:

  env:
    ACTIONS_RUNNER_FORCED_INTERNAL_NODE_VERSION: node16
    ACTIONS_RUNNER_FORCE_ACTIONS_NODE_VERSION: node16

But it didn't work. Not sure how to export these variables before starting the runners in our case.

Replacing the action used in the build_bundle_linux job with taiki-e/checkout-action@v1 (a 3rd party action that doesn't use node) avoids the error until the actions/upload-artifact action is called because it uses the same dependencies (see this run for example).

I've also tried to set ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION: true at the workflow level (as suggested by this comment) but it didn't work (see run here).

Maybe worth adding a link to https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/ to the PR description (and, thus, the git commit message).

I've also tried to set ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION: true at the workflow level (as suggested by actions/checkout#1809 (comment)) but it didn't work (see run here).

Note: @tautschnig told us this didn't work because v4 will always try to use node20. The flag works if we don't upgrade the action's version.

Maybe worth adding a link to https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/ to the PR description (and, thus, the git commit message).

Yes, added the link. Thanks!