Build Number Ranges
Use this reference of build number ranges to specify the correct since-build
and until-build
values in your plugin descriptor.
Setting the actual values in plugin.xml is managed by the patchPluginXml
Gradle task (Reference: 2.x, 1.x). See Patching the Plugin Configuration File for further details.
Build Number Validity
Please note the following regarding values:
Values must represent the actual build numbers. Any made-up numbers must not be used, and such plugins will be rejected on JetBrains Marketplace. For example,
233.*
is invalid forsince-build
; any of999.*
,234.*
(maximum is233.*
) and223.9999
are invalid foruntil-build
.Not specifying
until-build
means it will include all future builds. This includes future, yet unreleased versions and possibly new IDEs, which might impact compatibility later.To support all releases for a specific branch, use dot-star suffix (
.*
) inuntil-build
. For example,232.*
for all 2023.2.x releases.
Build Number Format
To denote a release, a multipart build number is used. It consists of the following parts:
Product ID (
IC
for IDEA Community,IU
for IDEA Ultimate,RM
for RubyMine,PY
for PyCharm,PS
for PhpStorm, etc.)Branch number (
223
)Build number in the branch (
9559
)
Branch numbers are based on the YYYY.R
IDE release version numbers. The branch number takes the last two digits of the year and the R
release number. For example, 231
for 2023.1, 232
for 2023.2, and 233
for 2023.3.
The build number may have multiple components: IU-162.94.11
, IU-162.94.11.256.42
. This gives more flexibility for third-party plugins and IDE developers. Plugins may specify compatibility versions more precisely (for example, requiring a specific bugfix release); IDE vendors may have build numbers based on a specific IntelliJ Platform version and specify an additional internal version (for example, 256.42
in XX-162.94.11.256.42
) to allow plugin developers for their IDE to specify compatibility.
Multipart build numbers can also be used in the since-build
and until-build
attributes of idea-version
. Usually you should omit the product ID and use only the branch number and build number, for example:
Targeting Multiple IDE Versions
When supporting multiple major versions, it is strongly recommended to build against the lowest supported version to guarantee backwards-compatibility. In the case of supporting a range of platform versions with different underlying Java level (see below), it is required.
Verifying Plugin Compatibility discusses tooling support to ensure compatibility with the chosen version range and IDEs.
Consult Incompatible API Changes and Notable API Changes for an overview of known breaking and relevant changes across IDE versions.
In some cases, keeping a dedicated branch and corresponding plugin release for each major IDE version might be required due to incompatibilities that cannot be solved in other ways. The IDE will automatically install only the corresponding compatible build.
Platform Versions
Note that there is no YY0
. In the YYYY.R
versioning scheme, the R
part starts at 1.
Branch number | IntelliJ Platform version |
---|---|
2024.2 NOTE Java 21 is now required | |
2024.1 | |
2023.3 | |
2023.2 | |
2023.1 |