2025.2: How does the new until-build handling work?

IntelliJ Platform
1

I installed the new 2025.2 eap. The upgrade by Toolbox automatically copied the installed plugins from 2025.1 to the new 2025.2 installation.

Among these plugins it copied a plugin (BashSupport Pro), which defines until-build=251.*, to 2025.2 and the plugin was enabled in 2025.2.

But the plugin is marked as compatible until 2025.1 on the Marketplace.

After uninstalling the copied plugin, I’m unable to install it again from the Marketplace.

  • Is there more information how the new until-build treatment works?
  • Is copying the 251.* plugin to 2025.2 intentional? It’s not marked as compatible on the Marketplace, which is supposed to be the source of truth now for 2025.2.
1 Like
2

+1 for more info as this can make users uninstall plugin for not being compatible…

3

+1. If my memory is correct, when targeting 251.* IDEs, the until-build flag from the plugin.xml is ignored. You have to specify it on the marketplace, on every release, which can be very annoying. At least, that’s what was announced.
Meanwhile, I’m not sure if this is how it works today.

4

We have not announced yet, but very soon

5

This was announced on Slack :wink:

6

I’m unhappy about this change. My plugin is large and complex, and I maintain separate code branches for the different IntelliJ versions I support specifically to avoid compatibility problems. This change is taking that control away from me, for no visible benefit to me.

As a data point, I just upgraded my IDE to 2025.2. My plugin was copied over (with previous versions it would not start up due to the until-build) and then immediately failed at startup with an ExceptionInInitializerError.

If the new means of controlling this is via the Marketplace, is it possible to set the until-build value per version via an API so that at least I can do that when I deploy?

7 Likes