Is there a reason for that? Is it already reflected on the marketplace and in IDEs? Will this affect existing plugin releases?
I think this is a good thing for most plugins. Meanwhile, some plugins may want to restrict the until-build for good reasons (like support…). Is there any reason to force this new behavior?
Just a personal feeling, it would be good to get involved in such impacting changes. If my understanding is correct, there has been no discussion with the plugin developers community.
If this really is what it appears to, then I strongly dislike it already
There’s a reason I publish only for one major release. I don’t want to be swamped with exceptions when an EAP is out and want to do QA before I publish…
Important note: until-build is still honored if it comes from a custom repository or marketplace response. Until-build is only disregarded if it comes from a plugin.xml in a plugin artifact.
Does this mean if one manually edits the below (see screenshot) in the specific plugin version on marketplace, that the until-build will be honored?
If my understanding is correct, the until field on the marketplace should be blank if the until field from the plugin.xml is set to 251+.
Meanwhile, I’m probably wrong because I recently uploaded a new plugin release, with the until field (plugin.xml) set to 252.*, and the until field on the marketplace has been automatically set with 252.*.
I’m lost. I expect the marketplace won’t unset the until field later for existing plugin releases
Also, I see that several 3rd-party plugin are still using the intellij platform plugin v1 (migration to v2 can be painful), which does not show a warning about that. They will probably miss this information.
What’s your plans for existing plugin releases? Will we have to set the until-build field manually on the marketplace for each existing plugin release?
This would be a nightmare…
I don’t understand why there won’t be a way to do that programmatically (like an API, or the good old plugin.xml?). For both existing (?) and future plugin releases, once IJ 2025.3 has been released.
This is a regression for plugin developers (we lose control), and I don’t see the benefit for users, because we set the until-build property for good reasons. Could you please explain your motivation?
If you feel your life is too beautiful, you can also use the Network tab of your browser’s DevTools to check the network requests made when the Compatibility Range UI fields are edited (to copy the corresponding JS fetch() call, right click the request’s row, then Copy → Copy as fetch).
We are looking for automation and web API options for plugin deploy as well. So no Selenium needed.
I personally believe by using until-build people do a lot of harm to the ecosystem. But the only thing that we will change is usage of it in binaries, it will be no-go.
Please do not react too quickly before we publish details
