fix: Revert "chore: upgrade database-compat" - #2247
Merged
lahirumaramba merged 1 commit intoJul 13, 2023
Merged
Conversation
Copy link
Copy Markdown
Member
Sorry, something went wrong.
This reverts commit 844600b.
hsubox76
approved these changes
Jul 13, 2023
maneesht
approved these changes
Jul 13, 2023
This was referenced Jul 13, 2024
This was referenced Jul 25, 2024
This was referenced Aug 20, 2024
This was referenced Aug 23, 2024
This was referenced Aug 30, 2024
This was referenced Sep 4, 2024
This was referenced Sep 13, 2024
This was referenced Sep 24, 2024
This was referenced Oct 27, 2024
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.
Reverts #2244
This change was accidentally included in firebase-admin 11.10.0. Reverting to prepare an emergency patch release. database-compat upgrade should be included in the next major version of firebase-admin
RELEASE NOTES: Fixed an issue which caused the incompatibility in database types in version 11.10.0