chore(deps): bump the firebase group with 2 updates - #868
Open
dependabot[bot] wants to merge 1 commit into
Open
Conversation
Bumps the firebase group with 2 updates: [firebase_core](https://github.com/firebase/flutterfire/tree/main/packages/firebase_core) and [firebase_messaging](https://github.com/firebase/flutterfire/tree/main/packages/firebase_messaging). Updates `firebase_core` from 4.13.0 to 4.14.0 - [Release notes](https://github.com/firebase/flutterfire/releases) - [Commits](https://github.com/firebase/flutterfire/commits/firebase_core-v4.14.0/packages/firebase_core) Updates `firebase_messaging` from 16.5.0 to 16.6.0 - [Release notes](https://github.com/firebase/flutterfire/releases) - [Commits](https://github.com/firebase/flutterfire/commits/firebase_messaging-v16.6.0/packages/firebase_messaging) --- updated-dependencies: - dependency-name: firebase_core dependency-version: 4.14.0 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: firebase - dependency-name: firebase_messaging dependency-version: 16.6.0 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: firebase ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
Bot
added
dart
dependabot
Bot
added
dependencies
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.
Bumps the firebase group with 2 updates: firebase_core and firebase_messaging.
Updates
firebase_corefrom 4.13.0 to 4.14.0Commits
b757b4achore(release): publish packages9bc9d9cfeat(core): bump Firebase Android SDK to 34.18.0 (#18597)07febc3feat: bump Firebase iOS SDK to 12.18.0 (#18596)f29565bfeat(core): bump Firebase JS SDK to 12.18.0 (#18598)9a35775feat(core): bump Firebase C++ SDK to 13.11.0 (#18599)4c3865efix(ci): bump Kotlin Gradle plugin to 2.3.0 (#18600)a54439ffix(core, crashlytics): dropflutter_testfrom published dependencies (#18575)7a0f585refactor(core,android): migrate native implementation to Kotlin (#18570)3b9a655refactor(core,apple): migrate iOS/macOS plugin implementation to Swift (#18569)87ace84fix(ci): align Android toolchain and analyzer with Flutter 3.47 (#18566)Updates
firebase_messagingfrom 16.5.0 to 16.6.0Commits
b757b4achore(release): publish packages07febc3feat: bump Firebase iOS SDK to 12.18.0 (#18596)4c3865efix(ci): bump Kotlin Gradle plugin to 2.3.0 (#18600)69d16e4feat(messaging,ios): migrate example iOS runner from ObjC to Swift (#18578)1c89b68feat(messaging,android): improve how messaging is determining permission on A...87ace84fix(ci): align Android toolchain and analyzer with Flutter 3.47 (#18566)ef1cac4fix(messaging,android): fixing an issue with analytics being triggered twice ...cfbe35ftest: complete per-package e2e migration — all 13 products, secrets-injected ...1e6da07chore: add FlutterFramework dependency to plugins' Package.swift files (#18293)584acc9fix(messaging,macos): unwrap UNNotificationResponse launch payload (#18527)Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore <dependency name> major versionwill close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)@dependabot ignore <dependency name> minor versionwill close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)@dependabot ignore <dependency name>will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)@dependabot unignore <dependency name>will remove all of the ignore conditions of the specified dependency@dependabot unignore <dependency name> <ignore condition>will remove the ignore condition of the specified dependency and ignore conditions