search

Slicer / slicer-check-commit-message-action

GitHub composite action to verify that commit messages conform to the Slicer commit style guidelines.
MIT License
0 stars 0 forks source link

Potentially consider new base action using node 20 #3

Open jamesobutler opened 2 months ago

jamesobutler commented 2 months ago

As seen at https://github.com/Slicer/Slicer/actions/runs/10777311645

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

Based on https://github.com/GsActions/commit-message-checker/issues/100#issuecomment-2071114500, the author of the action is no longer responsive to keeping it updated so a fork or other solution should be considered.

jcfr commented 2 months ago

Ditto. I was initially considering to leverage one of the feature associated with new ruleset capabilities, but it is only available within GitHub enterprise.

so a fork or other solution should be considered

That would indeed be a sensible path forward :rocket:

image image
jamesobutler commented 1 month ago

Important new blog post regarding this situation. https://github.blog/changelog/2024-09-25-end-of-life-for-actions-node16/

Following our change to default customers to use Node20, Node16 will reach end of life in the Actions runner on the 15th of October 2024.

From the 15th of October, we will no longer include Node16 in the Actions runner and customers will no longer be able to use Node16 Actions or operating systems that do not support Node20.

To prevent disruption to your Actions workflows, if you’re an Actions maintainer, update your actions to run on Node20 instead of Node16. If you’re an Actions user, update your workflows with latest versions of the actions, which run on Node20.