NO-JIRA Add sqcb-26.9 version

[emma44-m]

---

Summary by Gitar

• Documentation:
  • Added 26.9.0.129388 version mapping to README.md for SonarQube Community Build.

_{This will update automatically on new commits.}

[gitar-bot]

Code Review ⚠️ Changes requested 0 resolved / 1 findings

Adds SonarQube Community Build 26.9 version mapping to the compatibility table, but the API 14 row omits the Java 11 → 17 runtime requirement—a breaking change at the major-version boundary that plugin authors need to see. Additionally, the branch is behind master and README self-contradicts (states JDK 11 while advertising API 14.0.0, which requires JDK 17). Rebase onto master to resolve the contradiction and add a note documenting the Java version requirement change.

⚠️ Quality: API 14 row omits the Java 11 -> 17 runtime requirement

📄 README.md:32-37 📄 README.md:89-93 📄 README.md:6 📄 README.md:93

This row is the first major-version boundary in the Community Build table (26.8 -> 13.8.0.4399, 26.9 -> 14.0.0.4498), and the 14.0 changelog entry on master records "Raise the minimum required Java version from 11 to 17" (release commit f7ff374, PLUGINAPI-219). The Compatibility section immediately above the table tells plugin authors "plugins should be compatible with future versions of the API within the same major version", so an author who has been compiling against 13.x gets no signal from this table that moving to the API shipped in CB 26.9 requires a Java 17 toolchain and runtime. Add a note at the major-version boundary so the matrix carries the breaking change it is documenting.

Add a note under the Community Build table flagging the Java 17 baseline introduced by API 14.0.0

| SonarQube      | Plugin API       |
|----------------|------------------|
| 26.9.0.129388  | 14.0.0.4498      |
| 26.8.0.126808  | 13.8.0.4399      |

> **Note:** Plugin API 14.0.0 raises the minimum required Java version from 11 to 17.
> Plugins compiled against API 14.x therefore require SonarQube Community Build 26.9 or later.

🤖 Prompt for agents

Code Review: Adds SonarQube Community Build 26.9 version mapping to the compatibility table, but the API 14 row omits the Java 11 → 17 runtime requirement—a breaking change at the major-version boundary that plugin authors need to see. Additionally, the branch is behind master and README self-contradicts (states JDK 11 while advertising API 14.0.0, which requires JDK 17). Rebase onto master to resolve the contradiction and add a note documenting the Java version requirement change.

1. ⚠️ Quality: API 14 row omits the Java 11 -> 17 runtime requirement
   Files: README.md:32-37, README.md:89-93, README.md:6, README.md:93

   This row is the first major-version boundary in the Community Build table (26.8 -> 13.8.0.4399, 26.9 -> 14.0.0.4498), and the 14.0 changelog entry on master records "Raise the minimum required Java version from 11 to 17" (release commit f7ff374, PLUGINAPI-219). The Compatibility section immediately above the table tells plugin authors "plugins should be compatible with future versions of the API within the same major version", so an author who has been compiling against 13.x gets no signal from this table that moving to the API shipped in CB 26.9 requires a Java 17 toolchain and runtime. Add a note at the major-version boundary so the matrix carries the breaking change it is documenting.

   Fix (Add a note under the Community Build table flagging the Java 17 baseline introduced by API 14.0.0):
   | SonarQube      | Plugin API       |
   |----------------|------------------|
   | 26.9.0.129388  | 14.0.0.4498      |
   | 26.8.0.126808  | 13.8.0.4399      |
   
   > **Note:** Plugin API 14.0.0 raises the minimum required Java version from 11 to 17.
   > Plugins compiled against API 14.x therefore require SonarQube Community Build 26.9 or later.

Options

Auto-apply is off → Gitar will not commit updates to this branch.
Display: compact → Showing less information.
Unblock → Override a blocking verdict and allow merging.

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

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

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

[sonarqube-next]

Quality Gate passed

Issues
0 New issues
0 Fixed issues
0 Accepted issues

Measures
0 Security Hotspots
0 Dependency risks
No data about Coverage
No data about Duplication

See analysis details on SonarQube

[dorian-burihabwa-sonarsource]

Hey @emma44-m , could you please add a ticket for the change? REL-4931 is probably good enough.