Repository navigation
chore(release): BoM 5.2.0 — 2026-11-16 - #18972
Merged
Merged
Conversation
- _flutterfire_internals@1.4.0 - cloud_firestore@7.2.0 - cloud_firestore_platform_interface@8.2.0 - cloud_firestore_web@5.9.0 - cloud_functions@7.1.0 - cloud_functions_platform_interface@6.2.0 - cloud_functions_web@5.2.0 - firebase_ai@5.2.0 - firebase_analytics@13.1.0 - firebase_analytics_platform_interface@6.1.0 - firebase_analytics_web@0.6.4+16 - firebase_app_check@0.5.2 - firebase_app_check_platform_interface@0.5.2+4 - firebase_app_check_web@0.3.2+4 - firebase_app_installations@0.5.2 - firebase_app_installations_platform_interface@0.1.8 - firebase_app_installations_web@0.1.10+16 - firebase_auth@7.1.0 - firebase_auth_platform_interface@9.2.0 - firebase_auth_web@6.4.0 - firebase_core@5.2.0 - firebase_core_platform_interface@8.2.0 - firebase_core_web@4.2.0 - firebase_crashlytics@6.1.0 - firebase_crashlytics_platform_interface@3.10.0 - firebase_data_connect@0.4.2 - firebase_database@13.1.0 - firebase_database_platform_interface@0.4.3+10 - firebase_database_web@0.2.10+17 - firebase_in_app_messaging@0.10.2 - firebase_in_app_messaging_platform_interface@0.2.8+31 - firebase_messaging@17.1.0 - firebase_messaging_platform_interface@4.12.0 - firebase_messaging_web@4.4.0 - firebase_performance@0.12.2 - firebase_performance_platform_interface@0.2.3+10 - firebase_performance_web@0.1.11+16 - firebase_remote_config@7.1.0 - firebase_remote_config_platform_interface@3.1.0 - firebase_remote_config_web@1.11.0 - firebase_storage@14.1.0 - firebase_storage_platform_interface@6.1.0 - firebase_storage_web@3.12.0
Lyokone
approved these changes
Nov 16, 2026
Contributor
There was a problem hiding this comment.
Code Review
This pull request updates the FlutterFire plugins to Flutter BoM version 5.2.0. It bumps the versions of various Firebase packages (including cloud_firestore, firebase_auth, firebase_core, and others) across their pubspec.yaml, changelogs, and platform-specific configuration files, and documents these updates in VERSIONS.md and scripts/versions.json. I have no feedback to provide as there are no review comments or issues identified in the changes.
demolaf
approved these changes
Nov 16, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
Cuts FlutterFire BoM 5.2.0 (2026-11-16) from
main.melos versionbumped 43 packages with minor changes since BoM 5.1.0, andmelos bomwroteVERSIONS.md,scripts/versions.json, and the root changelog.melos publish --dry-runvalidated all 43 packages.Native SDK pins in this BoM:
The 5.1.0 package tags and
BoM-v5.1.0were missing locally. Without them, Melos treats the newer 4.x backport tags as the baseline and counts the already-shipped 5.0.0 breaking changes again. Those 5.1.0 tags were created locally onfee5385a4and are not in this push.BoM-v5.2.0points at6c05baf70(chore(release): publish packages). The BoM file updates are in the following commit,05c6866b1. Merge with a merge commit or rebase, not squash, so the prepared tags stay on these commits.After this PR merges:
melos publish --no-dry-run, thengit push --tags(package tags,BoM-v5.2.0, and the missing 5.1.0 tags).Related Issues
None. Release cut for changes already on
main.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?
Test plan
release/2026-11-16VERSIONS.mdBoM 5.2.0 andfirebase_core5.2.0melos publish --no-dry-run, then push tags