@chriscarini yes, I just wanted to mention it in this thread
1 Like
Gotcha! Yeah, I had just wanted to confirm, because I saw similar error in one of the plugins I maintain. Thank you! 
2 Likes
@robert.novotny, @yann.cebron, @changjiong.liu Any updates on this issue? This is blocking me from releasing my plugins for 2025.1, and it’s been three weeks since I reported it with no progress or feedback.
2 Likes
Just wanted to chime in and say that Nx Console is experiencing the same issue. Even with the dependencies declared and on the latest version of the plugin verifier, the plugin verification throws this error 
Looking forward to a resolution!
I’m encountering the same issue and have created a ticket for it: YouTrack Issue MP-7358.
It might help to leave a comment or upvote the issue to emphasize its urgency.
1 Like
Just came here to say it now works (sorry didn’t see your message earlier @7ur1n9) 
So yeah seems to be resolved 
This has been resolved in Plugin Verifier 1.384.
Just wondering why the new JSON plugin should support 251.* versions if there are no supported versions in the market:
It is bundled plugin in all products, so even when not uploaded to Marketplace it is compatible when compiled with products
I’ve tried to add bundled plugin com.intellij.modules.json, gradle said there are no such bundled plugin. I built against IU 251 with targets range 243–251 and used the plugin in plugins sections pointing to one of 243.* versions.
No way to pass the gradle dependencies update. If I just add to regular plugins sections the json module, than verifier in the marketplace do not pass.
Hi Robert, do you know if there is an ETA when this new plugin verifier version will make its way to production/the main plugin verification tool? I’m still seeing everything verified against 1.383 which still has this issue. Thanks for all the support!
We uploaded the plugin for review, and it seems it won’t be approved because of the same issue. What can be done about it? Verifier used: 1.383
* binary incompatible with IntelliJ IDEA Ultimate IU-251.23774.200 due to the following problems
Undeclared plugin dependency (3 problems)
Plugin 'com.intellij.modules.json' not declared as a plugin dependency for class `Json5FileType`. JSON support has been extracted to a separate plugin. (1 problem)
Plugin 'com.intellij.modules.json' not declared as a plugin dependency for class `Json5Language`. JSON support has been extracted to a separate plugin. (1 problem)
Plugin 'com.intellij.modules.json' not declared as a plugin dependency for class `JsonLanguage`. JSON support has been extracted to a separate plugin. (1 problem)
gradle.properties contains: platformBundledPlugins = com.intellij.modules.json
plugin.xml contains <depends>com.intellij.modules.json</depends>
I noticed the same thing with the 2025.1 compatible version of my plugin that I uploaded this morning:
Nothing has changed in terms of how I express dependencies. Basically this build is just changing until-build to be 251.* and a few very minor updates due to (non-JSON-related) plugin SDK changes.
It looks like this update has been approved/published, but that’s a lot of noise!
1 Like
@yuriy.artamonov is there a solution or workaround for this bug?
This bug is preventing me from publishing the latest version of my plugin.
Any updates on this?
I also see this, all configs are correct
I see those errors, but everything works fine and configs are correct
Hello, @natalia.melnikova , could you help here
now without direct chat groups, it’s hard understand what prevents plugin from approval, those ghost errors, or something else
2 Likes
I have the same problem, is there a solution now?
This makes it worse:
(that happens following your suggestion and not having
plugin("com.intellij.modules.json") in build.gradle.kts)
Can you please revise or update your comment? There’s already a lot of bad/broken advice on this topic.
It seems that we have to specify the json module version (I get an error without it), which means we need to get a version number somehow.
Luckily, since @xepozz’s comment, there’s a version for 2025.1 listed on that page, which seems to work.
In any case, please revise your comment - as it sounds now it gives the wrong impression.
