Breaking change in Cucumber java plugin 2025.3 / recommended() versions in Verifier

IntelliJ Platform
1

I’m the developer of a plugin which extends features for cucumber feature files. For this it uses (or used to use) org.jetbrains.plugins.cucumber.java.steps.factory.JavaStepDefinitionFactory which was removed with [cucumber-java] remove the split between JavaStep1xDefinition.java an… · JetBrains/intellij-plugins@653b98f · GitHub

I have two questions:

  1. Shouldn’t this be in the list of breaking changes? If not, where are breaking changes for bundled plugins mentioned, if at all?
  2. I just found out this would’ve been caught by the plugin verifier but the recommended() version setting doesn’t seem to include the next EAP. After adding 253.28294.251 I got an error. Why is the next expected version not part of the recommended versions to verify against?

Thank you.

2

Hello,
yes, you are right. It is a breaking change. The documentation is in the Pull Request now, soon to be published. Sorry for the inconvenience of not documenting that earlier.

4

Hi Simon,
I made that change and forgot to update the breaking changes page. I’m sorry that it caused you problems. It’s updated now.

If you have any more questions regarding development of your plugin, please don’t hesitate to ask!

5

Thanks guys. It isn’t a huge bother. It only affects code that fixes some bugs that you fixed recently yourself so I can just simply delete the affected code. I was just wondering if I followed the correct procedure for breaking changes.

6

Hey! The fact that the recommended() helper overlooked the 253.28294.251 was an issue on our side. It happened, because there’s no longer IC distribution available for 253+, and IU should be suggested instead (yes, if you target i.e. IC-2025.2, the IU-253.x should be returned now).
I just fixed that in the IntelliJ Platform Gradle Plugin — it should be released pretty soon.

Edit: relevant commit: