hxuanyu/intellij-sdk-code-samples
1
0
Fork 0
mirror of https://github.com/JetBrains/intellij-sdk-code-samples.git synced 2025-07-30 18:27:49 +08:00
Code Issues Packages Projects Releases Wiki Activity

build_number_ranges.md: clarify Build Number Validity

Browse Source
This commit is contained in:
Yann Cébron 2024-02-20 14:55:41 +01:00
parent c793e42eb2
commit fa20d76823
1 changed files with 5 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

7
topics/basics/getting_started/build_number_ranges.md
View File

@ -12,9 +12,12 @@ Setting the actual values in <path>[plugin.xml](plugin_configuration_file.md)</p
Please note the following regarding values:
- Values must represent the [actual build numbers](#build-number-format). Any made-up numbers must not be used and such plugins will be rejected on JetBrains Marketplace (for example, `999.*`, `234.*`, or `223.9999` are invalid for `until-build`).
- Values must represent the [actual build numbers](#build-number-format).
Any made-up numbers must not be used and such plugins will be rejected on JetBrains Marketplace.
For example, `233.*` is invalid for `since-build`; any of `999.*`, `234.*` (maximum is `233.*`) and `223.9999` are invalid for `until-build`.
- Not specifying `until-build` means it will include _all_ future builds. This includes future, yet unreleased versions and possibly new IDEs, which might impact compatibility later.
- Use dot-star suffix (`.* `) in `until-build` to support all releases for the specific branch (for example, `232.*` for all 2023.2.x releases).
- To support all releases for a specific branch, use dot-star suffix (`.* `) in `until-build`.
For example, `232.*` for all 2023.2.x releases.
> Before publishing, the plugin must be checked using [](verifying_plugin_compatibility.md#plugin-verifier) against the specified version range (and specified compatible products) to ensure binary compatibility.
> Any additional reported errors/warnings should also be fixed when possible.