Fix warning about Node version in triage workflow #628
Conversation
|
@danielhjacobs, can you share more about what warning you observed and how this change addresses it? Is there a known issue in github/issue-labeler that might have more info? |
|
Also see https://github.com/github/issue-labeler/releases/tag/v2.6, which includes github/issue-labeler#57 which updated Node 12 to Node 16, plus see the links from the action, https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/ and https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/ |
|
Do you want any more info on this? In my opinion it's generally not a good idea to rely on the auto-upgrade behavior of the Node versions for GitHub actions when newer versions of the actions exist. |
|
The new timeline for Node16 to reach end of life in actions is June 30, 2024, according to https://github.blog/changelog/2024-05-17-updated-dates-for-actions-runner-using-node20-instead-of-node16-by-default/ |
No description provided.