CI : Continue using Node16 for actions #1424
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
GitHub actions are now run on Node20 by default, but this requires glibc >=2.28 so actions no longer run in our CentOS 7 build container.
Setting
ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true
allows us to continue using Node16 for the near future, but support for this may be removed in October...https://github.blog/changelog/2024-05-17-updated-dates-for-actions-runner-using-node20-instead-of-node16-by-default/
This also updates the existing Node12 actions to the Node16 native versions used on Gaffer CI to silence a few additional warnings reported during the CI run.