Repository navigation
chore(release): publish packages (BoM 4.20.1, Firestore iOS security fix) - #18863
Merged
Merged
Conversation
- cloud_firestore@6.10.1 - cloud_functions@6.5.1 - firebase_analytics@12.6.1 - firebase_app_check@0.4.9 - firebase_app_installations@0.4.5 - firebase_auth@6.7.1 - firebase_core@4.15.1 - firebase_crashlytics@5.4.1 - firebase_database@12.6.1 - firebase_in_app_messaging@0.9.5 - firebase_messaging@16.7.1 - firebase_ml_model_downloader@0.4.6 - firebase_performance@0.11.7 - firebase_remote_config@6.7.1 - firebase_storage@13.6.1
Contributor
There was a problem hiding this comment.
Code Review
This pull request introduces a security release (Flutter BoM 4.20.1) that bumps the Firebase iOS SDK to version 12.19.3 across all FlutterFire plugins (including cloud_firestore, firebase_core, firebase_auth, and others) to address a Firestore security vulnerability on iOS and macOS. It updates the corresponding package versions, changelogs, Swift package manifests, and metadata files. I have no feedback to provide as the changes are correct and complete.
russellwheatley
approved these changes
Oct 23, 2026
1 task done
Lyokone
added a commit
that referenced
this pull request
Oct 23, 2026
Forward-port of the 4.x security release (BoM 4.20.1, #18863) so that `flutterfire install 4.20.1` resolves and the release links on main work.
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
Release for the 4.x line: BoM 4.20.1, a security release for Cloud Firestore on iOS/macOS. It ships #18861, which pins the Firebase iOS SDK to
12.19.3for CocoaPods and SPM. That SDK removes compromised eMudhra CA roots from Firestore's embedded gRPC root-certificate bundle (firebase/firebase-ios-sdk#16930).Generated with
melos version+melos bom 4.20.1fromrelease/4.xat ff334ac.Packages (all patch bumps, none of these versions are on pub.dev yet)
Manual edits on top of melos output
firebase_core: ^4.15.1(melos left^4.14.0). Without it, a plugin can resolve againstfirebase_core4.15.0. CocoaPods would then quietly stay on 12.19.0, because podspecs read the SDK version fromfirebase_core. SPM would fail to resolve, because the two packages pinfirebase-ios-sdkto different exact versions.smartDependents: falsewas not used: on this line it bumps 19 platform-interface/web packages to versions already published from the 5.x line.firebase_core4.15.1 and the rootCHANGELOG.md: SPM users must upgrade; the CocoaPods$FirebaseSDKVersion = '12.19.3'workaround (with an app_check/analytics caveat); Windows is covered in a follow-up release.Release notes for maintainers
melos publishcompares local versions with pub.dev's latest (now 5.x), so unscoped it would also try to publish 28 already-published 4.x versions. Usemelos publish --no-dry-runwith a--scope=<package>for each package above. A scoped dry run passes for all 15: 0 warnings, and the only hint is "earlier than the latest published version".BoM-v4.20.1), notgit push --tags.Follow-ups
main'sscripts/versions.jsonandVERSIONS.md:flutterfire installreads versions frommain, and the changelog links point there.invertase/firestore-ios-sdk-frameworks): a12.19.3build is in progress. Once it is tagged, the 4.x Firestore example Podfiles can go back to using it.Breaking Change