From 1e7a9b38cca20f815100b24d5420d28ad548b196 Mon Sep 17 00:00:00 2001
From: Yuriy Artamonov <yuriy.artamonov@jetbrains.com>
Date: Sat, 30 Aug 2025 13:56:23 +0200
Subject: [PATCH 1/7] Reformat table in README

---
 README.md | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/README.md b/README.md
index 52dce62..8018edb 100644
--- a/README.md
+++ b/README.md
@@ -325,10 +325,10 @@ Within the default project structure, there is a `.run` directory provided conta
 
 ![Run/Debug configurations][file:run-debug-configurations.png]
 
-| Configuration name | Description                                                                                                                                               |
-|--------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------|
-| Run Plugin         | Runs [`:runIde`][gh:intellij-platform-gradle-plugin-runIde] IntelliJ Platform Gradle Plugin task. Use the *Debug* icon for plugin debugging.              |
-| Run Tests          | Runs [`:test`][gradle:lifecycle-tasks] Gradle task.                                                                                                       |
+| Configuration name | Description                                                                                                                                                                         |
+|--------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Run Plugin         | Runs [`:runIde`][gh:intellij-platform-gradle-plugin-runIde] IntelliJ Platform Gradle Plugin task. Use the *Debug* icon for plugin debugging.                                        |
+| Run Tests          | Runs [`:test`][gradle:lifecycle-tasks] Gradle task.                                                                                                                                 |
 | Run Verifications  | Runs [`:verifyPlugin`][gh:intellij-platform-gradle-plugin-verifyPlugin] IntelliJ Platform Gradle Plugin task to check the plugin compatibility against the specified IntelliJ IDEs. |
 
 > [!NOTE]

From ce1a11a6b9b8904f8576281ab001d841e2d6ecf0 Mon Sep 17 00:00:00 2001
From: Yuriy Artamonov <yuriy.artamonov@jetbrains.com>
Date: Sat, 30 Aug 2025 13:56:37 +0200
Subject: [PATCH 2/7] Set JDK 21 in settings

---
 .idea/gradle.xml | 1 +
 1 file changed, 1 insertion(+)

diff --git a/.idea/gradle.xml b/.idea/gradle.xml
index ce1c62c..05eca02 100644
--- a/.idea/gradle.xml
+++ b/.idea/gradle.xml
@@ -5,6 +5,7 @@
     <option name="linkedExternalProjectsSettings">
       <GradleProjectSettings>
         <option name="externalProjectPath" value="$PROJECT_DIR$" />
+        <option name="gradleJvm" value="21" />
         <option name="modules">
           <set>
             <option value="$PROJECT_DIR$" />

From 02df6e806c9f79489a7808fe9ffb32b722401a62 Mon Sep 17 00:00:00 2001
From: Yuriy Artamonov <yuriy.artamonov@jetbrains.com>
Date: Sat, 30 Aug 2025 14:05:32 +0200
Subject: [PATCH 3/7] Use 2025.1 for new plugins

---
 gradle.properties         | 4 ++--
 gradle/libs.versions.toml | 2 +-
 2 files changed, 3 insertions(+), 3 deletions(-)

diff --git a/gradle.properties b/gradle.properties
index ab20f1a..943c82a 100644
--- a/gradle.properties
+++ b/gradle.properties
@@ -7,11 +7,11 @@ pluginRepositoryUrl = https://github.com/JetBrains/intellij-platform-plugin-temp
 pluginVersion = 2.3.1
 
 # Supported build number ranges and IntelliJ Platform versions -> https://plugins.jetbrains.com/docs/intellij/build-number-ranges.html
-pluginSinceBuild = 243
+pluginSinceBuild = 251
 
 # IntelliJ Platform Properties -> https://plugins.jetbrains.com/docs/intellij/tools-gradle-intellij-plugin.html#configuration-intellij-extension
 platformType = IC
-platformVersion = 2024.3.6
+platformVersion = 2025.1.5
 
 # Plugin Dependencies -> https://plugins.jetbrains.com/docs/intellij/plugin-dependencies.html
 # Example: platformPlugins = com.jetbrains.php:203.4449.22, org.intellij.scala:2023.3.27@EAP
diff --git a/gradle/libs.versions.toml b/gradle/libs.versions.toml
index 2eacff7..1d22c04 100644
--- a/gradle/libs.versions.toml
+++ b/gradle/libs.versions.toml
@@ -5,7 +5,7 @@ opentest4j = "1.3.0"
 
 # plugins
 changelog = "2.4.0"
-intelliJPlatform = "2.7.1"
+intelliJPlatform = "2.7.2"
 kotlin = "2.2.0"
 kover = "0.9.1"
 qodana = "2025.1.1"

From 52eb4c92fba875183e75e71fcc26a5a2093645bc Mon Sep 17 00:00:00 2001
From: Yuriy Artamonov <yuriy.artamonov@jetbrains.com>
Date: Thu, 25 Sep 2025 23:26:27 +0200
Subject: [PATCH 4/7] Update intelliJPlatform Gradle plugin to 2.9.0

---
 gradle/libs.versions.toml | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/gradle/libs.versions.toml b/gradle/libs.versions.toml
index 1d22c04..f8bfcfc 100644
--- a/gradle/libs.versions.toml
+++ b/gradle/libs.versions.toml
@@ -5,8 +5,8 @@ opentest4j = "1.3.0"
 
 # plugins
 changelog = "2.4.0"
-intelliJPlatform = "2.7.2"
-kotlin = "2.2.0"
+intelliJPlatform = "2.9.0"
+kotlin = "2.1.20"
 kover = "0.9.1"
 qodana = "2025.1.1"
 

From cfa997f8d289afbae7ac82ceb318a773af21b327 Mon Sep 17 00:00:00 2001
From: Yuriy Artamonov <yuriy.artamonov@jetbrains.com>
Date: Thu, 25 Sep 2025 23:29:39 +0200
Subject: [PATCH 5/7] Disable Gradle scripts debug as it leads to restart of
 the Gradle daemon on each build

---
 .run/Run Plugin.run.xml | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/.run/Run Plugin.run.xml b/.run/Run Plugin.run.xml
index 00a760e..9db62fb 100644
--- a/.run/Run Plugin.run.xml	
+++ b/.run/Run Plugin.run.xml	
@@ -16,10 +16,10 @@
       </option>
       <option name="vmOptions" value="" />
     </ExternalSystemSettings>
-    <ExternalSystemDebugServerProcess>true</ExternalSystemDebugServerProcess>
+    <ExternalSystemDebugServerProcess>false</ExternalSystemDebugServerProcess>
     <ExternalSystemReattachDebugProcess>true</ExternalSystemReattachDebugProcess>
     <DebugAllEnabled>false</DebugAllEnabled>
     <RunAsTest>false</RunAsTest>
     <method v="2" />
   </configuration>
-</component>
+</component>
\ No newline at end of file

From faaec28ff8ed0241163c60079ee8d2a99efe8739 Mon Sep 17 00:00:00 2001
From: Yuriy Artamonov <yuriy.artamonov@jetbrains.com>
Date: Thu, 25 Sep 2025 23:38:24 +0200
Subject: [PATCH 6/7] Cleanup grammar and typos in README

---
 README.md | 20 ++++++++++----------
 1 file changed, 10 insertions(+), 10 deletions(-)

diff --git a/README.md b/README.md
index 8018edb..910ef7b 100644
--- a/README.md
+++ b/README.md
@@ -55,7 +55,7 @@ In this README, we will highlight the following elements of template-project cre
 
 Before we dive into plugin development and everything related to it, it's worth mentioning the benefits of using GitHub Templates.
 By creating a new project using the current template, you start with no history or reference to this repository.
-This allows you to create a new repository easily without copying and pasting previous content, clone repositories, or clearing the history manually.
+This allows you to create a new repository easily without copying and pasting previous content, cloning repositories, or clearing the history manually.
 
 All you have to do is click the <kbd>Use this template</kbd> button (you must be logged in with your GitHub account).
 
@@ -66,7 +66,7 @@ Once this is complete, open the newly created project's _Settings | Actions | Ge
 
 Now the project is ready to be cloned to your local environment and opened with [IntelliJ IDEA][jb:download-ij].
 
-The most convenient way for getting your new project from GitHub is the <kbd>Get from VCS</kbd> action available on the Welcome Screen, where you can filter your GitHub  repository by its name.
+The most convenient way for getting your new project from GitHub is the <kbd>Get from VCS</kbd> action available on the Welcome Screen, where you can filter your GitHub repository by its name.
 
 ![Get from Version Control][file:get-from-version-control]
 
@@ -74,7 +74,7 @@ The next step, after opening your project in IntelliJ IDEA, is to set the proper
 
 ![Project Structure — SDK][file:project-structure-sdk.png]
 
-For the last step, you have to manually review the configuration variables described in the [`gradle.properties`][file:gradle.properties] file and *optionally* move sources from the *com.github.username.repository* package to the one that works best for you.
+For the last step, you have to manually review the configuration variables described in the [`gradle.properties`][file:gradle.properties] file and *optionally* move sources from the `com.github.username.repository` package to the one that works best for you.
 Then you can get to work implementing your ideas.
 
 > [!NOTE]
@@ -268,9 +268,9 @@ The final test report is sent to [CodeCov][codecov] for better results visualiza
 
 ### UI tests
 
-If your plugin provides complex user interfaces, you should consider covering them with tests and the functionality they utilize.
+If your plugin provides complex user interfaces, you should consider covering them with tests and the functionality they use.
 
-[IntelliJ UI Test Robot][gh:intellij-ui-test-robot] allows you to write and execute UI tests within the IntelliJ IDE running instance.
+[IntelliJ UI Test Robot][gh:intellij-ui-test-robot] allows you to write and execute UI tests within the JetBrains IDE running instance.
 You can use the [XPath query language][xpath] to find components in the currently available IDE view.
 Once IDE with `robot-server` has started, you can open the `http://localhost:8082` page that presents the currently available IDEA UI components hierarchy in HTML format and use a simple `XPath` generator, which can help test your plugin's interface.
 
@@ -357,10 +357,10 @@ In the `.github/workflows` directory, you can find definitions for the following
   - Prepares a draft release of the GitHub Releases page for manual verification.
 - [Release](.github/workflows/release.yml)
   - Triggered on `released` event.
-  - Updates `CHANGELOG.md` file with the content provided with the release note.
+  - Updates `CHANGELOG.md` file with the content provided the release note.
   - Signs the plugin with a provided certificate before publishing.
   - Publishes the plugin to JetBrains Marketplace using the provided `PUBLISH_TOKEN`.
-  - Sets publish channel depending on the plugin version, i.e. `1.0.0-beta` -> `beta` channel.
+  - Sets a publication channel depending on the plugin version, i.e. `1.0.0-beta` -> `beta` channel.
   - Patches the Changelog and commits.
 - [Run UI Tests](.github/workflows/run-ui-tests.yml)
   - Triggered manually.
@@ -398,7 +398,7 @@ All plugins and dependencies used by Gradle are managed with [Gradle version cat
 > annotations = { group = "org.jetbrains", name = "annotations", version.ref = "annotations" }
 > ```
 
-Keeping the project in good shape and having all the dependencies up-to-date requires time and effort, but it is possible to automate that process using [Dependabot][gh:dependabot].
+Keeping the project in good shape and having all the dependencies up to date requires time and effort, but it is possible to automate that process using [Dependabot][gh:dependabot].
 
 Dependabot is a bot provided by GitHub to check the build configuration files and review any outdated or insecure dependencies of yours – in case if any update is available, it creates a new pull request providing [the proper change][gh:dependabot-pr].
 
@@ -444,7 +444,7 @@ You start with an almost empty changelog:
 Now proceed with providing more entries to the `Added` group, or any other one that suits your change the most (see [How do I make a good changelog?][keep-a-changelog-how] for more details).
 
 When releasing a plugin update, you don't have to care about bumping the `[Unreleased]` header to the upcoming version – it will be handled automatically on the Continuous Integration (CI) after you publish your plugin.
-GitHub Actions will swap it and provide you an empty section for the next release so that you can proceed with your development:
+GitHub Actions will swap it and provide you with an empty section for the next release so that you can proceed with your development:
 
 ```
 # YourPlugin Changelog
@@ -522,7 +522,7 @@ You can still replace it or add the `/src/main/java` directory to start working
 
 ### How to disable *tests* or *build* job using the `[skip ci]` commit message?
 
-Since February 2021, GitHub Actions [support the skip CI feature][github-actions-skip-ci].
+Since February 2021, GitHub Actions [has supported the skip CI feature][github-actions-skip-ci].
 If the message contains one of the following strings: `[skip ci]`, `[ci skip]`, `[no ci]`, `[skip actions]`, or `[actions skip]` – workflows will not be triggered.
 
 ### Why does the draft release no longer contain a built plugin artifact?

From 28451c0c0f2b1c3b2b2003c8f099496101d1d261 Mon Sep 17 00:00:00 2001
From: Yuriy Artamonov <yuriy.artamonov@jetbrains.com>
Date: Thu, 25 Sep 2025 23:51:35 +0200
Subject: [PATCH 7/7] Adjust links in README

---
 README.md | 3 +--
 1 file changed, 1 insertion(+), 2 deletions(-)

diff --git a/README.md b/README.md
index 910ef7b..eb240af 100644
--- a/README.md
+++ b/README.md
@@ -1,9 +1,8 @@
 # IntelliJ Platform Plugin Template
 
 [![official JetBrains project](https://jb.gg/badges/official.svg)][jb:github]
-[![Twitter Follow](https://img.shields.io/badge/follow-%40JBPlatform-1DA1F2?logo=twitter)](https://twitter.com/JBPlatform)
+[![Twitter Follow](https://img.shields.io/badge/follow-%40JBPlatform-1DA1F2?logo=twitter)](https://x.com/JBPlatform)
 [![Build](https://github.com/JetBrains/intellij-platform-plugin-template/workflows/Build/badge.svg)][gh:build]
-[![Slack](https://img.shields.io/badge/Slack-%23intellij--platform-blue?style=flat-square&logo=Slack)](https://plugins.jetbrains.com/slack)
 
 ![IntelliJ Platform Plugin Template][file:intellij-platform-plugin-template-dark]
 ![IntelliJ Platform Plugin Template][file:intellij-platform-plugin-template-light]