Skip to content

Update dependency firebase to v12.15.0 - #4026

Merged
amitsingh-007 merged 1 commit into
renovate-updatesfrom
renovate/firebase-12.x
Jul 8, 2026
Merged

amitsingh-007 merged 1 commit into
renovate-updatesfrom
renovate/firebase-12.x

Conversation

@amitsingh-007

@amitsingh-007 amitsingh-007 commented Jul 8, 2026 •

Copy link
Copy Markdown
Owner

ℹ️ Note

This PR body was truncated due to platform limits.

This PR contains the following updates:

Package Change Age Confidence
firebase (source, changelog) 12.12.1 → 12.15.0 age confidence

Release Notes

firebase/firebase-js-sdk (firebase)

v12.15.0

Compare Source

For more detailed release notes, see Firebase JavaScript SDK Release Notes.

What's Changed

@​firebase/app@​0.15.0

Minor Changes
  • 420156e #​10023 - Add ability to call initializeAppCheck without a provider. If no provider is passed to initializeAppCheck, App Check will attempt to initialize with a ReCaptchaEnterpriseProvider using the site key found in the recaptchaSiteKey field of the Firebase project config.

@​firebase/app-check@​0.12.0

Minor Changes
  • 420156e #​10023 - Add ability to call initializeAppCheck without a provider. If no provider is passed to initializeAppCheck, App Check will attempt to initialize with a ReCaptchaEnterpriseProvider using the site key found in the recaptchaSiteKey field of the Firebase project config.
Patch Changes
  • e389f70 #​9991 (fixes #​9405) - Fix error causing Auth and AppCheck conflict when both are using ReCAPTCHA Enterprise.

firebase@​12.15.0

Minor Changes
  • 043c0ab #​9929 - Merge offline pipeline implementation with one minor API change

  • 420156e #​10023 - Add ability to call initializeAppCheck without a provider. If no provider is passed to initializeAppCheck, App Check will attempt to initialize with a ReCaptchaEnterpriseProvider using the site key found in the recaptchaSiteKey field of the Firebase project config.

Patch Changes

@​firebase/firestore@​4.16.0

Minor Changes
  • 043c0ab #​9929 - Merge offline pipeline implementation with one minor API change

@​firebase/ai@​2.13.1

Patch Changes
  • 9bef5ab #​10035 - Deprecated GoogleMaps.enableWidget, following the announcement by the Grounding for Google Maps service.

  • 6a9d3d1 #​10026 (fixes #​9006) - Wrap params.systemInstruction with formatSystemInstruction() in the ChatSession constructor.

@​firebase/app-check-compat@​0.4.5

Patch Changes

@​firebase/app-compat@​0.5.14

Patch Changes

@​firebase/auth@​1.13.3

Patch Changes
  • e389f70 #​9991 (fixes #​9405) - Fix error causing Auth and AppCheck conflict when both are using ReCAPTCHA Enterprise.

  • 712091c #​10049 - Update 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-compat@​0.6.8

Patch Changes
  • 712091c #​10049 - Update 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.

  • Updated dependencies [e389f70, 712091c]:

  • @​firebase/auth@​1.13.3

@​firebase/firestore-compat@​0.4.11

Patch Changes

@​firebase/remote-config@​0.8.5

Patch Changes
  • 33521f2 #​10000 - Support ABT realtime when variant value matches default value of parameter

@​firebase/remote-config-compat@​0.2.26

Patch Changes

v12.14.0

Compare Source

For more detailed release notes, see Firebase JavaScript SDK Release Notes.

What's Changed

@​firebase/ai@​2.13.0

Minor Changes
  • f0752a0 #​9800 - Add initializeDeviceModel() method to allow explicit initialization of on-device model in hybrid mode.

  • bd08cae #​9926 - Change "beta" (public preview) tags to "public" (generally available) for all hybrid inference features.

Patch Changes
  • bd2644b #​9956 (fixes #​9938) - Fix a bug that caused ChatSession.sendMessageStream() and TemplateChatSession.sendMessageStream() to send duplicate user turns in the request.

