Skip to content

Conversation

@tnir
Copy link
Contributor

@tnir tnir commented Aug 13, 2025

Why

With v3, we have the following deprecation notices:

The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/

from https://github.com/collectiveidea/awesome_nested_set/actions/runs/11509088498.

See https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/

Node16 has been out of support since September 2023. As a result we have started the deprecation process of Node16 for GitHub Actions. We plan to migrate all actions to run on Node20 by Spring 2024.
Following on from our warning in workflows using Node16 we will start enforcing the use of Node20 rather than Node16 on the 3rd of June.

What

Bump actions/checkout from v3 (and v4) to v5.

@tnir tnir force-pushed the tn-use-actions-checkout-v4 branch from 45df06b to c6a1503 Compare August 13, 2025 23:10
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant