From ffbea4857c6d7d8cae2a4f0b9912c03579ba9d44 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Niklas=20Lamp=C3=A9n?= Date: Sun, 31 May 2026 20:33:40 +0300 Subject: [PATCH] @ ci(release): opt Firebase deploy into Node 24 (#388) FirebaseExtended/action-hosting-deploy@v0 still declares `using: node20`, which GitHub has deprecated: Node 20 actions are forced to Node 24 from 2026-06-02 and Node 20 is removed from runners on 2026-09-16. Set FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true on the deploy job so the action runs under Node 24 ahead of the forced cutover. This is a holding fix; remove it once upstream ships a Node 24 release (tracked in #388). @ --- .github/workflows/firebase-hosting-release.yml | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/.github/workflows/firebase-hosting-release.yml b/.github/workflows/firebase-hosting-release.yml index b6b97f9e6..7d90b630c 100644 --- a/.github/workflows/firebase-hosting-release.yml +++ b/.github/workflows/firebase-hosting-release.yml @@ -15,6 +15,14 @@ on: jobs: build_and_deploy: runs-on: ubuntu-latest + # Force GitHub's runner to execute JavaScript actions on Node 24. The Firebase + # deploy action below still declares `using: node20`, which GitHub has deprecated: + # Node 20 actions are forced to Node 24 from 2026-06-02 and Node 20 is removed + # from runners on 2026-09-16. Opting in early verifies the action runs under + # Node 24 before the forced cutover. Remove this once + # FirebaseExtended/action-hosting-deploy ships a Node 24 release (issue #388). + env: + FORCE_JAVASCRIPT_ACTIONS_TO_NODE24: 'true' steps: - uses: actions/checkout@v6