You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As of now with every new major or minor release of IntelliJ the plugin is incompatible with the new release. Everytime someone must modify the build.gradle.kts to support the new IntelliJ release. (See e.g. #99 and #133)
As this usually takes some days to be done, users of the plugin that update early to a new IntelliJ release cannot use the plugin for some days.
I suggest to stop specifying the untilBuild property. Thus all future IntelliJ releases are supported.
How will this change help?
Users of the plugin can freely update to new releases of IntelliJ without having to wait some days for the plugin to work again
Nobody needs to update the build.gradle.kts with every release of IntelliJ
Why do we need this improvement?
As of now with every new major or minor release of IntelliJ the plugin is incompatible with the new release. Everytime someone must modify the
build.gradle.kts
to support the new IntelliJ release. (See e.g. #99 and #133)As this usually takes some days to be done, users of the plugin that update early to a new IntelliJ release cannot use the plugin for some days.
I suggest to stop specifying the
untilBuild
property. Thus all future IntelliJ releases are supported.How will this change help?
build.gradle.kts
with every release of IntelliJScreenshots
No response
How could it be implemented/designed?
According to the docs (https://plugins.jetbrains.com/docs/intellij/tools-intellij-platform-gradle-plugin-extension.html#intellijPlatform-pluginConfiguration-ideaVersion-untilBuild) you can set
untilBuild = provider { null }
. This results in no upper bound for the supported IntelliJ release.I tried this locally and was able to run the plugin in IntelliJ 2024.3 (Build #IU-243.21565.193) which is not yet supported by the latest release of the plugin.
🚧 Breaking changes
No
👀 Have you checked for similar open issues?
🏢 Have you read the Contributing Guidelines?
Are you willing to work on this issue?
Yes I am willing to submit a PR!
The text was updated successfully, but these errors were encountered: