Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
_{You have signed the CLA already but the status is still pending? Let us recheck it.}

Up to standards ✅

_{NEW Get contextual insights on your PRs based on Codacy's metrics, along with PR and Jira context, without leaving GitHub. Enable AI reviewer
TIP This summary will be updated as you push new changes.}

Greptile Summary

Pins FirebaseExtended/action-hosting-deploy to a specific commit SHA (500ac625) that bumps the action's declared runtime from node20 to node24, resolving auth failures caused by GitHub Actions now forcing node20 actions to run under Node 24. The @v0 tag still resolves to the pre-fix v0.10.0 release, so a direct commit pin is the only viable workaround until an official release tag is cut.

• web.yml: Replaces FirebaseExtended/action-hosting-deploy@v0 with @500ac625ca2dd40cbd15f7659af953801858032a; all other workflow steps (validate, Cloudflare deploy) are unchanged.
• Using a full commit SHA is the recommended security practice for third-party GitHub Actions and is more tamper-proof than a mutable tag, but it should carry an inline comment so future maintainers know to upgrade once a proper release is available.

Confidence Score: 4/5

Safe to merge — a one-line CI dependency update with a well-understood motivation and no changes to application code or secrets handling.

The change is minimal and targeted: it replaces a floating @v0 tag with a full commit SHA that carries the Node 24 runtime fix. Using a full SHA is actually more tamper-proof than the tag it replaces. The only open question is whether the pinned commit may pull in other unreleased changes from upstream main, and there is no inline comment to guide future maintainers when an official release tag is eventually cut.

.github/workflows/web.yml — the bare commit SHA should get a short comment explaining the workaround so it is not inadvertently reverted to @v0 later.

Important Files Changed

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart TD
    A[Push to main] --> B[validate job\nNode 24 matrix]
    B --> |lint + test + build| C{validate passed?}
    C -- No --> D[CI fails]
    C -- Yes --> E[deploy job]
    E --> F[Build 🏗️]
    F --> G[Cloudflare Deploy\nwrangler-action@v4]
    F --> H[Firebase Deploy\naction-hosting-deploy@500ac625\nNode 24 runtime]
    G --> I[Deployed to\nCloudflare Pages]
    H --> J[Deployed to\nFirebase Hosting\nlive channel]

%%{init: {'theme': 'base', 'themeVariables': {"darkMode": true, "background": "#0d1117", "primaryColor": "#21262d", "primaryTextColor": "#e6edf3", "primaryBorderColor": "#8b949e", "lineColor": "#8b949e", "textColor": "#e6edf3", "edgeLabelBackground": "#161b22", "actorBkg": "#21262d", "actorBorder": "#8b949e", "actorTextColor": "#e6edf3", "actorLineColor": "#8b949e", "signalColor": "#8b949e", "signalTextColor": "#e6edf3", "noteBkgColor": "#373320", "noteBorderColor": "#d4a72c", "noteTextColor": "#f0e6c0", "labelBoxBkgColor": "#21262d", "labelBoxBorderColor": "#8b949e", "labelTextColor": "#e6edf3", "loopTextColor": "#e6edf3", "activationBkgColor": "#30363d", "activationBorderColor": "#8b949e"}}}%%
flowchart TD
    A[Push to main] --> B[validate job\nNode 24 matrix]
    B --> |lint + test + build| C{validate passed?}
    C -- No --> D[CI fails]
    C -- Yes --> E[deploy job]
    E --> F[Build 🏗️]
    F --> G[Cloudflare Deploy\nwrangler-action@v4]
    F --> H[Firebase Deploy\naction-hosting-deploy@500ac625\nNode 24 runtime]
    G --> I[Deployed to\nCloudflare Pages]
    H --> J[Deployed to\nFirebase Hosting\nlive channel]

_{Reviews (1): Last reviewed commit: "Fix Firebase Deploy CI failure: pin acti..." | Re-trigger Greptile}