feat(firebaseai): deprecate imagen - #18148
Conversation
Using Gemini Code AssistThe 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
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 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. |
paulb777
left a comment
There was a problem hiding this comment.
Ideally the Imagen example can be replaced with a nanobanana one, but that's a lower priority and can happen later
rachelsaunders
left a comment
There was a problem hiding this comment.
Is there a changelog entry that I can check as well?
| @Deprecated( | ||
| 'All Imagen models are deprecated and will shut down as early as June 2026. ' | ||
| 'As a replacement, you can migrate your apps to use Gemini Image models (the ' | ||
| '"Nano Banana" models)(https://firebase.google.com/docs/ai-logic/imagen-models-migration).', |
There was a problem hiding this comment.
hmmm... This doesn't seem to be formatted correctly (this same comment applies throughout).
The link to the docs should be a hyperlink on this text:
migrate your apps to use Gemini Image models (the "Nano Banana" models)
Description
Replace this paragraph with a description of what this PR is doing. If you're modifying existing behavior, describe the existing behavior, how this PR is changing it, and what motivated the change.
Related Issues
Replace this paragraph with a list of issues related to this PR from the issue database. Indicate, which of these issues are resolved or fixed by this PR. Note that you'll have to prefix the issue numbers with flutter/flutter#.
Checklist
Before you create this PR confirm that it meets all requirements listed below by checking the relevant checkboxes (
[x]).This will ensure a smooth and quick review process. Updating the
pubspec.yamland changelogs is not required.///).melos run analyze) does not report any problems on my PR.Breaking Change
Does your PR require plugin users to manually update their apps to accommodate your change?