Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

GitHub Actions: Transitioning from Node 16 to Node 20 #134

Closed
rlespinasse opened this issue Sep 23, 2023 · 3 comments · Fixed by #135
Closed

GitHub Actions: Transitioning from Node 16 to Node 20 #134

rlespinasse opened this issue Sep 23, 2023 · 3 comments · Fixed by #135
Labels

Comments

@rlespinasse
Copy link
Owner

https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/

@rlespinasse
Copy link
Owner Author

This only impact the v3, the v4 is not impacted since it's a composite action.

I consider this change as a breaking change and so since the v4 is already here. We could discontinue the v3.

This action support two versions for security fixes: The current one (v4) and the previous one (v3) without any ending date. We need to change this security support to only support the current one, and support the previous one for a period of type.

This enable us to have time for deprecating the v3 and time before starting the v5.

@rlespinasse
Copy link
Owner Author

rlespinasse commented Oct 20, 2023

To ease the migration of users from v3 to v4, the action will use node20 just before #136

@rlespinasse
Copy link
Owner Author

🎉 This issue has been resolved in version 4.5.0 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant