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…

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

+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.

[image] Jonathan Lermitage: that’s what was announced. We have not announced yet, but very soon

This was announced on Slack :wink:

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 upg…

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

IntelliJ Platform

yuriy.artamonov (Yuriy Artamonov) May 16, 2025, 1:49pm 4

We have not announced yet, but very soon

Topic		Replies	Views
New until-build checking - plugin is installing a later version IntelliJ Platform	0	72	June 1, 2025
Until-build ignored for 243+? IntelliJ Platform	14	251	July 23, 2025
IDE version 252? IntelliJ Platform	5	524	May 2, 2025
Why can't I set an until-build value greater than 251.*? JetBrains Marketplace	11	265	May 31, 2025
How best to handle multiple versions? JetBrains Marketplace	9	240	September 24, 2025

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

Related topics