From 0ea7b2da8972b585dfb19daaf32550ffbc62a1d7 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Yann=20C=C3=A9bron?= Date: Wed, 1 Mar 2023 16:41:06 +0100 Subject: [PATCH] build_number_ranges.md: clarify compatibility --- topics/basics/getting_started/build_number_ranges.md | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/topics/basics/getting_started/build_number_ranges.md b/topics/basics/getting_started/build_number_ranges.md index 3e82567ec..8bc507281 100644 --- a/topics/basics/getting_started/build_number_ranges.md +++ b/topics/basics/getting_started/build_number_ranges.md @@ -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). > -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.