firebase@12.15.0
📦 firebase-authView on GitHub →
✨ 3 features🐛 3 fixes⚡ 1 deprecations🔧 5 symbols
Summary
This release introduces the ability to initialize App Check without an explicit provider and merges the Firestore offline pipeline implementation. It also resolves a conflict between Auth and AppCheck when using ReCAPTCHA Enterprise.
Migration Steps
- If you rely on the old referrer policy for Auth API requests, note that it has been updated to strict-origin-when-cross-origin. This change is necessary for supporting HTTP Referrer-restricted API keys.
✨ New Features
- Ability to call initializeAppCheck without a provider in @firebase/app, @firebase/app-check, and firebase. If no provider is passed, App Check will attempt to initialize with a ReCaptchaEnterpriseProvider using the site key found in the project config.
- Merge of offline pipeline implementation in @firebase/firestore.
- Support for ABT realtime when remote config variant value matches the default parameter value in @firebase/remote-config.
🐛 Bug Fixes
- Fixed an error causing conflicts between Auth and AppCheck when both services use ReCAPTCHA Enterprise (@firebase/app-check, @firebase/auth).
- Wrapped params.systemInstruction with formatSystemInstruction() in the ChatSession constructor in @firebase/ai.
- Updated referrer policy for auth API requests from no-referrer to strict-origin-when-cross-origin to support HTTP Referrer-restricted API keys in browser environments (@firebase/auth, @firebase/auth-compat).
Affected Symbols
⚡ Deprecations
- The GoogleMaps.enableWidget function in @firebase/ai has been deprecated following the announcement by the Grounding for Google Maps service.