From b834bf59a8a311c3e8e584b237996bfe7785a22e Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Yann=20C=C3=A9bron?= Date: Mon, 5 Sep 2022 17:16:20 +0200 Subject: [PATCH] build_number_ranges.md: small wording issue --- topics/basics/getting_started/build_number_ranges.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/topics/basics/getting_started/build_number_ranges.md b/topics/basics/getting_started/build_number_ranges.md index 356d54b62..85c046771 100644 --- a/topics/basics/getting_started/build_number_ranges.md +++ b/topics/basics/getting_started/build_number_ranges.md @@ -7,7 +7,7 @@ Setting the actual values in plugin.xml is managed by [`patchPlugin Please note the following regarding values: - Values must represent the actual build numbers, any made-up numbers must not be used (e.g., using `999.*` for `until-build`). -- An empty value for `until-build` means it will include _all_ future builds (including unreleased IDE versions, which might impact compatibility later). +- Not specifying `until-build` means it will include _all_ future builds (including unreleased IDE versions, which might impact compatibility later). - Dot star suffix (`.* `) can be used in `until-build` to support all releases for the specific branch (i.e., `222.*` for all 2022.2.x releases). > Compatibility with the specified version range (and compatible products) must always be verified using [](verifying_plugin_compatibility.md#plugin-verifier) to ensure binary compatibility.