Skip to content
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

Update dependency com.google.firebase:firebase-bom to v32.2.2 #112

Merged
merged 1 commit into from
Aug 10, 2023

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Aug 3, 2023

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
com.google.firebase:firebase-bom 32.2.0 -> 32.2.2 age adoption passing confidence

Configuration

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

🚦 Automerge: Enabled.

Rebasing: Whenever PR becomes conflicted, 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 has been generated by Mend Renovate. View repository job log here.

@renovate renovate bot enabled auto-merge (squash) August 3, 2023 17:33
@renovate renovate bot changed the title Update dependency com.google.firebase:firebase-bom to v32.2.1 Update dependency com.google.firebase:firebase-bom to v32.2.2 Aug 3, 2023
@renovate renovate bot force-pushed the renovate/com.google.firebase branch 2 times, most recently from f2773b2 to 0982d9c Compare August 10, 2023 21:26
@renovate renovate bot force-pushed the renovate/com.google.firebase branch from 0982d9c to d09188a Compare August 10, 2023 21:32
@renovate renovate bot merged commit 489f07e into main Aug 10, 2023
1 check passed
@renovate renovate bot deleted the renovate/com.google.firebase branch August 10, 2023 21:34
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.

0 participants