Missing Notable Changes in 2026.1?

We’re told in “Keeping Plugins Compatible” to keep up to date with notable changes / breaking changes.

I can’t see 2026.x on either of the docs post (I can only post 2 links..):

`https://plugins.jetbrains.com/docs/intellij/``

  • /api-notable.html
  • /api-changes-list.html

There also isn’t tag/sources posted for the latest EAPs (https://github.com/JetBrains/intellij-community/tags) - this is painful, we have these tags for example for IDEA:

idea/2025.3-eap-1
idea/2025.3-eap-2
idea/2025.3-eap-3
idea/2025.3-eap-4
idea/2025.3-eap-5
idea/2025.3-eap-6
idea/2025.3-eap-7
idea/2025.3-eap-8
idea/2026.1-eap-1

Is this no longer going to be provided? It’s the best way to get sources at the specific EAP version, correct?

Tags are not published only temporary due to our ongoing infrastructure migration and we have no breaking changes in public APIs in 2026.1 EAP yet

3 Likes

Branch should be okay, right? e.g 261.19799?

(Thanks for replying on a weekend as well :heart_hands: )

no breaking changes in public APIs in 2026.1 EAP yet

We’ve seem to have found breaking changes in 2026.x/261/ (seems to be in 261.19799) in the intellij-elixir plugin (https://github.com/KronicDeth/intellij-elixir) plugin.

In platform/core-api/src/com/intellij/openapi/editor/FoldingGroup.java - intellij-community/platform/core-api/src/com/intellij/openapi/editor/FoldingGroup.java at 261.19799 · JetBrains/intellij-community · GitHub), this commit: cleanup foldings (part of IJPL-222955) · JetBrains/intellij-community@42ebb49 · GitHub made changes to newGroup - cleanup foldings (part of IJPL-222955) · JetBrains/intellij-community@42ebb49 · GitHub

, which seems to be a breaking change?

We’re getting a test failure here - Add support for 2026.1 EAP, 2025.3.2 version bumps · KronicDeth/intellij-elixir@3786bcd · GitHub) for it:

e: file:///home/runner/work/intellij-elixir/intellij-elixir/src/org/elixir_lang/folding/Builder.kt:260:75 Argument type mismatch: actual type is 'String?', but 'String' was expected.

Code: /src/org/elixir_lang/folding/Builder.kt#L257-L261 intellij-elixir/src/org/elixir_lang/folding/Builder.kt at 7cc76757e6e496dc220e9f50c1a9aec30c7c5952 · joshuataylor/intellij-elixir · GitHub

                                            val moduleAttributeName = atNonNumericOperation.moduleAttributeName()
                                            val foldingGroup =
                                                foldingGroupByModuleAttributeName.computeIfAbsent(moduleAttributeName) { debugName: String? ->
                                                    FoldingGroup.newGroup(debugName)
                                                }
                                            foldingDescriptorList.add(

(Again, as a new member I can’t post links, sorry for the weird link formatting, as I can’t post markdown links).

This commit adds @NotNull for result and parameter which is only source-incompatible with Kotlin code that passes null there, while fully binary-compatible and will not break existing plugin versions.

Incompatible API Changes in the documentation is the last resort for us when we cannot avoid breaking binary compatibility.

While we are writing down more Notable API changes one can now track API changes of the platform in YouTrack: https://youtrack.jetbrains.com/issues?q=tag:%20ij-api%20project:%20IJPL