You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: `FirebaseExtended/action-hosting-deploy@v0`. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026.
We use `FirebaseExtended/action-hosting-deploy@v0` in `.github/workflows/firebase-hosting-release.yml` to deploy the website. The action's own `action.yml` still declares `using: "node20"` as of the latest release (v0.10.0, 2025-08-18) and the repo has no Node 24 release yet.
Opt into Node 24 early — set `FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true` on the workflow / job and verify deploys still work. Buys us certainty before the June cutover.
Replace the action — deploy Firebase Hosting via `firebase-tools` directly in a `run:` step (we already depend on `firebase-tools` in devDependencies). Removes the third-party action entirely.
Suggested path
Start with option 2 (opt-in flag) on a draft PR to verify the action works under Node 24. If it does, land that as a holding fix. If upstream hasn't shipped a Node 24 release by ~August 2026, migrate to option 3.
Files
`.github/workflows/firebase-hosting-release.yml` — the only workflow using this action.
Problem
The Release workflow annotates every run with:
We use `FirebaseExtended/action-hosting-deploy@v0` in `.github/workflows/firebase-hosting-release.yml` to deploy the website. The action's own `action.yml` still declares `using: "node20"` as of the latest release (v0.10.0, 2025-08-18) and the repo has no Node 24 release yet.
Upstream issues tracking this (both still open):
Timeline
Options
Suggested path
Start with option 2 (opt-in flag) on a draft PR to verify the action works under Node 24. If it does, land that as a holding fix. If upstream hasn't shipped a Node 24 release by ~August 2026, migrate to option 3.
Files