-
Notifications
You must be signed in to change notification settings - Fork 616
Merge master into realtime-rc-merge and use Firebase executors. #4473
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
Conversation
This implementation: - Creates the base branch (name is based in user input) - Creates the release branch (name is based in user input) - Creates the release.cfg file in the release branch without adding any SDK (module) to it. It can create the branches based on any existing branch of the repo.
* Update versions
* WIP: `in` expansion. * Add composite filter in-expansion test. * Fix formatting. * Run in-expansion as part of DNF computation and add tests. * Add test with nested IN filters with CSI. * Add tests for other cases.
* refactor(functions): update firebase-iid to 21.1.0 * Update CHANGELOG.md * Update CHANGELOG.md * bump firebase-iid-interop to 17.1.0 * exclude firebase-components from firebase-iid dependency
firebase-database only uses StringUtils#repeat in test code, and it is easy to port repeat method to test file and remove plexus-utils from test dependency. Signed-off-by: utzcoz <[email protected]> Signed-off-by: utzcoz <[email protected]>
* test(functions): fix instrumentation tests * fix java format
Properly reset SharedPreferences test state in between each test.
* Remove redundant package list * Implement fix for link transformations * Set reference path in DackkaPlugin * Removed accidental dackka diff script
* Early return in getDocumentsMatchingTarget * Address Feedback
* Upgrade GRPC tp 1.50.2 * Add changelog for Upgrade GRPC tp 1.50.2 * Add links to changelog
* Add groupId removal transform * Add bug link for dackka exposing the configuration
* Initial version of the build release artifacts workflow. This version of the workflow hardcodes the list of sdks to release to include Firestore only. Also, generated javadoc is not yet equivalent to what's generated by the regular release process.
This will make it easier to identify them and apply restrictions on them.
* Fix code blocks * Fix linting in firebase-database * Fix FirebaseMLDownloader linting
* Integrate `SafetyNetAppCheckProvider` with Firebase Components. * Suppress warning. * Integrate DebugAppCheckProvider with Firebase Components. * Add unit tests for the new registrars. * Integrate `PlayIntegrityAppCheckProvider` with Firebase Components.
…#4440) Migrate firebase-inappmessaging SDK to go/firebase-android-executors.
…4449) * Migrate `firebase-appcheck-safetynet` to go/firebase-android-executors. * Migrate `firebase-appcheck-playintegrity` to go/firebase-android-executors. * Migrate `firebase-appcheck-debug` to go/firebase-android-executors. * Remove unnecessary class field from `SafetyNetAppCheckProvider`. * Update changelogs.
* Migrate core libraries to Gradle Kotlin DSL. * update * Add functions, fix tests * fix docs * fix functions ktx minSdk version. * Apply suggestions from code review Co-authored-by: Rodrigo Lazo <[email protected]> Co-authored-by: Rodrigo Lazo <[email protected]>
…#4442) * Fix overlay patch bug * Feedback * Delete comment
* Add diff javadoc workflow * Minor tweaks * Revert checkout order change * Revert incorrect changes * Modify ChangedModulesTask * Only compare modified SDKs * Change build order * Add fetch depth * Fix typo * Only Firebase SDKs
* Move continuations off main thread for `firebase-appcheck`. * One more continuation in `firebase-appcheck`. * Move continuations off main thread for `firebase-appcheck-debug`. * Rearrange executor order. * Move continuations off main thread for `firebase-appcheck-safetynet`. * Move continuations off main thread for `firebase-appcheck-playintegrity`. * Update changelog. * Fix `SafetyNetAppCheckProviderTest`. * Address review comments.
* update dagger * update * update * update * update registrar * update tests
Size Report 1Affected Products
Test Logs |
Coverage Report 1This report is too large (200,680 characters) to be displayed here in a GitHub comment. Please use the below link to see the full report on Google Cloud Storage.Test Logs |
Startup Time Report 1Note: Layout is sometimes suboptimal due to limited formatting support on GitHub. Please check this report on GCS. Startup time comparison between the CI merge commit (8978980) and the base commit (e40042a) are not available. No macrobenchmark data found for the base commit (e40042a). Analysis for the CI merge commit (8978980) can be found at: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Builds and tests pass locally.