-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
🐛 [bug]: using v1 gives node16 deprecation warnings #21
Comments
It should have been fixed with this #20 |
Will review, bump deps, test and release new one around end of 1st week of March. |
any way I can help to get this released? |
any update on the release @DariuszPorowski ? |
@mvanduijker @pakosak currently this PR is a blocker: #22 |
So, that's a won't fix for this simple uses: raven-actions/actionlint@ea4eb57846a36a6faefbdc2d9ac873da9057c1bb Looking forward, thanks for your work. 👍 |
🐛 What happened?
We start seeing deprecation warnings aboud node16 when using raven-actions/actionlint@v1:
🔬 How to reproduce?
Call actionlint action
🏗️ Code Sample / Log
🌌 Environment (actionlint action)
1.0.3
🌌 Environment (actionlint)
1.6.26-Linux-X64
🌌 Environment (GitHub Runner OS)
Linux
📷 Screenshots
No response
📈 Expected behavior
actions/cache is upgraded to v4 to remove the warning
📎 Additional context
No response
📜 Code of Conduct
The text was updated successfully, but these errors were encountered: