fix: lower Sonar Plugin API baseline to 11.1.0.2693 for broader compa…#20
Merged
Merged
Conversation
…tibility The plugin was compiled against Sonar Plugin API 13.5.0.4319, so its manifest required SonarQube to provide API >= 13.5. This prevented it from loading on SonarQube Server 2025.1.x LTA (Plugin API 11.x), e.g. Enterprise Edition 2025.1.3. Lower the API baseline to 11.1.0.2693 (the 2025.1.0 LTA baseline) so the plugin loads on the whole 2025.1.x LTA line as well as newer Community Build releases (e.g. 25.9, Plugin API 13.x). Align the test-scoped sonar-plugin-api-impl to 25.2.0.102705 to match. Bump version to 2.0.1. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
|
SebastianDT1
approved these changes
Jun 9, 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
2 participants
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.
Pull request type
Please check the type of change your PR introduces:
What is the current behavior?
The plugin is compiled against Sonar Plugin API
13.5.0.4319, so the JAR manifest requires the SonarQube server to provide API >= 13.5. On servers running an older API, the plugin is rejected at startup:
Plugin AsyncAPI Custom [asyncapicustom] requires at least Sonar Plugin API version 13.5.0.4319 (current: 13.0.0.3026) This prevents the plugin from loading on SonarQube Server 2025.1.x LTA (Plugin API 11.x), e.g. Enterprise Edition 2025.1.3.
Issue Number: N/A
What is the new behavior?
13.5.0.4319to11.1.0.2693(the 2025.1.0 LTA baseline), so the plugin loads on the whole 2025.1.x LTA line (Plugin API 11.x) and also on newer Community Builds (25.8/25.9, Plugin API 13.x) thanks to backward compatibility.sonar-plugin-api-impl(test scope) to25.2.0.102705, the Community Build that pairs with API 11.1, so the test harness matches the new baseline.2.0.0→2.0.1across all modules and adds the CHANGELOG entry.Other information
Verification performed:
mvn clean test→ BUILD SUCCESS, all tests pass.Sonar-Version: 11.1.0.2693.sonar-analyzer-commons(shaded) verified working on API 11.x in the tests.sonar-plugin-apiresolves uniquely to11.1.0.2693.Compatibility rule applied: plugin's required API ≤ API provided by the server. Building against the oldest API that still compiles maximizes compatibility without losing functionality (the plugin did not use anything newer than 11.1).