chore(firestore-bigquery-export): bump runtime to Node.js 22 for v1 functions#2727
chore(firestore-bigquery-export): bump runtime to Node.js 22 for v1 functions#2727
Conversation
…unctions Bumps the Cloud Functions runtime from nodejs20 to nodejs22 on the v1 functions branch, so users affected by the root wildcard regression (#2396) can continue using v1 triggers on a supported runtime.
There was a problem hiding this comment.
Code Review
This pull request updates the firestore-bigquery-export extension to version 0.1.61 and upgrades the Cloud Functions runtime from Node.js 20 to Node.js 22 across multiple resources. Feedback suggests ensuring that the package.json engines and @types/node dependencies are also updated to maintain consistency with the new runtime environment.
| then exports the changes into BigQuery. | ||
| properties: | ||
| runtime: nodejs20 | ||
| runtime: nodejs22 |
There was a problem hiding this comment.
When bumping the runtime to Node.js 22, it is important to maintain consistency in the project metadata. The functions/package.json file (which is not included in this diff) should be updated to include "engines": { "node": "22" } and the @types/node dependency should be updated to ^22.0.0 (currently ^20.4.4). This ensures that the local development environment, type checking, and build process are all aligned with the target production runtime.
Bumps the Cloud Functions runtime from nodejs20 to nodejs22 on the v1 functions branch, so users affected by the root wildcard regression (#2396) can continue using v1 triggers on a supported runtime.