chore(deps): Gradle 9.6.1 and IntelliJ Platform plugin 2.18.1 together - #26
Merged
Merged
Conversation
Dependabot proposed these as #17 and #18 and neither can merge alone. They require each other: #17 plugin 2.18.1 on Gradle 8.10.2 > IntelliJ Platform Gradle Plugin requires Gradle 9.0.0 and higher #18 Gradle 9.6.1 on plugin 2.1.0 > Adding a provider of configurations directly to the configuration container is not allowed (plugin/build.gradle.kts:50) Together they build. Also folds in #23 (setup-java v4 -> v5), which conflicted after the other action bumps landed, and the assertj patch that travelled with #17. The plugin bump changes the pluginVerification DSL. `ide(...)` is gone and the replacement is `create(type, version)`: - ide("IC-2024.2.5") + create(IntelliJPlatformType.IntellijIdeaCommunity, "2024.2.5") Worth recording why that matters beyond the rename. On 2.1.0 the string form worked while the typed overload accepted its arguments and then scheduled no verification at all — a green run that checked one IDE while appearing to check two, which is what the report-count assertion in ci.yml was added to catch. 2.18.1 removes ide() outright, so the same mistake is now a compile error. The assertion stays anyway; it guards the count, not the spelling, and its grep moves to the new call. Verified locally on Gradle 9.6.1: build, verifyPluginProjectConfiguration and verifyPluginStructure pass, and the Verifier still schedules both IDEs — Scheduled verifications (2): IC-242.24807.4 -> Compatible IC-243.26053.27 -> Compatible
This was referenced Aug 3, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Supersedes #17, #18 and #23.
Dependabot proposed the first two separately and neither can merge alone — they require each other:
IntelliJ Platform Gradle Plugin requires Gradle 9.0.0 and higherAdding a provider of configurations directly to the configuration container is not allowed(plugin/build.gradle.kts:50)Together they build. This also folds in #23 (setup-java v4 → v5), which conflicted once the other action bumps landed, and the assertj patch that travelled with #17.
The DSL moved
Worth recording beyond the rename. On 2.1.0 the string form worked while the typed overload accepted its arguments and scheduled no verification at all — a green run that checked one IDE while appearing to check two. That is precisely what the report-count assertion in
ci.ymlwas added to catch. 2.18.1 removeside()outright, so the same mistake is now a compile error instead.The assertion stays: it guards the count, not the spelling. Its grep moves to the new call.
Verified locally on Gradle 9.6.1
build,verifyPluginProjectConfigurationandverifyPluginStructurepass, and the Verifier still schedules both IDEs: