Auto-update dependencies.

[dpebot]

Brought to you by your friendly Repository Gardener.

[gemini-code-assist]

Summary of Changes

Hello @dpebot, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request performs an automated update of project dependencies, encompassing both Ruby gems and CocoaPods. The primary goal is to maintain the project's health by incorporating the latest stable versions of libraries, thereby benefiting from recent bug fixes, performance improvements, and security enhancements across various Firebase and Google components.

Highlights

• Ruby Dependency Updates: The Gemfile.lock file has been updated to include newer versions of Ruby gems: bigdecimal is now at 3.3.0 (from 3.2.3) and json is at 2.15.1 (from 2.15.0).
• CocoaPods Dependency Updates: Numerous CocoaPods dependencies across various Firebase-related modules (e.g., FirebaseAnalytics, FirebaseCore, FirebaseAuth, FirebaseFirestore, FirebaseMessaging, FirebasePerformance, FirebaseStorage, FirebaseABTesting, FirebaseRemoteConfig, FirebaseInstallations, FirebaseAppCheckInterop, FirebaseAuthInterop, FirebaseCoreExtension, FirebaseRemoteConfigInterop, FirebaseSharedSwift, FirebaseSessions, FirebaseAppDistribution, FirebaseInAppMessaging) and Google-related pods (GoogleAdsOnDeviceConversion, GoogleAppMeasurement) have been updated. Most of these updates are minor or patch versions, moving from 12.3.x to 12.4.x or 3.0.x to 3.1.x.
• Checksum Refresh: All updated CocoaPods dependencies have had their corresponding SPEC CHECKSUMS refreshed in the Podfile.lock files to reflect the new versions and ensure integrity.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[gemini-code-assist]

Code Review

This pull request is an automated dependency update from Repository Gardener. It bumps versions for several Ruby gems in Gemfile.lock and numerous CocoaPods across various Podfile.lock files, mainly for the Firebase SDK. The updates are consistent, for example, upgrading Firebase libraries from 12.3.0 to 12.4.0. These are minor version increments, which should be backward-compatible. The changes appear correct and consistent for an automated update. Merging is recommended after all continuous integration checks have passed successfully.