Skip to content
This repository was archived by the owner on Apr 26, 2024. It is now read-only.

GitHub Actions: All Actions will begin running on Node16 instead of Node12 #39

Closed
wants to merge 1 commit into from
Closed

GitHub Actions: All Actions will begin running on Node16 instead of Node12 #39

wants to merge 1 commit into from

Conversation

rossijonas
Copy link

Hi!

Please consider this update of node12 to node16 as suggested by GitHub.

GitHub Actions: All Actions will begin running on Node16 instead of Node12

September 22, 2022

Node 12 has been out of support since April 2022, as a result we have started the deprecation process of Node 12 for GitHub Actions. We plan to migrate all actions to run on Node16 by Summer 2023. We will monitor the progress of the migration and listen to the community for how things are going before we define a final date.
To raise awareness of the upcoming change, we are adding a warning into workflows which contain Actions running on Node 12. This will come into effect starting on September 27th.

When this action runs, it is displaying an alert about the deprecation of node12.

Node.js 12 actions are deprecated. For more information see: https://github.blog/changelog/2022-09-22-github-actions-all-actions-will-begin-running-on-node16-instead-of-node12/. Please update the following actions to use Node.js 16: khan/pull-request-comment-trigger@master

Thank you very much and have a great week 😀

@rossijonas rossijonas closed this Nov 16, 2022
@rossijonas rossijonas deleted the deprecate-node12 branch November 16, 2022 13:38
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant