October 14, 2022

Features

• This release introduces mechanisms to help resolve potential conflicting function configuration. See Set runtime options.
• Dropped support for Node.js versions 8, 10, and 12.
• In comparison to the console-configured integrations with Slack, Jira, or PagerDuty, with this advanced alerting mechanism you can fully customize the information sent to the third-party service. For example, you can include custom fields, helpful deep-links into the Firebase console, or add company-specific troubleshooting information.
• functions.logger.error now always outputs an error object and is included in Google Cloud Error Reporting. See PR #1141.
• Performance Monitoring now lets you set up alerting to third-party services using Cloud Functions for Firebase. For example, you can write a function that captures an alert event for slow app start time and posts the alert information to a third-party service, like Discord, Slack, or Jira.
• Logs created with the functions.logger package in 2nd gen functions are now annotated with each request's trace ID, making it easy to correlate log entries with the incoming request. Trace IDs are especially useful for cases where 2nd gen's concurrency feature permits a function to handle multiple requests at any given time. See Correlate log entries to learn more.
• Event parameters for 2nd generation functions are now strongly typed, permitting stronger TypeScript types for matched parameters.
• Reworked the apps library and Removed lodash as a runtime dependency. See PR 1144.
• Dropped support for Admin SDK versions 8 and 9. Update with npm install firebase-admin@latest --save.
• Reorganized source code location. This affects only apps that directly import files instead of using the recommend entry points specified in the package exports. See PR 1149.
• Crashlytics now lets you set up customized alerting to third-party services using Cloud Functions for Firebase. For example, you can write a function that captures an alert event for velocity alerts and posts the alert information to a third-party service, like Discord, Slack, or Jira.
• App Distribution now lets you set up advanced alerting to third-party services using Cloud Functions for Firebase. For example, you can write a function that captures an alert event for the registration of a new Apple device and posts the alert information to a third-party service, like Discord, Slack, or Jira.
• Deprecated allowInvalidAppCheckToken option. Instead use enforceAppCheck.
• To learn more about advanced alerts, see Set up advanced alerting to third-party services, and check out an example of handling a Crashlytics alert event.
• To learn more about advanced alerts, see Set up advanced alerting to third-party services, and check out an example of handling a Performance Monitoring alert event.
• Removed the functions.handler namespace.
• App Check enforcement on callable functions is disabled by default in v4. Requests containing invalid App Check tokens won't be denied unless you explicitly enable App Check enforcement using the new enforceAppCheck option. Furthermore, when enforcement is enabled, callable functions will deny all requests without App Check tokens.
• Dropped support for Firebase Test SDK for Cloud Functions version 2. Update with npm install firebase-functions-test@latest --save.
• The logging severity of Auth/App Check token validation has changed from info to debug level.
• To learn more about App Distribution alerts, see Receive alerts, and check out an example of handling an App Distribution alert event.
• This release introduces parameterized configuration for environment configuration, providing strongly typed configuration that is available both at runtime and deploy time.
• This release introduces 2nd-gen beta support for these background triggers:
• Removed \_\_trigger object on function handlers. See PR 1150.
• The Realtime Database DataSnapshot passed to the Realtime Database trigger now matches the DataSnapshot returned by the Admin SDK, with null values removed. See PR #926.