I just received an email from JetBrains about:
Request for Plugin Compatibility Update for upcoming IDE Release
We noticed that due to a limited Until range, the following plugins will not be compatible with the upcoming IDE version (252):
I would assume that 252 is 2025.2, and any release at that level has generally been run through an EAP program before the release. However, the EAP program is current closed:
Am I just interpreting this wrong? Was this an unintended email to plugin devs?
That may have been a typo, I hope 
Does your plugin have pluginUntilBuild = 251.* or similar? If so, then this warning is correct: Your plugin would be marked as incompatible for users using 2025.2 when it is released.
@insyncwithfoo sorry if I wasn’t clear, but yes, I do constrain the until-build value in my plugin.xml given that there are breaking SDK changes in almost every significant IDE update these days.
My question wasn’t about what this message means but rather that it’s unexpected to receive one for what I assume would be 2025.2 almost immediately after the release of 2025.1, and without an active EAP program to verify/fix things that might be broken.
Like @AlexanderBartash, I’m assuming/hoping that it was a mistake.
Such a constraint means that your plugin is incompatible with later IDE versions by default, regardless of how it fares at runtime. The compatible range for each release can be edited manually via Marketplace, so I’d say there’s no need to specify an upper bound for the latest version; you can just change it when you find an incompatibility.
@insyncwithfoo again, thanks for the response, but yes, I understand that. That’s intentional for the reason stated above…breaking plugin SDK changes across JetBrains’ seasonal releases that require plugin client changes to ensure binary compatibility.
Every seasonal release, I use the EAP program to make those client changes, and I update the value for until-build when the EAP enters the RC phase and further breaking plugin SDK changes are unlikely.
My question here is not about what this message means. It’s about why we’d be receiving an email about 252/2025.2 only a couple of weeks after 251/2025.1 was released, and when there’s no active EAP program for 252.
Hopefully that helps clarify my question/concern.