GHA-291 Delete cloud-security-automated-release.yml

[jonas-wielage-sonarsource]

All workflows dependent on it migrated away from it to the generic automated-release.yml workflow

Part of

[hashicorp-vault-sonar-prod]

GHA-291

[sonar-review-alpha]

Summary

This PR removes the cloud-security-specific cloud-security-automated-release.yml workflow (427 lines). The workflow was a reusable GitHub Actions workflow that handled the complete release orchestration for cloud security projects, including branch freezing, Jira integration, GitHub release creation, analyzer updates, and notification reporting.

All callers of this workflow have already been migrated to use the generic automated-release.yml workflow instead, making this specialized version redundant.

What reviewers should know

Verification before merge:

• Confirm that all repositories that previously called cloud-security-automated-release.yml have been successfully migrated to automated-release.yml (this may have been done in separate PRs/repos)
• Check that no remaining references to this workflow exist in this repo using workflow search tools

What was in this workflow:
The deleted workflow orchestrated a multi-step release process: branch freezing, pre-release validation, version preparation, Jira ticket creation, GitHub release publishing, Jira version release, integration ticket creation (for SLVS, SLVSCODE, SLE, SLI, SC, SONAR), and analyzer updates for SQS/SQC products. If reviewing the generic replacement workflow, ensure it covers all this functionality.

Safe to delete:
This is purely a cleanup/consolidation. The file can be easily restored from git history if needed.

---

• Generate Walkthrough
• Generate Diagram

🗣️ Give feedback

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues
0 New dependency risks

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

See analysis details on SonarQube Cloud

[sonar-review-alpha]

LGTM! ✅

Clean deletion with no loose ends. No remaining references to cloud-security-automated-release.yml exist anywhere in the repo — no docs, no other workflow files, no test CI workflow was left behind.

automated-release.yml is a superset of the deleted workflow: every input is covered, and the cloud-security-specific hardcoded Slack channel (squad-security-cloud-notifs) is now properly parameterised via the generic slack-channel input, which is strictly better.

🗣️ Give feedback

[jonas-wielage-sonarsource]

@nils-werner-sonarsource Requesting review mainly for awareness

[nils-werner-sonarsource]

Thanks for the migration effort!