Update Gradle dependencies to v11#1679
Conversation
SummaryThis PR updates the SonarLint Core libraries from v10.34.1 to v11.3.0 via a single-line change to the Gradle version catalog ( What reviewers should knowKey areas to review:
Nothing to worry about:
|
There was a problem hiding this comment.
The change is a single version bump in the version catalog — no production code is touched. All three upgraded libraries (sonarlint-core, sonarlint-rpc-java-client, sonarlint-rpc-impl) are declared exclusively in integrationTestImplementation scope in its/plugin/build.gradle.kts, so there is no runtime risk to the plugin itself.
The only real risk is integration test compilation. The IT tests bind tightly to the SonarLint RPC API through positional constructors with many arguments and a full SonarLintRpcClientDelegate interface implementation. If v11 added or removed parameters anywhere in that surface area, the tests will fail to compile. There are no companion source changes in this PR to adapt to any such API evolution. Reviewers should confirm the CI build (specifically the integration test compilation step) passes cleanly before merging.
| sonarqube = "26.2.0.118776" | ||
| sonar-orchestrator = "6.1.0.3962" | ||
| sonarlint = "10.34.1.83453" | ||
| sonarlint = "11.1.0.85284" |
There was a problem hiding this comment.
MockSonarLintRpcClientDelegate implements SonarLintRpcClientDelegate with ~25 @Override methods, and SonarLintUtils.featureFlagsForStandaloneMode() constructs FeatureFlagsDto with 11 positional boolean arguments. Both are brittle against interface changes and constructor-signature changes between major versions.
This PR contains no corresponding source edits, so if v11 added or removed any abstract methods or constructor parameters, the integration tests will fail to compile. Confirm that the IT test compilation step is green in CI before merging.
- Mark as noise
b15956b to
a9d038b
Compare
a9d038b to
9391387
Compare
|
| sonarqube = "26.2.0.118776" | ||
| sonar-orchestrator = "6.1.0.3962" | ||
| sonarlint = "10.34.1.83453" | ||
| sonarlint = "11.2.0.85396" |
There was a problem hiding this comment.
The its/plugin/gradle.lockfile still pins all SonarLint transitive dependencies (sonarlint-core, sonarlint-rpc-impl, sonarlint-rpc-java-client, and 10 others) to 10.34.1.83453. With resolutionStrategy.activateDependencyLocking() active, Gradle will reject the new version at dependency resolution and the build will fail before even reaching compilation.
Run ./gradlew --write-locks (across all affected subprojects, at minimum :its:plugin) to regenerate the lock files against 11.2.0.85396.
- Mark as noise
9391387 to
5583411
Compare
5583411 to
1d70ded
Compare
1d70ded to
ea6af69
Compare
There was a problem hiding this comment.
Both previously flagged issues remain unresolved and the PR is not yet ready to merge.
One additional observation: the PR description lists the target version as 11.2.2.85453, but the actual diff bumps sonarlint to 11.3.0.85510. This is likely because Renovate rebased to a newer release after the PR description was generated — not a bug in the change itself, but worth confirming the intended target version.
|





This PR contains the following updates:
10.34.1.83453→11.3.0.8551010.34.1.83453→11.3.0.8551010.34.1.83453→11.3.0.85510Configuration
📅 Schedule: (in timezone CET)
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about these updates again.
This PR was generated by Mend Renovate. View the repository job log.