Skip to content

chore(release): BoM 5.0.0 — 2026-10-15 - #18803

Merged
SelaseKay merged 4 commits into
mainfrom
release/2026-10-15
Oct 15, 2026
Merged

SelaseKay merged 4 commits into
mainfrom
release/2026-10-15

Conversation

@SelaseKay

Copy link
Copy Markdown
Contributor

Description

Cuts FlutterFire BoM 5.0.0 (2026-10-15) from main: Melos versioning, changelogs, VERSIONS.md / scripts/versions.json, and generated web/SPM version files.

Native SDK pins in this BoM:

  • Android 35.0.0
  • Web 13.0.0
  • Windows 14.0.0
  • Apple CocoaPods 12.19.0 / SPM 13.0.0 (dual-pin)

Includes majors from the already-merged breaking work (SDK bumps, App Check activate provider removals, Data Connect auth/appCheck removals, ML Model Downloader package removal, Firebase AI live-session change). Release notes document the Apple dual-pin, ML shutdown (15 June 2027) with the Cloud Storage migration link, and App Check / Data Connect migrations.

After this PR merges: melos publish --no-dry-run, git push --tags, mark firebase_ml_model_downloader (+ platform interface) discontinued on pub.dev, ping @kevinthecheung.

Related Issues

None. Release cut for the breaking change already on main.

Checklist

  • I read the Contributor Guide and followed the process outlined there for submitting PRs.
  • My PR includes unit or integration tests for all changed/updated/fixed behaviors (See Contributor Guide).
  • All existing and new tests are passing.
  • I updated/added relevant documentation (doc comments with ///).
  • The analyzer (melos run analyze) does not report any problems on my PR.
  • I read and followed the Flutter Style Guide.
  • I signed the CLA.
  • I am willing to follow-up on review comments in a timely manner.

Breaking Change

Does your PR require plugin users to manually update their apps to accommodate your change?

  • Yes, this is a breaking change.
  • No, this is not a breaking change.

See package changelogs and the BoM 5.0.0 section in CHANGELOG.md for migrations (App Check providers, Data Connect args, ML removal, native SDK majors).

Test plan

  • CI green on release/2026-10-15
  • Spot-check VERSIONS.md dual Apple pins and absence of firebase_ml_model_downloader from BoM 5.0.0
  • After merge: dry-run already listed 42 packages; run melos publish --no-dry-run then push tags

 - cloud_firestore@7.0.0
 - cloud_firestore_platform_interface@8.0.8
 - cloud_functions@7.0.0
 - cloud_functions_platform_interface@6.1.0
 - firebase_ai@5.0.0
 - firebase_analytics@13.0.0
 - firebase_app_check@0.5.0
 - firebase_app_check_platform_interface@0.5.0+2
 - firebase_app_check_web@0.3.0+2
 - firebase_app_installations@0.5.0
 - firebase_auth@7.0.0
 - firebase_auth_web@6.3.1
 - firebase_core@5.0.0
 - firebase_core_web@4.0.0
 - firebase_crashlytics@6.0.0
 - firebase_data_connect@0.4.0
 - firebase_database@13.0.0
 - firebase_in_app_messaging@0.10.0
 - firebase_in_app_messaging_platform_interface@0.2.6+29
 - firebase_messaging@17.0.0
 - firebase_messaging_platform_interface@4.11.0
 - firebase_messaging_web@4.3.0
 - firebase_performance@0.12.0
 - firebase_remote_config@7.0.0
 - firebase_storage@14.0.0
 - _flutterfire_internals@1.3.78
 - cloud_firestore_web@5.7.4
 - cloud_functions_web@5.1.14
 - firebase_analytics_platform_interface@6.0.8
 - firebase_analytics_web@0.6.2+14
 - firebase_app_installations_platform_interface@0.1.6
 - firebase_app_installations_web@0.1.8+14
 - firebase_auth_platform_interface@9.1.1
 - firebase_crashlytics_platform_interface@3.9.1
 - firebase_database_platform_interface@0.4.1+8
 - firebase_database_web@0.2.8+15
 - firebase_performance_platform_interface@0.2.1+8
 - firebase_performance_web@0.1.9+14
 - firebase_remote_config_platform_interface@3.0.8
 - firebase_remote_config_web@1.10.15
 - firebase_storage_platform_interface@6.0.8
 - firebase_storage_web@3.11.14
@gemini-code-assist

Copy link
Copy Markdown
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 by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

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 pull request comments and review comments.
Help /gemini help Displays a list of available commands.

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 .gemini/ folder in the base of the repository. Detailed instructions can be found here.

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.

@SelaseKay
SelaseKay merged commit 39069d5 into main Oct 15, 2026
109 checks passed
@SelaseKay
SelaseKay deleted the release/2026-10-15 branch October 15, 2026 12:42
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.

3 participants