build_number_ranges.md: clarify compatibility

This commit is contained in:
Yann Cébron 2023-03-01 16:41:06 +01:00
parent 36acd43fc4
commit 0ea7b2da89

View File

@ -63,7 +63,10 @@ Usually you should omit the product ID and use only the branch number and build
> Which versions should your plugin support? We've collected some insights based on download statistics in [Statistics: Product Versions in Use](https://plugins.jetbrains.com/docs/marketplace/product-versions-in-use-statistics.html). > Which versions should your plugin support? We've collected some insights based on download statistics in [Statistics: Product Versions in Use](https://plugins.jetbrains.com/docs/marketplace/product-versions-in-use-statistics.html).
> >
Please see also corresponding entries in [Incompatible API Changes](api_changes_list.md) and [Notable API Changes](api_notable.md). When supporting multiple major versions, it is strongly recommended to build against the _lowest_ supported version to guarantee backwards-compatibility.
See [](verifying_plugin_compatibility.md) for tooling support to ensure compatibility with chosen version range and IDEs.
Consult [Incompatible API Changes](api_changes_list.md) and [Notable API Changes](api_notable.md) for an overview of known breaking and relevant changes.
<include from="tools_gradle_intellij_plugin.md" element-id="gradle_plugin_223_problem"/> <include from="tools_gradle_intellij_plugin.md" element-id="gradle_plugin_223_problem"/>