(version ‘2026.1.2’) is not compatible with the current version of the IDE, because it requires build 261.* or newer but the current build is IU-261.19799.12
I’m afraid it’s not clear what issue you’re currently facing.
I am running runIDE, and my plugin is not being loaded. I am getting the following message, which seems to contradict itself. The current version is 261.19799.12, which should satisfy requirement 261.*, correct?
I tried various versions – got this message also in the current one:
pluginVersion=2026.1.2
pluginSinceBuild=261.*
platformType=IU
platformVersion=261.19799-EAP-CANDIDATE-SNAPSHOT
in the catalog I am using:
intelliJPlatform = "2.11.0"
need anymore info?
It is the right bracket actually, please use pluginSinceBuild=261 to start with this Major
This is a known change in the Gradle plugin?
As far as I know it was always like this, since requires some build number and not a mask. Any of 261, 261.19799 or 261.19799.12 would do
It worked, I think it should fail in this case or at least a better warning or explanation, no? With what version it can work when configured with *?
Thank 
<since-build> must not contain wildcards. This is documented in Build Numbers and even validated with IntelliJ Plugin Verifier.
Yes but when running the runIde it is not failing… and the message is not clear IMO
Hum, I wanted to say there is no logic when using a wildcard in since-build, but I think I understand.
Let’s say you want to support all 2026.1 IDEs.
It makes sens to use 261.* in until-build, because you can’t know the exact latest version. Without a wildcard, you would have to use something like 261.9999999 (some plugins developers did that a long time ago - I was one of them).
For the since-build, we can use the same approach: because we don’t know the exact minimum version we wan to support (is it 261.100123 or 261.123456?), we may want to use 261.* as well.
(old? 
) Plugin developers may not know that we can simply use 261.
It’s not necessarily obvious. At least, both approaches seem valid to me, and unless you read the documentation carefully, you can use the wrong approach.
I’m not saying we should allow plugin developers to use a wildcard in since-build, but I’m trying to understand why this might be confusing. But, of course, it’s very important to read the documentation.
Edit: actually, it would be also logic to set until-build=261 as well. It would mean: all 261 version, because in since-build=261, 261 means the same thing: it’s like 261.*. You see how it’s confusing? Or, set until-build=262 (if the interval is not inclusive).
For a long time now, I’m using since-build=261.0 and until-build=261.* to support all builds of a particular major version, e.g. 2026.1.
But usually I limit since-build to the version I’m building against, e.g. since-build=261.19799 or since-build=261.19799.0 for the (EAP) version 261.19799.20. Allowing earlier versions, especially with EAPs, could cause problems if an earlier EAP with incompatible API is used with the plugin built against a newer version.