REL-4630 Release SQS 2025.1.8

[jimil09]

---

Summary by Gitar

• Version bump:
  • Update SonarQube version to 2025.1.8 in github_env.yaml and throughout commercial-editions Dockerfiles.
• Configuration updates:
  • Synchronize example-compose-files with the new version by updating Dockerfile-app, Dockerfile-search, and README.md.

_{This will update automatically on new commits.}

[sonarqube-next]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0 Dependency risks
No data about Coverage
0.0% Duplication on New Code

See analysis details on SonarQube

[gitar-bot]

CI failed: The PR release automation failed due to a SAML identity provider configuration conflict within the GitHub organization, unrelated to the code changes.

Overview

All analyzed CI logs (3/3) show a consistent failure in the gh-action-lt-backlog automation process triggered during the PR workflow. The failure is caused by an organization-level SAML restriction and does not stem from the actual release changes.

Failures

SAML Identity Provider Configuration Conflict (confidence: high)

• Type: tooling
• Affected jobs: 78108753690, 78109535470
• Related to change: no
• Root cause: The GitHub action is encountering a policy restriction: "The Organization's SAML identity provider is disabled when an Enterprise SAML identity provider is available." The service account/token used by the automation is not correctly authorized or configured to operate under the current Enterprise SAML enforcement.
• Suggested fix: Repository administrators should verify if the service account used by the gh-action-lt-backlog requires updated permissions or if the action's internal authentication handling needs adjustment for Enterprise SAML environments. Since this is an environmental configuration issue, it can be bypassed if necessary by manual intervention for the release task.

Summary

• Change-related failures: 0
• Infrastructure/flaky failures: 1 (Tooling failure caused by Organization-wide SAML configuration)
• Recommended action: This failure is external to the PR contents. The author should contact the DevOps/Infrastructure team to resolve the SAML authorization issue for the release automation account. Once the underlying infrastructure issue is resolved, the CI job should be retried.

Code Review ✅ Approved

Bumps the SonarQube version to 2025.1.8 across all Dockerfiles and example configurations. No issues found.

Tip

Comment Gitar fix CI or enable auto-apply: gitar auto-apply:on

Options

Auto-apply is off → Gitar will not commit updates to this branch.
Display: compact → Showing less information.

Comment with these commands to change:

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

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

[matteo-mara-sonarsource]

LGTM validate that the version 2025.1.8.123366 is the one used and that the 2025.1.7 occurrences have been moved to 2025.1.8.