fix(ci): bump Kotlin Gradle plugin to 2.3.0 - #18600
Conversation
firebase-auth 24.2.0 ships Kotlin 2.3.0 metadata that example apps still compiling with 1.9/2.1 cannot consume.
Using Gemini Code AssistThe full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips. Invoking Gemini You can request assistance from Gemini at any point by creating a comment using either
Customization To customize the Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a Limitations & Feedback Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counterproductive. You can react with 馃憤 and 馃憥 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for GitHub and other Google products, sign up here. |
Wiz Scan Summary
To detect these findings earlier in the dev lifecycle, try the Wiz Code extension for VS Code, JetBrains, or Visual Studio. |
Kotlin 2.3.0 rejects android.kotlinOptions.jvmTarget as a String. Use kotlin.compilerOptions instead.
Description
firebase-auth24.2.0 (Firebase Android BoM 34.18.0) was compiled with Kotlin 2.3.0 metadata. Example apps and the aggregate tests project still pin the Kotlin Gradle plugin to 1.9.x / 2.1.x / 2.2.x, so Android e2e builds fail when compiling:firebase_auth:compileDebugKotlin:Bump the Kotlin Gradle plugin to 2.3.0 across example apps, the Firestore pipeline example,
tests/android, and the remaining pluginext.kotlin_versionpins. Thefirebase_authexample already uses 2.3.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.yamland changelogs is not required.///).melos run analyze) does not report any problems on my PR.Breaking Change
Does your PR require plugin users to manually update their apps to accommodate your change?