firebase@​12.14.0

Minor Changes
  • 3b337b9 #​9917 - Add new API and deprecate old API for creating and deleting fcm registration

  • f0752a0 #​9800 - Add initializeDeviceModel() method to allow explicit initialization of on-device model in hybrid mode.

  • d5b0f61 #​9913 - Added minimum and maximum FieldValue operations

  • bd08cae #​9926 - Change "beta" (public preview) tags to "public" (generally available) for all hybrid inference features.

Patch Changes

@​firebase/firestore@​4.15.0

Minor Changes
Patch Changes
  • 85f6f4e #​9985 - Improved robustness and logging in query listen stream creation and re-creation

@​firebase/messaging@​0.13.0

Minor Changes
  • 3b337b9 #​9917 - Add new API and deprecate old API for creating and deleting fcm registration
Patch Changes
  • a1a2455 #​9916 - Fix delivery metrics Firelog flushing when BigQuery export is enabled: schedule the first flush immediately (next timer tick) instead of waiting a full LOG_INTERVAL_IN_MS, start processing only when there are queued events (so enabling export with an empty queue does not arm a day-long idle timer that blocks later stageLog flushes), and ensure staging a log starts the service when needed. When export is disabled, clear any queued events and cancel pending flush timers immediately (rather than waiting for the background loop).

  • Updated dependencies [3b337b9]:

  • @​firebase/messaging-interop-types@​0.2.5

@​firebase/app@​0.14.13

Patch Changes
  • Update SDK_VERSION.

@​firebase/app-check@​0.11.4

Patch Changes
  • d675580 #​9987 - Fix a bug where getLimitedUseToken() did not correctly get a limited use token because it did not send the limited_use param.

@​firebase/app-check-compat@​0.4.4

Patch Changes

@​firebase/app-compat@​0.5.13

Patch Changes

@​firebase/auth@​1.13.2

Patch Changes
  • 2697919 #​9845 (fixes #​9732) - Updated _isAvailable() to use retry logic for the initial IndexedDB availability check, preventing incorrect fallbacks to in-memory persistence in environments where transactions may occasionally drop on startup.

@​firebase/auth-compat@​0.6.7

Patch Changes
  • 2697919 #​9845 (fixes #​9732) - Updated _isAvailable() to use retry logic for the initial IndexedDB availability check, preventing incorrect fallbacks to in-memory persistence in environments where transactions may occasionally drop on startup.

  • Updated dependencies [2697919]:

  • @​firebase/auth@​1.13.2

@​firebase/data-connect@​0.7.1

Patch Changes
  • 51e93fc #​9936 - Eliminated the 1-minute delay before closing idle backend connections to save resources.

@​firebase/firestore-compat@​0.4.10

Patch Changes

@​firebase/functions@​0.13.5

Patch Changes

@​firebase/functions-compat@​0.4.5

Patch Changes

@​firebase/messaging-compat@​0.2.27

Patch Changes

@​firebase/messaging-interop-types@​0.2.5

Patch Changes
  • 3b337b9 #​9917 - Add new API and deprecate old API for creating and deleting fcm registration

@​firebase/remote-config@​0.8.4

Patch Changes
  • 4d3f71a #​9981 - Call update experiment when the last running experiment is stopped

@​firebase/remote-config-compat@​0.2.25

Patch Changes

v12.13.0

Compare Source

For more detailed release notes, see Firebase JavaScript SDK Release Notes.

What's Changed

@​firebase/ai@​2.12.0

Minor Changes
  • ffa39f6 #​9795 - Added LiveSession.resumeSession() to allow resuming a previous LiveSession. Also added contextWindowCompression feature.

  • 86dc0db #​9819 - Added support for ImageConfig (aspect ratio and size).
    Expanded FinishReason values to include all currently available values provided by the models.

  • 345c5f6 #​9458 - AI Logic : Feature : Added support for Grounding with Google Maps.

Patch Changes

@​firebase/data-connect@​0.7.0

