# How can I ensure my plugin is compatible with both Kotlin versions k1 and k2 across different IntelliJ IDEA releases from 2022.3 to 2024.3?
**URL:** https://platform.jetbrains.com/t/how-can-i-ensure-my-plugin-is-compatible-with-both-kotlin-versions-k1-and-k2-across-different-intellij-idea-releases-from-2022-3-to-2024-3/477
**Category:** Plugin Verifier
**Created:** [February 13, 2025, 8:08am UTC](https://platform.jetbrains.com/t/how-can-i-ensure-my-plugin-is-compatible-with-both-kotlin-versions-k1-and-k2-across-different-intellij-idea-releases-from-2022-3-to-2024-3/477 "2025-02-13T08:08:58Z")
**Posts on this page:** 5
**Page:** 1
### Author:  [@the.fallenangel.965](https://platform.jetbrains.com/u/the.fallenangel.965)
#### Post date: [February 13, 2025, 8:08am UTC](https://platform.jetbrains.com/t/how-can-i-ensure-my-plugin-is-compatible-with-both-kotlin-versions-k1-and-k2-across-different-intellij-idea-releases-from-2022-3-to-2024-3/477/1 "2025-02-13T08:08:58Z")
I was checking the compatibility results for my plugin and encountered a warning about compatibility with k2, as shown in the following image:
It indicates that I need to declare a compatibility mode, but… my plugin’s support range is “223.7571.182 — 243.x”, and I plan to maintain this interval, for example, “224.7571.182 — 244.x”, “230.7571.182 — 250.x”.
This presents a problem. My plugin’s development version is 223.7571.182, which didn’t have this extension, so I can’t declare compatibility or migrate the dependency on `BindingContext` to `analyze`.
I can’t continue using only k1 without supporting k2 until the release of 2026.2 (at which point I will drop support for 2024.1), nor can I abandon support for k1 and only support IDEA versions starting from 2024.2. What should I do?
---
### Author:  [@yann.cebron](https://platform.jetbrains.com/u/yann.cebron)
#### Post date: [February 13, 2025, 8:23am UTC](https://platform.jetbrains.com/t/how-can-i-ensure-my-plugin-is-compatible-with-both-kotlin-versions-k1-and-k2-across-different-intellij-idea-releases-from-2022-3-to-2024-3/477/3 "2025-02-13T08:23:16Z")
You’ll need to build and release separate versions of your plugin for each range of supported IDEs if you need to support any features only present in newer version.
> **[Build Number Ranges | IntelliJ Platform Plugin SDK](https://plugins.jetbrains.com/docs/intellij/build-number-ranges.html#multipleIDEVersions)**
---
### Author:  [@the.fallenangel.965](https://platform.jetbrains.com/u/the.fallenangel.965)
#### Post date: [February 13, 2025, 8:28am UTC](https://platform.jetbrains.com/t/how-can-i-ensure-my-plugin-is-compatible-with-both-kotlin-versions-k1-and-k2-across-different-intellij-idea-releases-from-2022-3-to-2024-3/477/5 "2025-02-13T08:28:43Z")
So you’re suggesting that I should release an entirely new plugin to provide support for k1 from 2022.3 to 2024.2, and adjust the support range of the current plugin to start from 2024.2 onwards?
---
### Author:  [@yann.cebron](https://platform.jetbrains.com/u/yann.cebron)
#### Post date: [February 13, 2025, 8:31am UTC](https://platform.jetbrains.com/t/how-can-i-ensure-my-plugin-is-compatible-with-both-kotlin-versions-k1-and-k2-across-different-intellij-idea-releases-from-2022-3-to-2024-3/477/6 "2025-02-13T08:31:14Z")
Technically not a “new” plugin, but a dedicated release.
e.g. you can use release numbers like `1.0-223` for plugin supporting 2022.3+ and another release `1.0-242` for plugin built against 2024.2+.
---
### Author:  [@the.fallenangel.965](https://platform.jetbrains.com/u/the.fallenangel.965)
#### Post date: [February 13, 2025, 8:37am UTC](https://platform.jetbrains.com/t/how-can-i-ensure-my-plugin-is-compatible-with-both-kotlin-versions-k1-and-k2-across-different-intellij-idea-releases-from-2022-3-to-2024-3/477/7 "2025-02-13T08:37:20Z")
Hmm, I’ve noticed the link in your previous reply now… I initially thought that wasn’t part of your response, as I’ve never seen a hyperlink that looks like that before…
I’m looking into that link now, thanks for your suggestion!