diff --git a/topics/basics/getting_started/build_number_ranges.md b/topics/basics/getting_started/build_number_ranges.md index 2210b845b..f9a6f4edf 100644 --- a/topics/basics/getting_started/build_number_ranges.md +++ b/topics/basics/getting_started/build_number_ranges.md @@ -9,8 +9,8 @@ Setting the actual values in [plugin.xml](plugin_configuration_file.md)

Compatibility with the specified version range (and compatible products) must always be verified using [](verifying_plugin_compatibility.md#plugin-verifier) to ensure binary compatibility. @@ -40,7 +40,7 @@ Plugins may specify compatibility versions more precisely (e.g., requiring a spe 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: - + ```xml @@ -54,6 +54,8 @@ Usually you should omit the product ID and use only the branch number and build > 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](https://www.jetbrains.com/idea/download/previous.html). +> For upcoming versions, see [Early Access Program](https://eap.jetbrains.com). +> > See also [What versions of IntelliJ-based IDEs are supported?](https://intellij-support.jetbrains.com/hc/en-us/articles/360019574859-What-versions-of-IntelliJ-based-IDEs-are-supported-) for JetBrains IDE support policy. > {style="note"}