chore: renumber BoM 5.0.0 to 4.19.0 - #18609
Conversation
The BoM went major only because generate_bom.dart bumps major whenever any tracked package does, and firebase_ai 3.15.0 -> 4.0.0 was in the set. Renumber the entry to 4.19.0; the 17 package pins are unchanged and match what was published to pub.dev on 2026-08-24.
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 the 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 counterproductive. 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. |
BoM 5.0.0 → 4.19.0
Renumbers the 2026-08-24 BoM entry. The 17 package pins are unchanged and match what was published to pub.dev.
generate_bom.dartbumps the BoM major whenever any tracked package goes major, sofirebase_ai3.15.0 → 4.0.0 alone took the BoM 4.18.0 → 5.0.0. The remaining 16 packages were 10 minor and 6 patch.Changes
scripts/versions.json5.0.0→4.19.0VERSIONS.mdflutterfire installcommandCHANGELOG.mdVERSIONS.mdanchorTags
BoM-v5.0.0is superseded and needs deleting;BoM-v4.19.0replaces it. The 45 package tags are unaffected.Note
firebase_ai4.0.0 remains in this BoM, so 4.19.0 does contain a breaking package change.