Request: release containing Node 24 runtime bump (PR #450)

[jmp-csm]

Hi maintainers — thanks for this action, we use it heavily across our portfolio.

Request

Could you cut a release (e.g. v0.10.1 or v0.11.0) containing the Node 24 runtime bump from #450 (commit 500ac62)?

Why this is time-sensitive

GitHub forces Node.js 24 as the Actions runtime default on 2026-06-02. Actions whose internal runtime is still Node 20 will begin emitting hard errors on that date. The latest stable release (v0.10.0, 2025-08-18) and the floating @v0 tag both still declare using: node20 in action.yml, while main has the fix sitting unreleased since 2026-04-30.

Roadmap question

Is a release on the near-term roadmap? If yes, knowing a rough ETA would help us plan. If no, would you consider tagging one before 2026-06-02?

Our workaround in the meantime

We are pinning to commit SHA 500ac62 directly with an inline comment to revert to a normal tag pin as soon as a release ships. Sharing in case other consumers run into the same situation.

Thanks!

[danielsigl]

Please release it, we are also using it heavily...Thank you!

[anisabboud]

We're still encountering the Github Actions warning:

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 16th, 2026. Node.js 20 will be removed from the runner on September 16th, 2026.

As mentioned above, this was fixed in #448 (April 30, 2026), but the issue persists because there hasn't been a release since.
The last release is from Aug 18, 2025 https://github.com/FirebaseExtended/action-hosting-deploy/releases.

[nathanblaubach]

@jhuleatt I see that you've done all of the releases for this action so far. Can you cut the new release?