Azure/container-apps-deploy-action

`Node.js 16 actions are deprecated. `

afifurrohman-id opened this issue ยท 8 comments

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/

Is container-apps-deploy-action deprecated?

@afifurrohman-id for

azure/login@v1

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 :
Getting action download info
Download action repository 'azure/login@v1'

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 :

azure/container-apps-deploy-action@v2

did someone plan to update node version of this action ??

You must have a step in your workflow which uses this action v1 and you can then replace it with azure/login@v2

Thank you fyi, i didn't check if azure-login have v2.

Dear team,
Could you please have a look at this line:

using: 'node16'

Looks like it has been forgotten to update.

Dear team, Could you please have a look at this line:

using: 'node16'

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:

"@types/node": "^20.6.0"

@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:

"@types/node": "^20.6.0"

That's just a library version, the problem itself not about the library, but the runtime itself.

https://docs.github.com/en/actions/creating-actions/metadata-syntax-for-github-actions#runs-for-javascript-actions

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?