Minor Changes
  • 714b41d #​9905 - Hardened the Firebase SQL Connect streaming transport with intelligent reconnection, query de-duplication, and resume optimizations.
Patch Changes

firebase@​12.13.0

Minor Changes
  • ffa39f6 #​9795 - Added LiveSession.resumeSession() to allow resuming a previous LiveSession. Also added contextWindowCompression feature.

  • 714b41d #​9905 - Hardened the Firebase SQL Connect streaming transport with intelligent reconnection, query de-duplication, and resume optimizations.

  • 86dc0db #​9819 - Added support for ImageConfig (aspect ratio and size).
    Expanded FinishReason values to include all currently available values provided by the models.

  • 345c5f6 #​9458 - AI Logic : Feature : Added support for Grounding with Google Maps.

Patch Changes

@​firebase/analytics@​0.10.22

Patch Changes

@​firebase/analytics-compat@​0.2.28

Patch Changes

@​firebase/analytics-interop-types@​0.3.5

Patch Changes

@​firebase/analytics-types@​0.8.4

Patch Changes

@​firebase/app@​0.14.12

Patch Changes

@​firebase/app-check@​0.11.3

Patch Changes

@​firebase/app-check-compat@​0.4.3

Patch Changes

@​firebase/app-check-interop-types@​0.3.4

Patch Changes

@​firebase/app-check-types@​0.5.4

Patch Changes

@​firebase/app-compat@​0.5.12

Patch Changes

@​firebase/app-types@​0.9.5

Patch Changes

@​firebase/auth@​1.13.1

Patch Changes

@​firebase/auth-compat@​0.6.6

Patch Changes

@​firebase/auth-interop-types@​0.2.5

Patch Changes

@​firebase/auth-types@​0.13.1

Patch Changes

@​firebase/component@​0.7.3

Patch Changes

@​firebase/database@​1.1.3

Patch Changes

@​firebase/database-compat@​2.1.4

Patch Changes

@​firebase/database-types@​1.0.20

Patch Changes

@​firebase/firestore@​4.14.1

Patch Changes

@​firebase/firestore-compat@​0.4.9

Patch Changes

@​firebase/firestore-types@​3.0.4

Patch Changes

@​firebase/functions@​0.13.4

Patch Changes

@​firebase/functions-compat@​0.4.4

Patch Changes

@​firebase/functions-types@​0.6.4

Patch Changes

@​firebase/installations@​0.6.22

Patch Changes

@​firebase/installations-compat@​0.2.22

Patch Changes

@​firebase/installations-types@​0.5.4

Patch Changes

@​firebase/logger@​0.5.1

Patch Changes

@​firebase/messaging@​0.12.26

Patch Changes

@​firebase/messaging-compat@​0.2.26

Patch Changes

@​firebase/messaging-interop-types@​0.2.4

Patch Changes

@​firebase/performance@​0.7.12

Patch Changes

@​firebase/performance-compat@​0.2.25

Patch Changes

@​firebase/performance-types@​0.2.4

Patch Changes

@​firebase/remote-config@​0.8.3

Patch Changes

✂ Note

PR body was truncated to here.


Configuration

📅 Schedule: (UTC)

  • Branch creation
    • Between 12:00 AM and 03:59 AM, on day 1 of the month (* 0-3 1 * *)
  • Automerge
    • At any time (no schedule defined)

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR has been generated by Mend Renovate.

Greptile Summary

This PR bumps the firebase npm package from 12.12.1 to 12.15.0 via Renovate, updating the pnpm workspace catalog entry and regenerating the lock file accordingly.

  • Three minor releases are included (12.13–12.15), bringing bug fixes to Firestore (pending-response race condition, query listen stream robustness), Auth (IndexedDB retry on startup, ReCAPTCHA Enterprise conflict with App Check, referrer-policy update), App Check (getLimitedUseToken limited-use param fix), and FCM delivery-metrics flushing. No application source files were changed — only the version pin and lockfile.
  • The @firebase/firestore 4.16.0 release notes mention "one minor API change" in the offline pipeline merge; if the application uses the offline persistence API directly, it is worth verifying no call sites are affected.

