Skip to content

fix(deps): update dependency firebase_core to ^0.7.0 #96

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: develop
Choose a base branch
from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented May 9, 2021

This PR contains the following updates:

Package Update Type Change Package file References
firebase_core (source) minor dependencies ^0.4.0+6 -> ^0.7.0 pubspec.yaml homepage, source

Release Notes

firebase/flutterfire (firebase_core)

v0.7.0

Compare Source

  • REFACTOR: Migrate non-nullable types (#​4656).

v0.6.0

Compare Source

Note: This release has breaking changes.

  • FEAT: bump firebase-android-sdk to v26.2.0.
  • BREAKING REFACTOR: remove all currently deprecated APIs.
  • BREAKING FEAT: forward port to firebase-ios-sdk v7.3.0.
    • Due to this SDK upgrade, iOS 10 is now the minimum supported version by FlutterFire. Please update your build target version.
  • CHORE: harmonize dependencies and version handling.

v0.5.3

Compare Source

  • FEAT: bump android com.android.tools.build & 'com.google.gms:google-services versions (#​4269).

v0.5.2+1

Compare Source

  • Update a dependency to the latest release.

v0.5.2

  • Update a dependency to the latest release.

v0.5.1

  • FEAT: bump compileSdkVersion to 29 (#​3975).
  • FEAT: update Firebase Android SDK BoM version to 25.12.0 (from 25.3.1).
  • FEAT: update Firebase iOS SDK version to 6.33.0 (from 6.26.0).

v0.5.0+1

Compare Source

  • FIX: remove unused dart:async import (#​3611).

v0.5.0

  • FIX: remove unused dart:async import (#​3611).

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate renovate bot force-pushed the renovate/firebase_core-0.x branch from c59bc13 to 751d299 Compare March 19, 2023 02:03
@renovate renovate bot changed the title fix(deps): update dependency firebase_core to v0.7.0 fix(deps): update dependency firebase_core to ^0.7.0 Mar 19, 2023
@renovate
Copy link
Contributor Author

renovate bot commented Mar 19, 2023

⚠ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

  • any of the package files in this branch needs updating, or
  • the branch becomes conflicted, or
  • you click the rebase/retry checkbox if found above, or
  • you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: pubspec.lock
Command failed: docker run --rm --name=renovate_sidecar --label=renovate_child -v "/mnt/renovate/gh/kodekameratene/Oase":"/mnt/renovate/gh/kodekameratene/Oase" -v "/tmp/renovate-cache":"/tmp/renovate-cache" -v "/tmp/containerbase":"/tmp/containerbase" -e BUILDPACK_CACHE_DIR -e CONTAINERBASE_CACHE_DIR -w "/mnt/renovate/gh/kodekameratene/Oase" docker.io/containerbase/sidecar bash -l -c "install-tool flutter 3.7.7 && flutter pub upgrade firebase_core"
Because cloud_firestore >=0.11.0 <0.13.3 depends on firebase_core ^0.4.0 and oase depends on firebase_core ^0.7.0, cloud_firestore >=0.11.0 <0.13.3 is forbidden.
So, because oase depends on cloud_firestore ^0.12.5+2, version solving failed.
pub finished with exit code 1

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants