Yann Cébron
Yann Cébron
as a workaround, specify since/until-build values (can be "empty string") explicitly via `patchPluginXml` task instead https://plugins.jetbrains.com/docs/intellij/tools-gradle-intellij-plugin.html#tasks-patchpluginxml, see also https://plugins.jetbrains.com/docs/intellij/configuring-plugin-project.html#patching-the-plugin-configuration-file
This seems obsolete in the latest version of `release.yml` https://github.com/JetBrains/intellij-platform-plugin-template/blob/main/.github/workflows/release.yml#L41
why can't you use the default bundled workflows as-is?
https://intellij-support.jetbrains.com/hc/en-us/community/posts/14397678486418/comments/15082225353874 might be helpful
Will ping the WS team on that.
That would be awesome. Some additional thoughts/suggestions: 1. show total number of possible combinations resulting from currently selected variants "using 231 of 8392 possible combinations" 2. show "you have trained...
Please reopen with updates/more details if it still reproduces on your side.
Thanks for your detailed suggestions, we are very much interested in optimizing the build/CI performance for plugin projects. The suggested optimizations to skip execution of Gradle tasks make a number...
might affect 2.x as well
see also #1591 FTR Kotlin is now the preferred language for Gradle build files