BUILD-10483 update release instructions

[julien-carsique-sonarsource]

Update the release instructions:

• new Slack channel: #ask-github-migration -> #ops-platform-releases
• add a reference to the Communicate Updates, Changes and Migrations xtranet page
• changed Improvements icon that was the same as the title: 🚀 -> ⚡

[hashicorp-vault-sonar-prod]

BUILD-10483

[Copilot]

Pull request overview

This PR updates the release instructions in the README to provide more comprehensive guidance on the release process for the ci-github-actions repository. The changes clarify semantic versioning practices, add a pre-release validation step, update communication channels, and expand the release announcement template.

Changes:

• Added pre-release validation requirements (dogfooding status check)
• Enhanced semantic versioning guidelines with clearer categorization of changes
• Updated Slack channel from #ask-github-migration to #ops-platform-releases
• Added reference to xtranet documentation for major updates requiring user action

Comments suppressed due to low confidence (1)

README.md:1578

• Grammar issue: "following as indicated in" is awkward. Consider rephrasing to "as indicated in" (remove "following") for better readability.

    Communicate major updates, changes and migrations that require action from users following as indicated in

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[sonarqubecloud]

SonarQube reviewer guide

Summary: Updates release process documentation to clarify semantic versioning principles, expand patch version criteria, and redirect release communications to the ops-platform-releases Slack channel with additional migration notification requirements.

Review Focus: Verify that the semantic versioning guidance is accurate and complete (particularly the expanded patch version criteria now including improvements and documentation). Confirm the Slack channel change (#ask-github-migration to #ops-platform-releases) is correct and that the new migration communication requirement via xtranet is appropriate for your release workflow.

Start review at: README.md (Release section). This is the only file changed and contains process documentation that directly impacts how your team executes releases, so accuracy is critical.

💬 Please send your feedback

Quality Gate passed

Issues
0 New issues
0 Accepted issues
0 Dependency risks

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

See analysis details on SonarQube Cloud