8.0 KiB
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 usually managed by patchPluginXml
Gradle task, see Patching the Plugin Configuration File for details.
Compatibility with the specified version range (and compatible products) must always be verified using to ensure binary compatibility.
Plugins hosted on JetBrains Marketplace are checked automatically. According to Approval Guidelines, incompatible plugin versions will be restricted by JetBrains if necessary.
{type="warning"}
Starting with IntelliJ IDEA 9 beta, a multipart build number is used, such as IU-162.94
.
The number 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 (
162
) - Build number in the branch (
94
)
Since version 2016.2 of the IntelliJ Platform, 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, 162
for 2016.2, 163
for 2016.3, 171
for 2017.1.
In this scheme, IU-162.94
corresponds to the 2016.2 release.
Starting with 2016.2, the build number may also have multiple components: IU-162.94
, 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; IDE vendors may have build numbers based on a specific IntelliJ Platform version and specify additional internal version (e.g. 256.42
in XX-162.94.11.256.42
) to allow plugin developers for their IDE to specify compatibility.
Multi-part 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:
<idea-version since-build="94.539"/>
<idea-version since-build="162.539.11"/>
<!-- any build until 162, not inclusive!-->
<idea-version until-build="162"/>
<!-- any 162-based version, 162.94, 162.94.11, etc.-->
<idea-version since-build="162" until-build="162.*"/>
Specific build numbers and their corresponding release version are available via Previous Releases on the corresponding product's download page, e.g. Previous IntelliJ IDEA Releases. See also What versions of IntelliJ-based IDEs are supported? for JetBrains IDE support policy.
{type="note"}
IntelliJ Platform Based Products of Recent IDE Versions
Which versions should your plugin support? We've collected some insights based on download statistics in Statistics: Product Versions in Use.
{type="tip"}
Please see also corresponding entries in Incompatible API Changes and Notable API Changes.
Branch number | IntelliJ Platform version |
---|---|
222 | 2022.2 NOTE Java 17 is now required |
221 | 2022.1 |
213 | 2021.3 |
212 | 2021.2 |
211 | 2021.1 |
203 | 2020.3 NOTE Java 11 is now required (blog post) |
202 | 2020.2 |
201 | 2020.1 |
193 | 2019.3 |
192 | 2019.2 |
191 | 2019.1 |
183 | 2018.3 |
182 | 2018.2 |
181 | 2018.1 |
173 | 2017.3 |
172 | 2017.2 |
171 | 2017.1 |
163 | 2016.3 |
162 | 2016.2 |
Note that there is no 170
.
In the YYYY.R
versioning scheme, the R
part starts at 1.