[Firebase AI] Switch to SemVer tagged firebase-ios-sdk

[andrewheard]

Updated the Firebase AI quickstart to use the tagged release of firebase-ios-sdk for the SPM dependency (up to next major version) instead of depending on main.

[gemini-code-assist]

Hello @andrewheard, 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!

Summary of Changes

As gemini-code-assist, I've reviewed this pull request. The primary goal of this PR, as indicated by the title and description, is to update the Firebase AI quickstart project to use a stable, version-tagged release of the firebase-ios-sdk Swift Package Manager dependency instead of pointing directly to the main branch. This change promotes stability and predictability in the project's dependencies. Additionally, the PR includes a minor update to the README file to correct the default bundle identifier mentioned in the setup instructions.

Highlights

• Dependency Management: Switched the firebase-ios-sdk Swift Package Manager dependency requirement in the Xcode project file (project.pbxproj) from tracking the main branch to using a Semantic Versioning requirement (upToNextMajorVersion) starting from version 11.13.0. This ensures the project depends on released versions rather than potentially unstable development commits.
• Documentation Update: Corrected the default bundle identifier mentioned in the README.md file to match the actual bundle ID used in the sample project.

Changelog

• firebaseai/FirebaseAIExample.xcodeproj/project.pbxproj
  • Modified the requirement block for the firebase-ios-sdk Swift Package Manager dependency (lines 616-619).
  • Changed the kind from branch to upToNextMajorVersion.
  • Removed the branch = main line.
  • Added minimumVersion = 11.13.0.
• firebaseai/README.md
  • Updated the default bundle ID string on line 30 from com.google.firebase.VertexAISample to com.google.firebase.quickstart.FirebaseAIExample.

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.

---

From 'main' branch, wild and free,
To versioned stability,
A tag now guides the way,
For Firebase AI today,
Code builds reliably.

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 is a great pull request that significantly improves the project's dependency management and documentation accuracy. Switching the firebase-ios-sdk dependency from tracking the main branch to a semantic versioned release (upToNextMajorVersion) is an excellent move for stability and predictability. The update to the bundle ID in the README also ensures clarity for developers setting up the sample. Well done on these improvements!

Summary of Findings

• Enhanced Dependency Stability: The modification in FirebaseAIExample.xcodeproj/project.pbxproj to use upToNextMajorVersion with minimumVersion = 11.13.0 for the firebase-ios-sdk dependency is a best practice. This change ensures that the project relies on stable, tagged releases rather than the potentially volatile main branch, leading to more reliable and reproducible builds.
• Improved Documentation Accuracy: The update in firebaseai/README.md correcting the default bundle ID to com.google.firebase.quickstart.FirebaseAIExample aligns the documentation with the actual project configuration (as seen in PRODUCT_BUNDLE_IDENTIFIER in the project settings). This is crucial for a smooth setup experience for users of this quickstart guide.

Merge Readiness

The changes in this pull request are clear, beneficial, and directly address the stated objectives. By improving dependency stability and documentation accuracy, this PR enhances the overall quality of the quickstart example. I believe these changes are ready for merging. As always, please ensure any other necessary reviews or CI checks are completed before finalizing the merge.