Confidence Score: 5/5

Dependency-only update with no application source changes; all modified files are the lock file and workspace catalog.

Only pnpm-lock.yaml and pnpm-workspace.yaml are touched. The three included firebase releases are patch/minor fixes (Auth, Firestore, App Check, FCM) with no removed APIs used by this codebase based on the diff. The lock file resolution looks consistent with the catalog change.

No files require special attention.

Reviews (1): Last reviewed commit: "Update dependency firebase to v12.15.0" | Re-trigger Greptile

@amitsingh-007
amitsingh-007 enabled auto-merge (squash) July 8, 2026 16:27
@qodo-code-review

Copy link
Copy Markdown

PR Summary by Qodo

Bump firebase to v12.15.0 (pnpm)

⚙️ Configuration changes 🕐 10-20 Minutes

Grey Divider

AI Description

• Upgrade firebase from 12.12.1 to 12.15.0.
• Refresh pnpm catalog and lockfile for updated @firebase transitive packages.
Diagram

graph TD
  A["App code"] --> B["pnpm-workspace.yaml"] --> C["pnpm-lock.yaml"] --> D{{"firebase@12.15.0"}} --> E{{"@firebase/*"}} --> F{{"re2js@0.4.3"}}

  subgraph Legend
    direction LR
    _svc["Internal"] ~~~ _file["Config/Lock"] ~~~ _ext{{"External package"}}
  end
Loading
High-Level Assessment

This is the standard, low-risk approach for Renovate-managed dependency upgrades: update the workspace catalog pin and regenerate the pnpm lockfile. Alternatives considered (but not recommended here) include deferring the bump or pinning specific @firebase subpackages independently, which increases drift and maintenance burden.

Files changed (2) +272 / -341

Other (2) +272 / -341
pnpm-lock.yamlLock firebase 12.15.0 and update resolved @firebase graph +271/-340

Lock firebase 12.15.0 and update resolved @firebase graph

• Updates the resolved firebase version to 12.15.0 and refreshes many @firebase subpackages to match. Introduces a new transitive dependency (re2js@0.4.3) and records new deprecation metadata for some packages already present.

pnpm-lock.yaml

pnpm-workspace.yamlBump firebase version in pnpm workspace catalog +1/-1

Bump firebase version in pnpm workspace catalog

• Updates the workspace catalog pin for firebase from 12.12.1 to 12.15.0 so all importers resolve the newer SDK consistently.

pnpm-workspace.yaml

@qodo-code-review

Copy link
Copy Markdown

Code Review by Qodo

🐞 Bugs (1) 📘 Rule violations (0) 📜 Skill insights (0)

Context used
✅ Compliance rules (platform): 22 rules

Grey Divider


Remediation recommended

1. Unpinned Node engine requirement 🐞 Bug ☼ Reliability
Description
Updated Firebase subpackages require Node >=20, but the repo does not declare an engines.node
constraint, so installs/builds can break in environments that default to older Node versions (local
dev or deployment). This is especially relevant because deployment config (Vercel) does not pin Node
either, while CI uses Node 24.
Code

pnpm-lock.yaml[R1300-1303]

+  '@firebase/app@0.15.0':
+    resolution: {integrity: sha512-soIskolmGgbpi0K/MfrjtdpO1220qRCbXA4Z8Qx3lM+fVwA3q40m+OM+7zBHd2nuQCrLXb33L6Oc1aBH3Y26AQ==}
    engines: {node: '>=20.0.0'}

-  '@firebase/auth-compat@0.6.5':
-    resolution: {integrity: sha512-IfVsafZ3QiXbsydXTP/XMI0wVYbJLI1rkb8Qqf03/h5FnL+upbbPOb+6Yj3RpcX+Y1iP5Uh18lxTHlXfbiyAow==}
Relevance

⭐⭐ Medium

