Renovate Sonarqube-Server

SonarQube Server / Community Build
1

Hi everyone,

We have just successfully upgraded our SonarQube Server to the latest 2026.1-LTA version. Our instance is deployed using the official Helm Chart on a Kubernetes cluster.

Now that we are on the LTA branch, we are considering automating our patch management using Renovate. I would like to get some advice or best practices from the community regarding this.

Our Goal: We want Renovate to automatically create and merge Merge Requests for patch updates (e.g., 2026.1.1, 2026.1.2, etc.) of the SonarQube Helm Chart and the underlying Docker image.

Our Environment:

  • SonarQube Version: 2026.1-LTA

  • Deployment: Helm Chart on K8s

  • Database: External AWS RDS PostgreSQL 17.7

  • Automation: Renovate for dependency updates

Specific Question

Is it guaranteed that patch releases (2026.1.x) within the LTA cycle never require a manual database migration via the /setup endpoint?

I want to make our maintenance as “hands-off” as possible while remaining on the stable LTA path. Any experiences or “lessons learned” from similar setups would be greatly appreciated!

Thanks in advance!

Best regards, Maximilian Berthold

2

Hi Maximilian,

Welcome to the community!

No. It is highly, highly unlikely, but I think there was one time we had to do a migration as part of fixing a bug. I think you’re probably safe doing the automation, but you should leave yourself an escape hatch to manually run a migration in the 0.5% case.

 
HTH,
Ann

1 Like
3

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.