Skip to content

Auto-update dependencies. #1732

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Jul 18, 2025
Merged

Auto-update dependencies. #1732

merged 1 commit into from
Jul 18, 2025

Conversation

dpebot
Copy link
Collaborator

@dpebot dpebot commented Jul 17, 2025

Brought to you by your friendly Repository Gardener.

Copy link

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

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

Summary of Changes

Hello @dpebot, I'm Gemini Code Assist1! 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 is an automated dependency update, primarily focusing on upgrading various Firebase SDK components and GTMSessionFetcher to their latest major versions within the firestore/Podfile.lock file. This ensures the project's dependencies are kept up-to-date, benefiting from the latest features, bug fixes, and security improvements.

Highlights

  • Dependency Major Version Upgrades: Several core Firebase SDK components, including FirebaseAppCheckInterop, FirebaseAuth, FirebaseCore, and FirebaseFirestore, have been upgraded from version 11.15.0 to 12.0.0. This includes their internal dependencies like FirebaseCoreExtension, FirebaseCoreInternal, FirebaseAuthInterop, and FirebaseFirestoreInternal.
  • GTMSessionFetcher Update: The GTMSessionFetcher/Core dependency has been updated from version 4.5.0 to 5.0.0, and its version constraint within FirebaseAuth has been adjusted to < 6.0, >= 3.4.
  • Checksum Updates: All corresponding checksums for the updated pods in the Podfile.lock have been refreshed to reflect the new versions, ensuring integrity and consistency.
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 in your pull request via creating an issue comment (i.e. comment on the pull request page) using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands.

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 issue 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 is currently in preview and 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 to provide feedback.

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.

Copy link

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

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

Code Review

This pull request updates Firebase dependencies in Podfile.lock. It's important to verify the checksums and ensure compatibility with the updated versions.

Comment on lines +1197 to +1229
- FirebaseAppCheckInterop (12.0.0)
- FirebaseAuth (12.0.0):
- FirebaseAppCheckInterop (~> 12.0.0)
- FirebaseAuthInterop (~> 12.0.0)
- FirebaseCore (~> 12.0.0)
- FirebaseCoreExtension (~> 12.0.0)
- GoogleUtilities/AppDelegateSwizzler (~> 8.1)
- GoogleUtilities/Environment (~> 8.1)
- GTMSessionFetcher/Core (< 5.0, >= 3.4)
- GTMSessionFetcher/Core (< 6.0, >= 3.4)
- RecaptchaInterop (~> 101.0)
- FirebaseAuthInterop (11.15.0)
- FirebaseAuthInterop (12.0.0)
- FirebaseAuthUI (15.1.0):
- FirebaseAuth (< 13.0, >= 11.0)
- FirebaseCore
- FirebaseCore (11.15.0):
- FirebaseCoreInternal (~> 11.15.0)
- FirebaseCore (12.0.0):
- FirebaseCoreInternal (~> 12.0.0)
- GoogleUtilities/Environment (~> 8.1)
- GoogleUtilities/Logger (~> 8.1)
- FirebaseCoreExtension (11.15.0):
- FirebaseCore (~> 11.15.0)
- FirebaseCoreInternal (11.15.0):
- FirebaseCoreExtension (12.0.0):
- FirebaseCore (~> 12.0.0)
- FirebaseCoreInternal (12.0.0):
- "GoogleUtilities/NSData+zlib (~> 8.1)"
- FirebaseEmailAuthUI (15.1.0):
- FirebaseAuth
- FirebaseAuthUI (~> 15.0)
- FirebaseCore
- GoogleUtilities/UserDefaults
- FirebaseFirestore (11.15.0):
- FirebaseCore (~> 11.15.0)
- FirebaseCoreExtension (~> 11.15.0)
- FirebaseFirestoreInternal (= 11.15.0)
- FirebaseSharedSwift (~> 11.0)
- FirebaseFirestoreInternal (11.15.0):
- FirebaseFirestore (12.0.0):
- FirebaseCore (~> 12.0.0)
- FirebaseCoreExtension (~> 12.0.0)
- FirebaseFirestoreInternal (~> 12.0.0)
- FirebaseSharedSwift (~> 12.0.0)
- FirebaseFirestoreInternal (12.0.0):

Choose a reason for hiding this comment

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

high

This PR updates multiple Firebase dependencies across a major version boundary (v11 to v12), such as FirebaseAuth, FirebaseCore, and FirebaseFirestore. Major version updates frequently introduce breaking API changes. Without corresponding code changes to adapt to the new APIs, there is a high risk that this change will break the application's build or runtime behavior.

Comment on lines +1416 to +1426
FirebaseAppCheckInterop: c848d06a04030c9858ef0ae555b82035dbe470d0
FirebaseAuth: 654e4de84787c45d7265599a651038e854ccb439
FirebaseAuthInterop: 002da671896af5e8879ae117dc604ed240b86e80
FirebaseAuthUI: c574e8904bd14503ff47e55ba2fc9ec64aacaed6
FirebaseCore: efb3893e5b94f32b86e331e3bd6dadf18b66568e
FirebaseCoreExtension: edbd30474b5ccf04e5f001470bdf6ea616af2435
FirebaseCoreInternal: 9afa45b1159304c963da48addb78275ef701c6b4
FirebaseCore: 055f4ab117d5964158c833f3d5e7ec6d91648d4a
FirebaseCoreExtension: 639afb3de6abd611952be78a794c54a47fa0f361
FirebaseCoreInternal: dedc28e569a4be85f38f3d6af1070a2e12018d55
FirebaseEmailAuthUI: b6c80ac6ae42bacf2fece92762fa79bc4ee736ed
FirebaseFirestore: 1e5fafdac2b2ef1ffc24034460b7b4821a15be96
FirebaseFirestoreInternal: df9ab608a59a4e8eefd0796ed7652f3c1a88473a
FirebaseSharedSwift: e17c654ef1f1a616b0b33054e663ad1035c8fd40
FirebaseFirestore: 64f13d770a1e5a77e667efc5ed5576461f4d7827
FirebaseFirestoreInternal: 1ba4a8841496a9af788622a97fc45eb7b3b92c5f
FirebaseSharedSwift: 59266c22ccfcef604d725c034c568fa666ea9bda

Choose a reason for hiding this comment

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

medium

The checksums for Firebase dependencies have been updated. Verify that these checksums are correct and correspond to the expected versions to ensure the integrity of the dependencies.

@dpebot dpebot force-pushed the dpebot-repositorygardener branch from 4b937be to 17364ef Compare July 18, 2025 01:43
@paulb777 paulb777 merged commit 212a9f2 into main Jul 18, 2025
6 checks passed
@paulb777 paulb777 deleted the dpebot-repositorygardener branch July 18, 2025 16:36
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.

2 participants