Skip to content

REL-4629 Release SQS 2025.4.7#907

Merged
jimil09 merged 1 commit into
release/2025.4from
jd/REL-4629-release-sqs-2025.4.7
May 27, 2026
Merged

REL-4629 Release SQS 2025.4.7#907
jimil09 merged 1 commit into
release/2025.4from
jd/REL-4629-release-sqs-2025.4.7

Conversation

@jimil09
Copy link
Copy Markdown
Contributor

@jimil09 jimil09 commented May 27, 2026


Summary by Gitar

  • Version bump:
    • Update current SonarQube version to 2025.4.7 in github_env.yaml and commercial edition Dockerfiles.
    • Update version tags in sq-dce-custom-zip-postgres Dockerfiles and README.md documentation.

This will update automatically on new commits.

Signed-off-by: Jimil Desai <jimil.desai@sonarsource.com>
@gitar-bot
Copy link
Copy Markdown

gitar-bot Bot commented May 27, 2026

CI failed: The CI build failed due to an automation tooling error where the GitHub integration could not look up SAML identities, likely due to an organization-level SAML configuration mismatch.

Overview

One failure was identified in the release automation pipeline. The job failed during the execution of a GitHub Action responsible for Jira/GitHub synchronization, specifically due to a SAML identity resolution error.

Failures

GitHub/Jira Integration SAML Identity Resolution Failure (confidence: high)

  • Type: tooling
  • Affected jobs: 78111461879
  • Related to change: no
  • Root cause: The sonarsource/gh-action-lt-backlog action is failing because the GitHub organization's SAML identity provider settings conflict with the action's current lookup logic (Enterprise SAML vs. standard SAML).
  • Suggested fix: This is an environment/configuration issue rather than a code change issue. Escalate to the DevOps or platform engineering team to review the GitHub organization's SAML configuration or the action's authentication service account permissions.

Summary

  • Change-related failures: 0
  • Infrastructure/flaky failures: 1 (Tooling integration failure)
  • Recommended action: This failure is unrelated to the PR content. Since it is a tooling/configuration issue, it should be addressed by the team managing the integration workflows rather than the PR author.
Code Review ✅ Approved

Updates SonarQube to version 2025.4.7 across environment configurations, Dockerfiles, and documentation. 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

@sonarqube-next
Copy link
Copy Markdown

Copy link
Copy Markdown
Contributor

@matteo-mara-sonarsource matteo-mara-sonarsource left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Validate that all the new build numbers are referring to 2025.4.7.123368 and that all the occurrences of 2025.4.6 have been moved to 2025.4.7.

@jimil09 jimil09 merged commit 6c3a0d7 into release/2025.4 May 27, 2026
22 of 24 checks passed
@jimil09 jimil09 deleted the jd/REL-4629-release-sqs-2025.4.7 branch May 27, 2026 15:41
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants