fix(ui_auth): Update email_validator dependency for firebase_ui_auth from 2.1.17 to 3.0.0 #535
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
I updated the email_validator version for firebase_ui_auth from 2.1.17 to 3.0.0
Because firebase_ui_auth >=1.8.0 depends on email_validator ^2.1.17 and firebase_ui_auth <1.8.0 depends on email_validator ^2.0.1, every version of firebase_ui_auth requires email_validator ^2.0.1.
And because arcane >=3.7.3 depends on email_validator ^3.0.0 and serverpod_auth_firebase_flutter >=1.1.0 depends on firebase_ui_auth ^1.2.2, arcane >=3.7.3 is incompatible with serverpod_auth_firebase_flutter >=1.1.0.
Related Issues
Checklist
Before you create this PR confirm that it meets all requirements listed below by checking the relevant checkboxes (
[x]
).This will ensure a smooth and quick review process. Updating the
pubspec.yaml
and changelogs is not required.///
).melos run analyze
) does not report any problems on my PR.melos run test:unit:all
doesn't fail).Breaking Change
Does your PR require plugin users to manually update their apps to accommodate your change?