GHA-210 Send release summary to the Slack channel.

[tomasz-tylenda-sonarsource]

In order to avoid problems with Docker, we create a reusable action slack-message to send a markdown messages.

Test run: https://github.com/SonarSource/sonar-ruby/actions/runs/23011828945 (Slack: #squad-jvm-releases)
Test on private runner: https://github.com/SonarSource/sonar-apex/actions/runs/23052390757

[hashicorp-vault-sonar-prod]

GHA-210

[nils-werner-sonarsource]

Please see my comments

[nils-werner-sonarsource]

LGTM!

[sonarqubecloud]

SonarQube reviewer guide

Summary: Refactor release workflow summary job to support multi-project releases and add Slack notifications via a new reusable action.

Review Focus:

• The message generation logic is now extracted into a separate step and output as a variable, enabling reuse across multiple notification channels. Verify the bash script correctly handles all result variables, particularly the newly added RESULT_BUMP_VERSION.
• The hardcoded Jira URL fallback was removed; ensure inputs.release-process is always provided or the workflow handles empty values gracefully.
• The new slack-message action uses external dependencies (slackify-markdown-action, slack-github-action). Verify version pinning and credential handling via vault-action-wrapper.

Start review at: .github/workflows/automated-release.yml. This is the core change where the refactored logic centralizes message generation, adds project name support, includes dry-run indication, and conditionally posts to Slack—all critical to understanding the release workflow's new behavior.

💬 Please send your feedback

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud