chore(deps): bump the gradle-minor-patch group across 1 directory with 2 updates - #17
Closed
dependabot[bot] wants to merge 1 commit into
Closed
chore(deps): bump the gradle-minor-patch group across 1 directory with 2 updates#17dependabot[bot] wants to merge 1 commit into
dependabot[bot] wants to merge 1 commit into
Conversation
dependabot
Bot
added
dependencies
…h 2 updates Bumps the gradle-minor-patch group with 2 updates in the / directory: [org.assertj:assertj-core](https://github.com/assertj/assertj) and org.jetbrains.intellij.platform. Updates `org.assertj:assertj-core` from 3.27.0 to 3.27.7 - [Release notes](https://github.com/assertj/assertj/releases) - [Commits](assertj/assertj@assertj-build-3.27.0...assertj-build-3.27.7) Updates `org.jetbrains.intellij.platform` from 2.1.0 to 2.18.1 --- updated-dependencies: - dependency-name: org.assertj:assertj-core dependency-version: 3.27.7 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: gradle-minor-patch - dependency-name: org.jetbrains.intellij.platform dependency-version: 2.18.1 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: gradle-minor-patch ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
Bot
changed the title
dependabot
Bot
force-pushed
the
dependabot/gradle/gradle-minor-patch-0f34165ada
branch
from
August 3, 2026 14:24
d648a0b to
c93e00b
Compare
GabrielBBaldez
added a commit
that referenced
this pull request
Aug 3, 2026
#26) 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
Member
|
Superseded by #26, which lands this together with what it needs. On its own this could not build — #17 and #18 require each other (plugin 2.18.1 needs Gradle 9.0.0+), so merging either alone would have broken main. #26 carries all three, plus the Verified on Gradle 9.6.1 — the Plugin Verifier still schedules both IDEs and both report Compatible. |
Contributor
Author
|
This pull request was built based on a group rule. Closing it will not ignore any of these versions in future pull requests. To ignore these dependencies, configure ignore rules in dependabot.yml |
This was referenced Aug 3, 2026
dependabot
Bot
deleted the
dependabot/gradle/gradle-minor-patch-0f34165ada
branch
August 3, 2026 14:37
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.
Bumps the gradle-minor-patch group with 2 updates in the / directory: org.assertj:assertj-core and org.jetbrains.intellij.platform.
Updates
org.assertj:assertj-corefrom 3.27.0 to 3.27.7Release notes
Sourced from org.assertj:assertj-core's releases.
... (truncated)
Commits
e840716[maven-release-plugin] prepare release assertj-build-3.27.785ca7ebDeprecateXmlStringPrettyFormatter77081dcMerge commit from forkb68fc24Bump github/codeql-action from 4.31.9 to 4.31.10 in the github-actions group ...0cf5bb6Bumpkotlin.versionfrom 2.1.0 to 2.2.21d393ef1Abort tests when symbolic links cannot be created (#3788)2212433Add IntelliJ custom inspection for test class names5717d02Update JetBrains icona8ec20bAdd icon for JetBrains productsc05fb3dBump Maven to 3.9.12 and Wrapper to 3.3.4Updates
org.jetbrains.intellij.platformfrom 2.1.0 to 2.18.1