Which information is more accurate - Table example or Upgrade calculator

SonarQube Server / Community Build
,
1

Must-share information (formatted with Markdown):

  • 25.10.0.114319 (Community Build)
  • Helm
  • Find the correct upgrade path
  • Reading SonarQube documentation.

Do not share screenshots of logs – share the text itself (bonus points for being well-formatted)!

On link, we see the upgrade path table example, showing

From version To version Update path

25.10.0.x 26.1.0.x 25.10.0.x > 26.1.0.x (direct)

However, the Calculate Your Update Path calculator says (clicking Calculate Path)

25.10 > 25.12(December Release) > 26.4

Question:

  1. Can we upgrade from 25.10.0.x to v26.1.0.x OR must we upgrade from 25.10.0.x to v25.12 ?

  2. Which information is more accurate ? Table example or Upgrade calculator ?

Thanks

2

Hi,

It looks like we didn’t get the calculator updated. The docs are correct. I’ll flag this internally for the calculator. Thanks for raising this!

 
Thx,
Ann

4

Thx for responding Ann

Is the calculator correct when it says it is good to upgrade from 2025.1.4 LTA to 2026.1.2 LTA (directly) ?

6

Hi,

The table is correct. However, the table you pointed to earlier doesn’t address SonarQube Server at all. However, you can upgrade from any point release to any point release, so 2025.1.x → 2026.1.y works.

 
HTH,
Ann

7

Hi @uwpsqcb445

Why would you want to update to 26.1? it’s recommended to stay on latest community build release. If you are on 25.10.0.x you should update to currently latest 26.3.0.x with intermediate 25.12.0.x or 26.1.0.x (both are acceptable due to a bug on particular DBs in 25.12.0.x).

Indeed our table and calculator are not consistent here, but we decided to keep it that way to not complicate calculator.

9

I’d go with the upgrade path documented for the specific SonarQube versions you’re running rather than relying on the calculator alone. If the table and calculator are showing different paths, it’s worth checking the release-specific upgrade notes as well, since version requirements can change between releases. The calculator may be applying additional upgrade rules that aren’t obvious from the example.