Skip to content

[Infra] Update versions for Release 11.14.0 #14875

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 2 commits into from
May 21, 2025
Merged

[Infra] Update versions for Release 11.14.0 #14875

merged 2 commits into from
May 21, 2025

Conversation

ncooke3
Copy link
Member

@ncooke3 ncooke3 commented May 20, 2025

#no-changelog

Copy link
Contributor

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.

@andrewheard
Copy link
Contributor

@ncooke3 I'd ignore firebaseai / quickstart for now. I'll need to fix the script to update the dependency now that it's using semver upToNextMajorVersion instead of branch main.

Investigating vertexai / pod-lib-lint since that failure was unexpected to me.

@ncooke3
Copy link
Member Author

ncooke3 commented May 20, 2025

For future us, the vertexai / pod-lib-lint had to do with the release tooling not correctly bumping FirebaseVertexAI's dependency on FirebaseAI. See manual fix in 423cb48

Copy link
Contributor

@andrewheard andrewheard left a comment

Choose a reason for hiding this comment

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

LGTM on vertexai / pod-lib-lint green. It's getting late so waiting for the Zip CI likely isn't practical. I think it'd be ok to merge and move tags, then diagnose the Nightlies tomorrow.

@andrewheard
Copy link
Contributor

andrewheard commented May 20, 2025

For future us, the vertexai / pod-lib-lint had to do with the release tooling not correctly bumping FirebaseVertexAI's dependency on FirebaseAI. See manual fix in 423cb48

Manual fix staged: firebase/SpecsStaging@593a78d

Cancelled and restarted the Zip CI after staging, should fix https://github.com/firebase/firebase-ios-sdk/actions/runs/15149000415/job/42591366220?pr=14875#step:7:149 🤞

@ncooke3 ncooke3 merged commit 4d78573 into main May 21, 2025
516 of 534 checks passed
@ncooke3 ncooke3 deleted the version-11.14 branch May 21, 2025 00:07
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment