-
Notifications
You must be signed in to change notification settings - Fork 31
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
Node.js 16 actions are deprecated.
#97
Comments
Node.js 16 actions are deprecated.
Is |
@afifurrohman-id for
You must have a step in your workflow which uses this action v1 and you can then replace it with azure/login@v2 If not, check in the Set up job in your workflow if you can find something like : which means that one of your marketplace step that you use in your workflow uses the old version of this action. Try to update it if a new version is available or raise an issue on their repo. about this :
did someone plan to update node version of this action ?? |
Thank you fyi, i didn't check if |
Dear team, container-apps-deploy-action/action.yml Line 144 in 02d0451
Looks like it has been forgotten to update. |
It's easy to just update a string, but a significant version changes may contains breaking changes |
@afifurrohman-id, it looks like the action is already using node version 20. It is just a description that is not being up to date: container-apps-deploy-action/package.json Line 27 in 02d0451
|
That's just a library version, the problem itself not about the library, but the runtime itself. |
Hello @snehapar9 & @cormacpayne, this issue has been open for 10 months now...is there any plan for Microsoft to continue the development and security patching of this Action? Or has it been abandoned and we should just resort to direct AZ CLI commands to perform these operations? |
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20:
azure/container-apps-deploy-action@v2
. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/The text was updated successfully, but these errors were encountered: