Skip to content

fix(ci): bump Kotlin Gradle plugin to 2.3.0 - #18600

Merged
Lyokone merged 2 commits into
mainfrom
fix/kotlin-2.3.0-auth-metadata
Aug 21, 2026
Merged

fix(ci): bump Kotlin Gradle plugin to 2.3.0#18600
Lyokone merged 2 commits into
mainfrom
fix/kotlin-2.3.0-auth-metadata

Conversation

@SelaseKay

Copy link
Copy Markdown
Contributor

Description

firebase-auth 24.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:

Module was compiled with an incompatible version of Kotlin.
The binary version of its metadata is 2.3.0, expected version is 2.1.0.

Bump the Kotlin Gradle plugin to 2.3.0 across example apps, the Firestore pipeline example, tests/android, and the remaining plugin ext.kotlin_version pins. The firebase_auth example 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.yaml and changelogs is not required.

  • I read the Contributor Guide and followed the process outlined there for submitting PRs.
  • My PR includes unit or integration tests for all changed/updated/fixed behaviors (See Contributor Guide).
  • All existing and new tests are passing.
  • I updated/added relevant documentation (doc comments with ///).
  • The analyzer (melos run analyze) does not report any problems on my PR.
  • I read and followed the Flutter Style Guide.
  • I signed the CLA.
  • I am willing to follow-up on review comments in a timely manner.

Breaking Change

Does your PR require plugin users to manually update their apps to accommodate your change?

  • Yes, this is a breaking change.
  • No, this is not a breaking change.

firebase-auth 24.2.0 ships Kotlin 2.3.0 metadata that example apps still compiling with 1.9/2.1 cannot consume.
@gemini-code-assist

Copy link
Copy Markdown
Contributor
Using Gemini Code Assist

The 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 /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature Command Description
Code Review /gemini review Performs a code review for the current pull request in its current state.
Pull Request Summary /gemini summary Provides a summary of the current pull request in its current state.
Comment @gemini-code-assist Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help /gemini help Displays a list of available commands.

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 .gemini/ folder in the base of the repository. Detailed instructions can be found here.

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-9635d3485b

wiz-9635d3485b Bot commented Aug 21, 2026

Copy link
Copy Markdown

Wiz Scan Summary

Scanner Findings
Vulnerability Finding鈥俈ulnerabilities 2 Medium
Data Finding鈥係ensitive Data -
Secret Finding鈥係ecrets -
IaC Misconfiguration鈥侷aC Misconfigurations -
SAST Finding鈥係AST Findings -
Software Management Finding鈥係oftware Management Findings -
Total 2 Medium

View scan details in Wiz

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.
@Lyokone
Lyokone merged commit 4c3865e into main Aug 21, 2026
112 checks passed
@Lyokone
Lyokone deleted the fix/kotlin-2.3.0-auth-metadata branch August 21, 2026 09:50
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.

3 participants