Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Warning: Please update the following actions to use Node.js 16
See original GitHub issueThis is the warning I see every time I my workflow:
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: getsentry/paths-filter@v2
Issue Analytics
- State:
- Created 10 months ago
- Comments:6 (5 by maintainers)
Top Results From Across the Web
Node.js 12 actions deprecation warning on github
In several CI runs, I see a warning like Node.js 12 actions are deprecated. ... Please update the following actions to use Node.js...
Read more >Warning in workflow about nodejs version · Issue #114 - GitHub
Warning in workflow about nodejs version #114 ... Please update the following actions to use Node.js 16: azure/arm-deploy, azure/functions- ...
Read more >Github actions for Rust shows Node.js warning (12 - 16)
Support for Node.js 12 will not be dropped out of a sudden. However, maintainers should act to update their actions and users should...
Read more >All Actions will begin running on Node16 instead of Node12
Node 12 has been out of support since April 2022, as a result we have started the deprecation process of Node 12 for...
Read more >Deprecated APIs | Node.js v19.3.0 Documentation
Deprecated APIs#. Node.js APIs might be deprecated for any of the following reasons: Use of the API is unsafe. An improved alternative API...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
@iamtodor you are not using action from this repo. You are using a fork which lacks the latest changes fixing the issue. So instead of this:
Use this:
Scratch all that. Confirmed this is not an issue with your action. Mine was a checkout action and I lacked an attention to detail. Looking closer at @iamtodor’s deprecation notice it looks like they’re using a custom variant of
paths-filterthat’s the culprit. This issue can likely be closed.