Repository navigation
build: extend IDE compatibility range to 2025.1 - 2026.3 - #542
Merged
Merged
Conversation
AkibaAT
force-pushed
the
feature/541-2026.3-compatibility
branch
from
September 18, 2026 22:20
0d9c939 to
93f4fab
Compare
2 tasks done
AkibaAT
force-pushed
the
feature/541-2026.3-compatibility
branch
from
September 26, 2026 19:33
e3b1fc4 to
1a061af
Compare
The state watcher runs `ddev describe` every 10 seconds, so a broken local setup raised an IDE error on every poll. Failures of `ddev --version` and `ddev describe` are now logged as warnings and shown once as a notification carrying the message DDEV reported, until the command succeeds again or the plugin is reloaded. Commands that exit successfully without output fail with an explicit message instead of a JSON parse error. Fixes DDEV-INTEGRATION-PLUGIN-WE Fixes DDEV-INTEGRATION-PLUGIN-WJ Fixes DDEV-INTEGRATION-PLUGIN-WM Fixes DDEV-INTEGRATION-PLUGIN-12Z Fixes DDEV-INTEGRATION-PLUGIN-144 Fixes DDEV-INTEGRATION-PLUGIN-1ZY Fixes DDEV-INTEGRATION-PLUGIN-200 Fixes DDEV-INTEGRATION-PLUGIN-206 Fixes DDEV-INTEGRATION-PLUGIN-207 Fixes DDEV-INTEGRATION-PLUGIN-20B
… is gone A ddev binary path stored in the settings stays there after DDEV is moved or uninstalled, e.g. a Homebrew path on macOS or a Linux path on Windows outside of WSL. A configured absolute path that no longer exists, or a binary that cannot be started, is now replaced by the one found on the PATH. Fixes DDEV-INTEGRATION-PLUGIN-139 Fixes DDEV-INTEGRATION-PLUGIN-13Q Fixes DDEV-INTEGRATION-PLUGIN-119 Fixes DDEV-INTEGRATION-PLUGIN-13C Fixes DDEV-INTEGRATION-PLUGIN-20G Fixes DDEV-INTEGRATION-PLUGIN-20D
With json-output enabled in the global DDEV config, `ddev --version` prints a JSON log line and the greedy version pattern captured the rest of that line. Fixes DDEV-INTEGRATION-PLUGIN-20A
Offline machines, proxies and GitHub outages make the release check fail; it is skipped with a warning instead of raising an IDE error. Fixes DDEV-INTEGRATION-PLUGIN-RT Fixes DDEV-INTEGRATION-PLUGIN-XV Fixes DDEV-INTEGRATION-PLUGIN-205 Fixes DDEV-INTEGRATION-PLUGIN-124
The state watcher checks for .ddev/config.yaml every 10 seconds. A plain file system check avoids a synchronous VFS refresh on each poll, which fails on cancellation or while the VFS is being rebuilt. Fixes DDEV-INTEGRATION-PLUGIN-20C Fixes DDEV-INTEGRATION-PLUGIN-20E Fixes DDEV-INTEGRATION-PLUGIN-1ZX
A state update finishing after the project was closed published to its listeners, which then failed to resolve project services. Fixes DDEV-INTEGRATION-PLUGIN-208
createTtyConnector(ShellStartupOptions) only exists from 2026.2 on, and the TtyConnector resize strategy hook only from 2026.3. Sessions are created through createProcess(options) and createTtyConnector(process), which every supported platform version provides.
PluginManagerCore.isLoaded only exists from 2026.2 on, and PluginManager.findEnabledPlugin is internal API from 2026.2 on.
ErrorReportSubmitter.getPluginDescriptor is override-only API in 2025.3 and the plugin descriptor lookups are internal API from 2026.3 on. The build writes the plugin version into a resource that the error reporter reads.
Release 1.2.9 raised the minimum to 2026.2, which left users of 2025.1 to 2026.1 on 1.2.8. The plugin is compiled against 2025.1 with Java 21 again and verified against every release line from 2025.1 to 2026.3. The 2025.1 test runtime needs the grid plugin and its chart dependencies for the database plugin to load.
The terminal runner hooks createProcess(options) and createTtyConnector(process) are scheduled for removal from 2025.3 on, but 2025.1 and 2025.2 have no createTtyConnector(options). Each platform variant now compiles its own PlatformTerminalRunner from src/platform251 or src/platform261, selected with -PplatformVariant. The variants are separate Marketplace versions with a +251 or +261 suffix and their own compatibility ranges. CI builds, tests and verifies both, and the release workflow publishes both. The 261 verification fails on scheduled-for-removal API usages. The verifier resolves node-remote-interpreter from the Marketplace for some DataGrip versions without its NodeJS dependency, which reports the Node.js interpreter classes as missing. That plugin cannot load in DataGrip, so the problem is ignored.
FileEditorManager.openFile(VirtualFile, boolean) is reported as deprecated by the Marketplace. OpenFileDescriptor.navigate(true) opens and focuses the file on every supported platform version.
- Gradle wrapper 9.6.1 -> 9.8.2 - org.jetbrains.intellij.platform 2.17.0 -> 2.20.0 - IntelliJ Plugin Verifier 1.408 -> 1.411 - Gson 2.14.0 -> 2.15.0 - Sentry 8.47.0 -> 8.63.0 - JUnit Jupiter and JUnit Platform 6.1.1 -> 6.1.3 - Mockito 5.23.0 -> 5.24.0
AkibaAT
force-pushed
the
feature/541-2026.3-compatibility
branch
from
November 5, 2026 21:15
d168761 to
a934bd2
Compare
AkibaAT
force-pushed
the
feature/541-2026.3-compatibility
branch
from
November 5, 2026 22:11
bb1c963 to
3fa1b13
Compare
|
AkibaAT
changed the title
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The Problem/Issue/Bug:
2026.3 released with some incompatibilities with the existing code
How this PR Solves the Problem:
Update the code, but keeping two variants going forward, so we don't support just the very latest versions anymore
The new target range is 2025+
Manual Testing Instructions:
Related Issue Link(s):