SKIP UPGRADE CHECK Update IB Updates
This MR contains the following updates:
| Package | Update | Change |
|---|---|---|
| gluon | patch |
0.9.3 -> 0.9.7
|
| ironbank/sonarsource/sonarqube/sonarqube-community-build (source) | minor |
25.10.0.114319-community -> 25.11.0.114957-community
|
| registry1.dso.mil/ironbank/opensource/postgres/postgresql (source) | major |
16.2 -> 18.1
|
| registry1.dso.mil/ironbank/redhat/ubi/ubi9 (source) | minor |
9.6 -> 9.7
|
| registry1.dso.mil/ironbank/sonarsource/sonarqube/sonarqube-community-build (source) | minor |
25.10.0.114319-community -> 25.11.0.114957-community
|
| registry1.dso.mil/ironbank/sonarsource/sonarqube/sonarqube-community-build (source) | minor |
25.8.0.112029-community -> 25.11.0.114957-community
|
Complete MR checklist
Assignee
-
Followed upgrade instructions outlined in docs/DEVELOPMENT_MAINTENANCE.md -
Update Docs with new/updated steps as needed -
Tested and Validated Changes made with supporting info like logs or screenshots from test pipelines
Add supporting info below
Reviewer only
-
Tested and Validated changes
Configuration
-
If you want to rebase/retry this MR, check this box
This MR was automatically generated by Renovate Bot.
Linked Issues:
Upgrade Notices
Breaking Changes
This release includes major postgresql version change in Sonarqube Helm chart. Due to these changes in postgersql version, this can cause the helm upgrade command to fail. If you are using the not recommended way of the database provided with the Sonarqube helm chart you will need to dump database , reinstall the Sonarqube helm chart with the new postgresql version and then restore the database. The recommended approach for production is always to use an external database for Sonarqube.




