Open Pakisan opened 1 month ago
Regarding specifying every single bugfix update: this is (usually) not necessary. Bugfix updates are backwards-compatible by design.
"2022.3",
"2022.3.1",
"2022.3.2",
"2022.3.3",
In this case, checking against latest available bugfix version (2022.3.3) would be sufficient (and speedup this task considerably, apart from saving many GBs of space).
Regarding differences between local run and results from Marketplace: please check the local version of Plugin Verifier matches the one used on Marketplace.
What happened?
Plugin verification is totally broken
configuration:
execution:
execution result:
Incompatible build
Based on plugin verification report, looks like I can publish it without worries, but in fact is not true
Fact 1
Checking plugin inside 2024.1.6 via
:runIde
, was successfulWhile after installation of fresh downloaded 2024.1.6 with installation of plugin from disks, reproduces incompatibility
Fact 2
Verification report is not same, as verification results on plugin page
Fact 3
Looks like new version of Gradle plugin broke compatibility, because previous version build with v1 was ok
Fact 4
Changing id("org.jetbrains.intellij.platform") version "2.0.1" to id("org.jetbrains.intellij") version "1.17.4" builds compatible build with old gradle plugin.txt build with new gradle plugin.txt plugin
Relevant log output or stack trace
No response
Steps to reproduce
Clone repo https://github.com/asyncapi/jasyncapi-idea-plugin, switch to
/release/2.6.0
Choose IDEA version 2024.1.6
./gradlew :verifyPlugin
./gradlew :runIde
Inside created IDE everything is working smoothly
Download 2024.1.6 and install plugin manually, check IDEA log file
Gradle IntelliJ Plugin version
2.0.1
Gradle version
8.10
Operating System
None
Link to build, i.e. failing GitHub Action job
No response