Bump firebase from 11.10.0 to 12.17.1

[dependabot]

Bumps firebase from 11.10.0 to 12.17.1.

Release notes

Sourced from firebase's releases.

firebase@12.17.1

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

What's Changed

@​firebase/data-connect@​0.7.3

Patch Changes

• 79d7011 #10221 - Align SQL Connect Stream Transport exponential backoff parameters with other platform SDKs. No need for public release note.

• b0e23db #10217 - Add grpc request header for platform name and sdk version to enable metrics collection in cloud monitoring.

@​firebase/database-compat@​2.1.6

Patch Changes

• 993e8a6 #10243 (fixes #10242) - Fix regression causing peerDeps to be unbundled in standalone bundle.

firebase@12.17.1

Patch Changes

• Updated dependencies [993e8a6, 79d7011, b0e23db]:
  • @​firebase/database-compat@​2.1.6
  • @​firebase/data-connect@​0.7.3

firebase@12.17.0

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

What's Changed

@​firebase/ai@​2.14.0

Minor Changes

• 7c5e6e5 #10145 - Added support for text-to-speech capabilities (both single- and multi-speaker configurations) for non-Live API models (for example, Gemini TTS models).

• 178daf7 #10184 - Deprecated VertexAIBackend in favor of AgentPlatformBackend to reflect the renaming of Vertex AI to Gemini Enterprise Agent Platform.

  The only difference for AgentPlatformBackend is the default location for accessing the model. The default location for AgentPlatformBackend is global, whereas the default location for VertexAIBackend is us-central1. To use us-central1 with AgentPlatformBackend, specify getAI(app, { backend: new AgentPlatformBackend('us-central1') }) when initializing the SDK. However, note that most new Gemini models do not support us-central1.

Patch Changes

• Updated dependencies [736fa3f]:
  • @​firebase/util@​1.15.2
  • @​firebase/component@​0.7.4

@​firebase/app@​0.16.0

Minor Changes

• 177f08d #10210 - Remove ability to call initializeAppCheck without a provider.

... (truncated)

Commits

• 30eceb5 Version Packages (#10257)
• 5672537 Merge main into release
• 2225728 chore: add merge-to-main workflow and fix git tag (#10240)
• b0e23db feat(data-connect): add "X-Client-Version" header for cloud monitoring (#10217)
• 993e8a6 fix(database-compat): fix regression in standalone bundle (#10243)
• 7e400dd Upgrade workflow actions versions of official actions to the latest versions....
• f76a8c3 Merge branch 'release'
• d459c97 Version Packages (#10227)
• 79d7011 feat(data-connect): Align SQL Connect Stream Transport Exponential Backoff Pa...
• a799b16 Merge main into release
• Additional commits viewable in compare view

[socket-security]

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	next@​15.2.3 ⏵ 15.0.7			+2	+49
	firebase@​11.10.0 ⏵ 12.17.1	+1		+1	+2
	eslint-config-prettier@​9.1.2 ⏵ 10.1.8	+1		+29
	tailwindcss@​3.4.19 ⏵ 4.3.3	+3		-3
	eslint@​9.39.3 ⏵ 10.8.1				-1

View full report

[socket-security]

Warning

Review the following alerts detected in dependencies.

According to your organization's Security Policy, it is recommended to resolve "Warn" alerts. Learn more about Socket for GitHub.

Action	Severity	Alert  (click "▶" to expand/collapse)
Warn		Critical CVE: Authorization Bypass in Next.js Middleware CVE: GHSA-f82v-jwr5-mffw Authorization Bypass in Next.js Middleware (CRITICAL) Affected versions: >= 13.0.0 < 13.5.9; >= 14.0.0 < 14.2.25; >= 15.0.0 < 15.2.3; >= 12.0.0 < 12.3.5 Patched version: 15.2.3 From: package-lock.json → npm/next@15.0.7 ℹ Read more on: This package | This alert | What is a critical CVE? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Remove or replace dependencies that include known critical CVEs. Consumers can use dependency overrides or npm audit fix --force to remove vulnerable dependencies. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/next@15.0.7. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		Obfuscated code: npm next is 90.0% likely obfuscated Confidence: 0.90 Location: Package overview From: package-lock.json → npm/next@15.0.7 ℹ Read more on: This package | This alert | What is obfuscated code? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/next@15.0.7. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		Obfuscated code: npm next is 90.0% likely obfuscated Confidence: 0.90 Location: Package overview From: package-lock.json → npm/next@15.0.7 ℹ Read more on: This package | This alert | What is obfuscated code? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/next@15.0.7. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		Obfuscated code: npm next is 90.0% likely obfuscated Confidence: 0.90 Location: Package overview From: package-lock.json → npm/next@15.0.7 ℹ Read more on: This package | This alert | What is obfuscated code? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/next@15.0.7. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		Obfuscated code: npm next is 90.0% likely obfuscated Confidence: 0.90 Location: Package overview From: package-lock.json → npm/next@15.0.7 ℹ Read more on: This package | This alert | What is obfuscated code? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/next@15.0.7. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

View full report

[dependabot]

Looks like firebase is up-to-date now, so this is no longer needed.