Skip to content

Support Kotlin 2.3.0 #20661

Description

@hfhbd

Description of the issue
Kotlin 2.3.0-Beta1 was released on 2025-10-07: https://github.com/JetBrains/kotlin/releases/tag/v2.3.0-Beta1
Kotlin 2.3.0 was released on 2025-12-16: https://github.com/JetBrains/kotlin/releases/tag/v2.3.0

CodeQL does not support Kotlin 2.3.0 yet, due to changes in the Kotlin compiler plugin api.

Activity

  1. hvitved commented on Oct 20, 2025

    @hvitved
    Contributor

    Hi 👋

    Thank for reporting this; it is already on our radar, but I cannot give you a timeline at this point, I'm afraid.

  2. forketyfork commented on Dec 17, 2025

    @forketyfork

    Looks like the work is being done in #20965, referencing it for transparency.

  3. st235 commented on Jan 6, 2026

    @st235

    Hello, thank you for your constant support,
    I am wondering whether you have a rough estimate when this can be resolved?

  4. david-allison commented on Jan 6, 2026

    @david-allison
    Contributor

    We have been making progress and expect to have a working solution this week. Support for Kotlin 2.3 is expected to be available in CodeQL 2.24.1 (Early February)

  5. 37 remaining items

  6. marcphilipp commented on Feb 18, 2026

    @marcphilipp

    How so? I just ran a check with 2.24.1 and it failed

  7. smowton commented on Feb 18, 2026

    @smowton
    Contributor

    @marcphilipp please file a fresh issue with the particulars, including excerpts from the logs showing what happened?

  8. marcphilipp commented on Feb 18, 2026

    @marcphilipp
  9. hfhbd commented on Mar 16, 2026

    @hfhbd
    Author

    Kotlin 2.3.20 is out: #21484

  10. rupert-jung-mw commented on Mar 25, 2026

    @rupert-jung-mw

    Pipelines failing again:

    Kotlin version 2.3.20 is too recent. CodeQL currently supports versions below 2.3.20

    Please don't repeat this with every single patch version. These are often automatically updated by Dependabot & Co. and should not break CodeQL at all. It should just work with all 2.3.X versions and not break again at 2.3.30.

  11. yonatankarp commented on Mar 30, 2026

    @yonatankarp

    +1 on that, and the issue should probably be reopened as the issue persists

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    questionFurther information is requested

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions