PLUGINAPI-223 Update SonarSource/sonar-plugin-api monorepo to v14

[hashicorp-vault-sonar-prod]

This PR contains the following updates:

Package	Change	Age	Confidence
org.sonarsource.api.plugin:sonar-plugin-api-test-fixtures (source)	13.11.0.4459 → 14.0.0.4498
org.sonarsource.api.plugin:sonar-plugin-api (source)	13.11.0.4459 → 14.0.0.4498

---

Release Notes

SonarSource/sonar-plugin-api (org.sonarsource.api.plugin:sonar-plugin-api-test-fixtures)

v14.0.0.4498

Compare Source

What's Changed

• PLUGINAPI-175 Upgrade logback and slf4j versions by @​henryju in #​316
• PLUGINAPI-219 Update target Java version to 17 and upgrade JUnit to 6.x by @​henryju in #​317

Full Changelog: SonarSource/sonar-plugin-api@13.11.0.4459...14.0.0.4498

---

Configuration

📅 Schedule: (in timezone CET)

• Branch creation
  • At any time (no schedule defined)
• Automerge
  • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Never, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about these updates again.

---

• If you want to rebase/retry this PR, check this box

---

This PR has been generated by Mend Renovate.

[hashicorp-vault-sonar-prod]

PLUGINAPI-223

[gitar-bot]

💡 Quality: Test classpath now mixes plugin-api 14 with scanner-engine 13

Before this PR the test classpath paired sonar-plugin-api 13.11.0.4459 with org.sonarsource.scanner.engine:plugin-api-scanner-impl / sensor-test-fixtures 13.10.0.4657 (matching major lines); after the bump the API is 14.x while its scanner-side implementation and sensor test fixtures stay on 13.x, and Gradle silently resolves the impl's own plugin-api dependency up to 14.0.0.4498. The 14.0.0 release notes list only a slf4j/logback upgrade and a Java 17 / JUnit 6 retarget, so no API removal is confirmed, but the two artifacts are no longer version-aligned and scannerEngineVersion is not in the same Renovate group, so nothing will re-align them. Bump scannerEngineVersion to a build published against plugin-api 14, or add a Renovate packageRules group so the scanner-engine artifacts move together with the plugin API.

_{Was this helpful? React with 👍 / 👎}

[gitar-bot]

Code Review 👍 Approved with suggestions 0 resolved / 1 findings

Updates SonarSource/sonar-plugin-api monorepo to v14 (slf4j/logback upgrade and Java 17/JUnit 6 retarget). Consider aligning scannerEngineVersion to a build published against plugin-api 14, or add a Renovate packageRules group so scanner-engine artifacts stay synchronized with the plugin API rather than remaining on v13.

💡 Quality: Test classpath now mixes plugin-api 14 with scanner-engine 13

📄 sonar-rust-plugin/build.gradle.kts:26-28 📄 sonar-rust-plugin/build.gradle.kts:36-38 📄 sonar-rust-plugin/gradle.lockfile:49-56

Before this PR the test classpath paired sonar-plugin-api 13.11.0.4459 with org.sonarsource.scanner.engine:plugin-api-scanner-impl / sensor-test-fixtures 13.10.0.4657 (matching major lines); after the bump the API is 14.x while its scanner-side implementation and sensor test fixtures stay on 13.x, and Gradle silently resolves the impl's own plugin-api dependency up to 14.0.0.4498. The 14.0.0 release notes list only a slf4j/logback upgrade and a Java 17 / JUnit 6 retarget, so no API removal is confirmed, but the two artifacts are no longer version-aligned and scannerEngineVersion is not in the same Renovate group, so nothing will re-align them. Bump scannerEngineVersion to a build published against plugin-api 14, or add a Renovate packageRules group so the scanner-engine artifacts move together with the plugin API.

🤖 Prompt for agents

Code Review: Updates SonarSource/sonar-plugin-api monorepo to v14 (slf4j/logback upgrade and Java 17/JUnit 6 retarget). Consider aligning `scannerEngineVersion` to a build published against plugin-api 14, or add a Renovate `packageRules` group so scanner-engine artifacts stay synchronized with the plugin API rather than remaining on v13.

1. 💡 Quality: Test classpath now mixes plugin-api 14 with scanner-engine 13
   Files: sonar-rust-plugin/build.gradle.kts:26-28, sonar-rust-plugin/build.gradle.kts:36-38, sonar-rust-plugin/gradle.lockfile:49-56

   Before this PR the test classpath paired `sonar-plugin-api` 13.11.0.4459 with `org.sonarsource.scanner.engine:plugin-api-scanner-impl` / `sensor-test-fixtures` 13.10.0.4657 (matching major lines); after the bump the API is 14.x while its scanner-side implementation and sensor test fixtures stay on 13.x, and Gradle silently resolves the impl's own plugin-api dependency up to 14.0.0.4498. The 14.0.0 release notes list only a slf4j/logback upgrade and a Java 17 / JUnit 6 retarget, so no API removal is confirmed, but the two artifacts are no longer version-aligned and `scannerEngineVersion` is not in the same Renovate group, so nothing will re-align them. Bump `scannerEngineVersion` to a build published against plugin-api 14, or add a Renovate `packageRules` group so the scanner-engine artifacts move together with the plugin API.

Options

Auto-apply is off → Gitar will not commit updates to this branch.
Display: compact → Showing less information.

Comment with these commands to change the behavior for this request:

Auto-apply	Compact
gitar auto-apply:on	gitar display:verbose

_{Was this helpful? React with 👍 / 👎 | Gitar}

[sonarqube-next]

Quality Gate passed for 'sonar-rust'

Issues
0 New issues
0 Fixed issues
0 Accepted issues

Measures
0 Security Hotspots
0 Dependency risks
No data about Coverage
0.0% Duplication on New Code

See analysis details on SonarQube

[vdiez]

Auto-approved: Renovate dependency update.