You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It should be fairly easy to change this by replacing using: node12 with using: node16 - I wouldn't expect anything in this Action's source code to break as a result of that.
One thing to note, by and large I've seen other Actions use a major version bump when releasing this change. The motivation being that older GitHub Actions runners may not support node16. See for example the "What's new" section of actions/checkout.
I noticed #151 includes this change. However, it's scope is quite broad which might be holding it back. Hence, I created this ticket to bring extra attention to this particular aspect of that PR.
The text was updated successfully, but these errors were encountered:
I am getting an error that Node 12 deprecated while deploying through Azure github actions.
I searched on internet and found out to update to Node 16
can anybody help me out.
Following the recent blog post "GitHub Actions: All Actions will begin running on Node16 instead of Node12" by GitHub, I noticed this action is still running on
node12
:paths-filter/action.yml
Lines 50 to 52 in 8c7f485
It should be fairly easy to change this by replacing
using: node12
withusing: node16
- I wouldn't expect anything in this Action's source code to break as a result of that.One thing to note, by and large I've seen other Actions use a major version bump when releasing this change. The motivation being that older GitHub Actions runners may not support
node16
. See for example the "What's new" section ofactions/checkout
.I noticed #151 includes this change. However, it's scope is quite broad which might be holding it back. Hence, I created this ticket to bring extra attention to this particular aspect of that PR.
The text was updated successfully, but these errors were encountered: