A new minor version is available on the project Gitlab releases and on the JetBrains plugin marketplace. It removes usage of JetBrains internal classes to keep compatibility with 2026.2 EAP . Install it by clicking on the widget on the right. On this post there is a summary of the changes since version |
Preface
Around mid-November 2025 the wonderful people of JetBrains emailed me to discuss the possibility of collaborating for improving the Vale CLI plugin experience in JetBrains IDEs. They invited me to a Google Meet call with one of their developers to go over the details of their Vale integration in the Grazie Pro Plugin and how to possibly apply those practices on this plugin.
Just as these changes were almost ready, I received an improvement contribution that I hadn’t noticed because of my GitLab account settings. As a result, I asked the contributor to rework it. Fortunately, this didn’t discourage them, and they went on to submit 10 more contributions.
So, without much further ado, here are the latest changes from version 0.0.25 to 0.0.37 .
Vale CLI Plugin Changes Summary
As a result of applying the suggestions and contributions, the plugin has
-
Improved linting workflow
-
Better IDE integration,
-
Per-project Vale configuration
Improved linting workflow
Version 0.0.28 changed how the plugin lints files with Vale, from manual actions on selected files or current editor or on the whole project
towards automatically linting the file opened in the editor in the background.
Added:
-
Vale styles synchronization action
-
Run Vale lint with the content of the editor instead of file which allowed the lint process to run in the background.
Removed:
-
Tools menu global lint action
-
Editor popup menu actions
-
Project view linting selected files popup actions
Per-project settings
Starting in 0.0.28, the plugin supports different Vale configurations for different projects instead of relying solely on global settings.
Later, 0.0.32 improved this further by storing project-specific settings inside the sharable .idea directory, making them suitable for version control and team sharing.
Better IDE integration
The plugin now behaves much more like a native JetBrains language plugin, due to
-
Better detection of Vale binary and Vale configuration file
-
Navigation to Vale rules and Vale configuration file
-
Documentation of Vale style rules and Vale configuration file entries.
-
A quick-fix chooser appears when Vale suggests more than one replacement.
Better binary and configuration detection
Several releases improved how the plugin discovers and uses Vale:
-
Don’t run Vale when no configuration exists
-
better handling when configuration files are missing
-
better detection of Vale installed through pyenv
-
option to disable extension restrictions when invoking Vale
Navigation
Added:
-
navigate directly to the Vale configuration file
-
navigate from
.vale.inientries to the referenced rule definitions
Version timeline
| Version | Release date | Description |
|---|---|---|
0.0.25 … 0.0.27 |
07 Dec 2025 … 21 Dec 2025 |
Incremental fixes |
0.0.28 |
08 Feb 2026 |
Major release: per-project configs, stdin linting, sync action, workflow redesign |
0.0.29 |
15 Feb 2026 |
IO and EDT fixes |
0.0.30 |
22 Feb 2026 |
Better quick fixes, EDT fix |
0.0.31 |
08 Mar 2026 |
Skip running Vale without config |
0.0.32 |
23 Mar 2026 |
Shared project settings, pyenv detection, extension restriction option |
0.0.33 |
28 Mar 2026 |
Documentation integration |
0.0.34 |
11 Apr 2026 |
Navigate to config file |
0.0.35 |
18 Apr 2026 |
|
0.0.36 |
17 May 2026 |
Refresh/threading fixes and dependency fixes |
0.0.37 |
07 Jun 2026 |
2026.2 compatibility (remove internal API usage) |
Wrap up and next steps
That covers the highlights from 0.0.25 to 0.0.37. If you want the full
picture, the complete changelog is available on the
plugin documentation "What’s new" section .
Thanks to the JetBrains team for reaching out and taking the time to walk me through their Vale integration approach. Thanks also to everyone who opened issues along the way, and to the contributor who submitted the improvements that shaped these latest releases.
And as for the next steps?
Right now the Gitlab project has zero open issues!
-
Perhaps address a couple of deprecated API usages as newer IDE versions require it.
-
Implementing split mode would be a big effort.