SONARJAVA-6239 Automated release 8.22

[leonardo-pilastri-sonarsource]

No description provided.

[hashicorp-vault-sonar-prod]

SONARJAVA-6239

[sonar-review-alpha]

Summary

This PR consolidates release and automation workflows to use centralized SonarSource reusable actions, replacing custom implementations with shared, maintained workflows.

Key changes:

• PrepareNextIteration.yml refactored to use SonarSource/release-github-actions/create-pull-request action. Input renamed from nextVersion to version with automatic normalization (X.Y → X.Y.0-SNAPSHOT).
• UpdateRuleMetadata.yml simplified to use SonarSource/release-github-actions/update-rule-metadata action, removing JFrog setup, Java configuration, and manual rule-api jar handling.
• automated-release.yml added as new comprehensive release workflow (delegates to reusable action) supporting dry-run, multiple integrations (IDE/SQC/SQS), and automated version bumping.
• release.yml enhanced with workflow_dispatch trigger, now supports both GitHub release events and manual triggering with explicit version/releaseId inputs.
• slack_notify.yml deleted; Slack notifications now handled by centralized reusable actions.
• Slack channel updated from squad-jvm-notifs to squad-jvm-releases.

What reviewers should know

Where to focus:

1. Reusable action dependencies: This PR introduces critical dependencies on SonarSource/release-github-actions (v1). These handle complex release logic—verify this external action is properly reviewed and maintained, and check permissions granted to it.

2. PrepareNextIteration.yml: Version normalization logic (lines 10-14) converts short version formats. Verify this matches expected behavior for your release process.

3. Slack notifications: The slack_notify.yml workflow is fully removed. Confirm that notifications are now emitted by the reusable actions and routed to the correct channel.

4. automated-release.yml: This is a new entrypoint for releases. It orchestrates IDE, SQC, and SQS integrations plus Jira interactions. Verify the inputs align with your release checklist and that the pm-email address is correct.

5. release.yml fallback logic (lines 35-37): The new inputs || github.event.release.* pattern handles both release and dispatch triggers—check that fallback values make sense for release event scenarios.

Testing tip: The new automated-release.yml defaults to dry-run: true and uses Jira sandbox—confirm this is safe for local testing.

---

• Generate Walkthrough
• Generate Diagram

🗣️ Give feedback

[sonarqube-next]

Quality Gate passed

Issues
0 New issues
0 Fixed 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

[sonar-review-alpha]

LGTM! ✅

Clean workflow modernization — no bugs found. The PR consistently delegates to SonarSource/release-github-actions reusable actions, removing duplicated git/gh/JFrog plumbing that was previously maintained locally.

🗣️ Give feedback

[github-actions]

This PR is stale because it has been open 7 days with no activity. If there is no activity in the next 7 days it will be closed automatically