No prior accepted reviews about adding root engines.node/Vercel pinning; CI bumped to Node 24
without engines change (PR #3743).

PR-#3743
PR-#3812

ⓘ Recommendations generated based on similar findings in past PRs

Evidence
The lockfile shows Firebase subpackages resolved by this PR require Node >=20, while the repo root
and Vercel config don’t declare/pin a Node version; CI happens to use Node 24 but that doesn’t
enforce the requirement elsewhere.

pnpm-lock.yaml[1289-1306]
package.json[1-34]
apps/web/vercel.json[1-8]
.github/workflows/build.yml[23-28]

Agent prompt
The issue below was found during a code review. Follow the provided context and guidance below and implement a solution

## Issue description
Firebase subpackages pulled in by `firebase@12.15.0` declare `engines.node >= 20`, but the repo doesn’t declare a Node engine/version contract in `package.json` (and Vercel config doesn’t pin Node either). This makes builds/deployments dependent on the ambient Node version.

## Issue Context
CI uses Node 24, but contributors/deploy targets may default to older Node versions unless explicitly pinned.

## Fix Focus Areas
- package.json[1-34]
- apps/web/vercel.json[1-8]
- pnpm-lock.yaml[1289-1306]
- .github/workflows/build.yml[23-28]

## Suggested fix
1. Add an engine requirement at the repo root (and optionally per-package if desired), e.g.:
  - `"engines": { "node": ">=20" }`
2. Consider adding a version pin file for developers/tooling (choose one): `.nvmrc`, `.tool-versions` (asdf), or Volta config.
3. Ensure deployment uses the same Node major (set in Vercel project settings and/or document it; if you prefer config-as-code, add a note or a check script since `vercel.json` doesn’t pin Node).
4. (Optional) Add a CI step to assert `node -v` satisfies the engines field.

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools


Grey Divider

Qodo Logo

Comment thread pnpm-lock.yaml
Comment on lines +1300 to 1303
'@firebase/app@0.15.0':
resolution: {integrity: sha512-soIskolmGgbpi0K/MfrjtdpO1220qRCbXA4Z8Qx3lM+fVwA3q40m+OM+7zBHd2nuQCrLXb33L6Oc1aBH3Y26AQ==}
engines: {node: '>=20.0.0'}

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Remediation recommended

1. Unpinned node engine requirement 🐞 Bug ☼ Reliability

Updated Firebase subpackages require Node >=20, but the repo does not declare an engines.node
constraint, so installs/builds can break in environments that default to older Node versions (local
dev or deployment). This is especially relevant because deployment config (Vercel) does not pin Node
either, while CI uses Node 24.
Agent Prompt
## Issue description
Firebase subpackages pulled in by `firebase@12.15.0` declare `engines.node >= 20`, but the repo doesn’t declare a Node engine/version contract in `package.json` (and Vercel config doesn’t pin Node either). This makes builds/deployments dependent on the ambient Node version.

## Issue Context
CI uses Node 24, but contributors/deploy targets may default to older Node versions unless explicitly pinned.

## Fix Focus Areas
- package.json[1-34]
- apps/web/vercel.json[1-8]
- pnpm-lock.yaml[1289-1306]
- .github/workflows/build.yml[23-28]

## Suggested fix
1. Add an engine requirement at the repo root (and optionally per-package if desired), e.g.:
   - `"engines": { "node": ">=20" }`
2. Consider adding a version pin file for developers/tooling (choose one): `.nvmrc`, `.tool-versions` (asdf), or Volta config.
3. Ensure deployment uses the same Node major (set in Vercel project settings and/or document it; if you prefer config-as-code, add a note or a check script since `vercel.json` doesn’t pin Node).
4. (Optional) Add a CI step to assert `node -v` satisfies the engines field.

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools

@amitsingh-007
amitsingh-007 merged commit 007362d into renovate-updates Jul 8, 2026
3 checks passed
@amitsingh-007
amitsingh-007 deleted the renovate/firebase-12.x branch July 8, 2026 16:50
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant