Skip to content

chore(release): BoM 5.2.0 — 2026-11-16 - #18972

Merged
SelaseKay merged 2 commits into
mainfrom
release/2026-11-16
Nov 16, 2026
Merged

SelaseKay merged 2 commits into
mainfrom
release/2026-11-16

Conversation

@SelaseKay

Copy link
Copy Markdown
Contributor

Description

Cuts FlutterFire BoM 5.2.0 (2026-11-16) from main. melos version bumped 43 packages with minor changes since BoM 5.1.0, and melos bom wrote VERSIONS.md, scripts/versions.json, and the root changelog. melos publish --dry-run validated all 43 packages.

Native SDK pins in this BoM:

  • Android 35.2.0
  • Web 13.3.0
  • Windows 14.1.0
  • Apple CocoaPods 12.19.3 / SPM 13.2.0

The 5.1.0 package tags and BoM-v5.1.0 were 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 on fee5385a4 and are not in this push.

BoM-v5.2.0 points at 6c05baf70 (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, then git 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.yaml and changelogs is not required.

  • 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.

Test plan

  • CI green on release/2026-11-16
  • Spot-check VERSIONS.md BoM 5.2.0 and firebase_core 5.2.0
  • After merge: dry run already passed for 43 packages; run melos publish --no-dry-run, then push tags

 - _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

@gemini-code-assist gemini-code-assist Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

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.

@SelaseKay
SelaseKay merged commit dfc9e73 into main Nov 16, 2026
113 of 115 checks passed
@SelaseKay
SelaseKay deleted the release/2026-11-16 branch November 16, 2026 14:18
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