Node.js 16 actions are deprecated

[rohit231095]

I am seeing this below warning in my project's GitHub actions repeatedly. This Firebase deployment action needs an upgrade to Node.js 18 or 20 as version 16 actions are deprecated.

Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: FirebaseExtended/action-hosting-deploy@v0. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.

Please upgrade this action as soon as possible.

[MNITD]

@rohit231095 do you have only the warning in the console or the action is broken as well?

[rohit231095]

@MNITD I can see only a warning like the image below. The action is still working, and deployment is not broken.

Reporting it to prevent any incoming breaking possibilities later on.

[oyvindwe]

I have already submitted PR #340 to address this.

Would be good if some of the maintainers could follow up before Node 16 is sunset!

[oyvindwe]

Actions are now failing:

That is most likely some other problem with your job. Sunset date for node 16 has not yet been communicated.

[annoyingmouse]

Actions are now failing:

That is most likely some other problem with your job. Sunset date for node 16 has not yet been communicated.

You are right - please accept my apologies!

[filfreire]

FYI, while maintainers don't merge @oyvindwe's PR #340 that fixes this warning, you can edit your action usage to point to the PR's commit directly:

-FirebaseExtended/action-hosting-deploy@v0
+FirebaseExtended/action-hosting-deploy@79b1a830a9ae85409cb38056dd7761f6f1cb83fd

[johnnyoshika]

This workaround to set a node version doesn't work:

      - uses: actions/setup-node@v4
        with:
          node-version: '18'

When using FirebaseExtended/action-hosting-deploy@v0 I still get this warning:

Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: FirebaseExtended/action-hosting-deploy@v0. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.

[steve-scorn]

This appears to have now been enforced, making this action no longer usable.

The only way I could get it to work was by using @filfreire 's solution above. Is it possible to get PR #340 merged?

[oyvindwe]

@johnnyoshika

This workaround to set a node version doesn't work:

This is to set the node version your build uses, not the version used by the action itself.

@steve-scorn:

This appears to have now been enforced, making this action no longer usable.

For now, you can work around this issue by setting the environment variabel ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true, but that will stop working May 13. See https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/

[testak-m]

I asked if it would be possible to release #344 since it would be resolved once it was released.
#344 (comment)

[jhonnycgarcia]

The error is still occurring.

[oyvindwe]

The error is still occurring.

It will occur until a fix is merged and released.

Workaround is described here: #341 (comment)

[oyvindwe]

Fixed by #344

This issue can be closed. Can we please get a release?

[memark]

@wayzie-jm AFAICT the fix has only been merged, not released.

[wayzie-jm]

@wayzie-jm AFAICT the fix has only been merged, not released.

Rookie mistake. Thanks.

[Danish-Dsouza]

What does one have to do to get a release around here?