Upgrade Algolia Search Extension Node.js 2 & Cloud Functions v2

[unbroken360]

The Firestore Algolia Search extension currently creates functions using Node.js 18 and Cloud Functions v1, despite Node.js 18 being deprecated (EOL on April 30, 2025).

• Changing the runtime manually in Google Cloud Console to Node.js 20 causes deployment failures.
• New extension installations still default to Node.js 18 and v1 functions.

[mike24dzy]

I noticed the same warnings on GCP as well for the Cloud Functions, when can we expect an update on this?

[Andre1992]

I am also noticing this now, the other extensions you can manually change runtime node.js version in package.json in GCP but Algolia CF does not have that and will cause deploy failure as previously stated. Are the Algolia team working on this or not? @smomin @Haroenv @e-krebs

[bilabror]

I’ve created a PR #233
hopefully, the Algolia team has time to review my PR and merge the code as soon as possible

[harryp1989]

I sent a message to algolia yesterday and looks like they merged it. Not sure how it works to then get the latest version into firebase as an upgrade?

[smomin]

Here is the RC for the extension using the supported version of Node. Please test it out and let me know. https://console.firebase.google.com/project/_/extensions/install?ref=algolia/firestore-algolia-search@1.2.9-rc.0

[bilabror]

@smomin I tested it just now, everything looks good on my end!

1. Setup: OK
2. Adding doc: OK
3. Editing doc: OK
4. Deleting doc: OK

[smomin]

I am uploading a stable build.

[seanblonien]

In the RC version when re-installing I only see the Node 22 runtime updated, but it still uses V1 cloud functions, not fully addressing the issue at hand -- just want to bring up the fact that V1 cloud functions are still in 1.2.9-rc.0

[smomin]

The Firebase Extension documentation supports both V1 & V2 as a mixed approach. Not all features are on V2.

@seanblonien if you have a PR in mind, I can take a look at it.

[seanblonien]

Oh didn't know it was on Google/Firebase's extension framework's end to not support V2 -- yea don't have a PR, seems like V2 being supported first is the pre-req before the task handlers can be updated and such

is there a firebase extensions Github issue or something that we can tag if this is a blocking issue to upgrade to V2?

[harryp1989]

Anyone else experiencing strange things with the field that allows you to update the "Extension instance ID. Sometimes it doesnt show as an option and then sometimes I enter it correctly, but when saving it, it reverts back to a defauly name like "firestore-algolia-search-e8kq".

[Jonathan-Ironman]

I came here to report the same thing. Updating the ext still keeps it on Node 18 even though the PR was merged in April?
How do I upgrade it?

The version published to Firebase Extension Hub is 1.2.10