2026.3: Breaking API change in Navigatable without announcement

Navigatable#navigate was changed so that it can no longer be used via delegation: [navigation] IJPL-253947: Mark Navigatable#navigate as override-only · JetBrains/intellij-community@5703000 · GitHub

A legitimate use case (delegation) is now blocked for plugins, but still used in the IDE’s own bundled plugins.

Why is that, and why is there no documentation with migration guidance about this breaking change?

I have resolved this by changing a delegation to a psiElement property from

override fun navigate(requestFocus: Boolean) = psiElement.navigate(requestFocus)

to

override fun navigate(requestFocus: Boolean) {
    NavigationService.getInstance(project = psiElement.project)
        .requestNavigate(
            psiElement,
            if (requestFocus) NavigationOptions.requestFocus() else NavigationOptions.defaultOptions()
        )
}

Is that as intended?

Hi, Oliver! Changes are still in progress, in the next release will make it publicly available, but not at the moment, this annotation won’t make it to 263 release. So your code won’t be affected in the upcoming release

Hi Nikolay, thanks for the response!

The change already did affect my plugin, as folks have requested an EAP version: https://plugins.jetbrains.com/plugin/27749-testballoon/versions/eap

If there is a publicly available EAP build of the IDE, people will prepare plugins for it (I’m building against “latest”). Otherwise, others won’t test the IDE (and compatible plugins) as early as possible.

So I guess API changes in a publicly available EAP builds should be treated the same way as in releases, with documentation and deprecation cycles.

There will be fixed EAP build next week where validation should pass easily, we release new builds each week

Since I’ve already dealt with the issue as shown above: Can I just keep my modified code and expect it to work with the next EAP and upcoming releases? I don’t want to bother users with micro-updates.