What's the 2025.2 release date?

IntelliJ Platform
21

I always try to release a new version of my plugins as close as possible to the first EAP, but I believe removing the until field is a bad decision.

If I don’t make it in time for the EAP, those brave developers who upgrade early will face breaking compatibility issues unless I go through all my previous releases on the Marketplace and manually add until build constraints until I can fix them. With four plugins and a full-time job, this isn’t something I can do quickly.

Since I personally use the latest EAP builds myself, I know firsthand how frustrating it can be when plugins break. I’ll have to think twice before updating because I’ll run into issues from all plugins that haven’t been updated yet.

The more advance notice we have about upcoming releases, the easier it is for us to prepare. Still, I really hope you’ll reconsider removing the until field.

22

honestly, I don’t understand what JetBrains gains from removing the until field. Maybe you could run an automated check across all (or a set ) Marketplace plugins and automatically set the until value for those that are not compatible with the latest version. That way, users won’t encounter breaking errors just because a plugin wasn’t updated in time. It would help maintain a smoother experience for both users and developers.

1 Like
23

We are going to detect and update until-build on the Marketplace for sure, working on it

24

Good to know, so I don’t need to worry about all versions with since 252 without an until value?