add labels to content

labels.list

@@ -9,6 +9,8 @@
   <primary-label id="IntelliJIDEA_Ultimate" short-name="IntelliJ IDEA Ultimate" name="IntelliJ IDEA Ultimate"
                  href="https://plugins.jetbrains.com/docs/intellij/idea-ultimate.html"/>
 
+  <primary-label id="2020.1" short-name="2020.1+" name="2020.1+"/>
+  <primary-label id="2020.2" short-name="2020.2+" name="2020.2+"/>
   <primary-label id="2020.3" short-name="2020.3+" name="2020.3+"/>
   <primary-label id="2021.3" short-name="2021.3+" name="2021.3+"/>
   <primary-label id="2022.1" short-name="2022.1+" name="2022.1+"/>

topics/basics/basic_action_system.md

@@ -197,8 +197,9 @@ There are two main ways to register an action: either by listing it in the [`<ac
 Registering actions in <path>plugin.xml</path> is demonstrated in the following reference examples, which document all elements and attributes used in the [`<actions>`](plugin_configuration_file.md#idea-plugin__actions) section and describe each element's meaning.
 
 #### Setting the `override-text` Element
+<primary-label ref="2020.1"/>
 
-Beginning in 2020.1, an alternate version of an action's menu text can be declared for use depending on where an action appears.
+An alternate version of an action's menu text can be declared for use depending on where an action appears.
 Using the [`<override-text>`](plugin_configuration_file.md#idea-plugin__actions__action__override-text) element, the menu text for an action can be different depending on context: menu location, toolbar, etc.
 This is also available for groups in 2020.3 and later.
 

topics/basics/getting_started/plugin_compatibility.md

@@ -37,8 +37,9 @@ Some modules are available in all products, and some modules are available only
 This section identifies and discusses modules of both types.
 
 ### Declaring Incompatibility with Module
+<primary-label ref="2020.2"/>
 
-Starting in 2020.2, a plugin can declare incompatibility with an arbitrary module by specifying [`<incompatible-with>`](plugin_configuration_file.md#idea-plugin__incompatible-with) containing module ID in its <path>plugin.xml</path>.
+A plugin can declare incompatibility with an arbitrary module by specifying [`<incompatible-with>`](plugin_configuration_file.md#idea-plugin__incompatible-with) containing module ID in its <path>plugin.xml</path>.
 
 ### Modules Available in All Products
 

topics/basics/indexing_and_psi_stubs.md

@@ -75,8 +75,9 @@ Please see [`VirtualFileGist`](%gh-ic%/platform/indexing-api/src/com/intellij/ut
 ## Improving Indexing Performance
 
 ### Performance Metrics
+<primary-label ref="2020.2"/>
 
-Indexing performance metrics in JSON format are generated in [logs directory](https://intellij-support.jetbrains.com/hc/en-us/articles/206544519-Directories-used-by-the-IDE-to-store-settings-caches-plugins-and-logs) (see [sandbox directory](ide_development_instance.md#the-development-instance-sandbox-directory) for development instance) in 2020.2 and later.
+Indexing performance metrics in JSON format are generated in [logs directory](https://intellij-support.jetbrains.com/hc/en-us/articles/206544519-Directories-used-by-the-IDE-to-store-settings-caches-plugins-and-logs) (see [sandbox directory](ide_development_instance.md#the-development-instance-sandbox-directory) for development instance).
 These are additionally available in HTML format starting with 2021.1.
 
 ### Avoid Using AST

topics/basics/plugin_structure/dynamic_plugins.md

@@ -1,10 +1,11 @@
 <!-- Copyright 2000-2024 JetBrains s.r.o. and contributors. Use of this source code is governed by the Apache 2.0 license. -->
 
 # Dynamic Plugins
+<primary-label ref="2020.1"/>
 
-<link-summary>Making a plugin dynamic allows installing, updating, and uninstalling it without IDE restart, as well as hot reloading plugin changes during the development.</link-summary>
+<link-summary>Making a plugin dynamic allows installing, updating, and uninstalling it without an IDE restart, as well as hot reloading plugin changes during the development.</link-summary>
 
-Starting with the **2020.1** release, installing, updating, and uninstalling plugins without restarting the IDE is available in the IntelliJ Platform.
+Installing, updating, and uninstalling plugins without restarting the IDE is available in the IntelliJ Platform.
 
 During plugin development, [Auto-Reload](ide_development_instance.md#enabling-auto-reload) also allows code changes to take effect immediately in the sandbox IDE instance.
 To test whether dynamic installation works correctly, verify installing [local build distribution](publishing_plugin.md#building-distribution) succeeds (see [Troubleshooting](#troubleshooting)).

topics/basics/plugin_structure/plugin_configuration_file.md

@@ -396,7 +396,7 @@ Examples
 
 ### `incompatible-with`
 {#idea-plugin__incompatible-with}
-_Supported since 2020.2_
+<primary-label ref="2020.2"/>
 
 Declares incompatibility with a provided module.
 

topics/basics/plugin_structure/plugin_extension_points.md

@@ -168,11 +168,12 @@ To report use of deprecated API, use `PluginException.reportDeprecatedUsage()` m
 - [`InspectionProfileEntry.getDisplayName()`](%gh-ic%/platform/analysis-api/src/com/intellij/codeInspection/InspectionProfileEntry.java)
 
 ## Dynamic Extension Points
+<primary-label ref="2020.1"/>
 
-To support [Dynamic Plugins](dynamic_plugins.md) (2020.1 and later), an extension point must adhere to specific usage rules:
+To support [Dynamic Plugins](dynamic_plugins.md), an extension point must adhere to specific usage rules:
 
 - extensions are enumerated on every use and extensions instances are not stored anywhere
-- alternatively, an [`ExtensionPointListener`](%gh-ic%/platform/extensions/src/com/intellij/openapi/extensions/ExtensionPointListener.kt) can perform necessary updates of data structures (register via `ExtensionPointName.addExtensionPointListener()`)
+- alternatively, an [`ExtensionPointListener`](%gh-ic%/platform/extensions/src/com/intellij/openapi/extensions/ExtensionPointListener.kt) can perform any necessary updates of data structures (register via `ExtensionPointName.addExtensionPointListener()`)
 
 Extension points matching these conditions can then be marked as _dynamic_ by adding `dynamic="true"` in their declaration:
 
@@ -185,5 +186,4 @@ Extension points matching these conditions can then be marked as _dynamic_ by ad
 </extensionPoints>
 ```
 
-> All non-dynamic extension points are highlighted via <control>Plugin DevKit | Plugin descriptor | Plugin.xml dynamic plugin verification</control> inspection available in IntelliJ IDEA 2020.1 or later.
+All non-dynamic extension points are highlighted via <control>Plugin DevKit | Plugin descriptor | Plugin.xml dynamic plugin verification</control> inspection.
-> Previous versions also highlight the `dynamic` attribute as "experimental".

topics/reference_guide/frameworks_and_external_apis/external_system_integration.md

@@ -146,8 +146,9 @@ Then register the instance with `ExternalSystemProjectTracker` to start tracking
 {style="note"}
 
 ### Icon for Reload Notification
+<primary-label ref="2020.1"/>
 
-From 2020.1, the icon for reload notification can be specified per external system.
+The icon for reload notification can be specified per external system.
 Implement [`ExternalSystemIconProvider`](%gh-ic%/platform/external-system-api/src/com/intellij/openapi/externalSystem/ui/ExternalSystemIconProvider.kt) and register via [com.intellij.externalIconProvider](https://jb.gg/ipe?extensions=com.intellij.externalIconProvider) extension point in <path>[plugin.xml](plugin_configuration_file.md)</path>.
 Alternatively, set `reloadIcon` field external system implements `ExternalSystemIconProvider` directly.
 

topics/reference_guide/jcef.md

@@ -1,6 +1,7 @@
 <!-- Copyright 2000-2024 JetBrains s.r.o. and contributors. Use of this source code is governed by the Apache 2.0 license. -->
 
 #  Embedded Browser (JCEF)
+<primary-label ref="2020.2"/>
 
 <link-summary>Embedding Chromium-based browser in IDE.</link-summary>
 

topics/tutorials/action_system/working_with_custom_actions.md

@@ -136,8 +136,9 @@ The full declaration is:
 ```
 
 #### Using `override-text` for an Action
+<primary-label ref="2020.1"/>
 
-By using the `override-text` element introduced in 2020.1 of the IntelliJ Platform, the action text can be different depending on the context of where the action appears: menu, toolbar, etc.
+By using the `override-text` element, the action text can be different depending on the context of where the action appears: menu, toolbar, etc.
 The example above uses this element to ensure the shorter text "Popup Dialog Action" is shown anywhere the action appears in the main menu structure.
 Otherwise, the default, more explanatory text "Action Basics Plugin: Popup Dialog Action" is shown.
 For more information, see [](basic_action_system.md#setting-the-override-text-element).