RUST-142 update gh-action_release to v7

[erwan-serandour]

No description provided.

[sonar-review-alpha]

Summary

Updates the gh-action_release action from v6 to v7 and changes the release workflow from automatic to manual-only.

Key changes:

• Removed the automatic on: release: types: [published] trigger — releases no longer happen automatically when a GitHub release is created
• Kept workflow_dispatch (manual trigger) but simplified inputs by removing the releaseId parameter
• Simplified the version input description and removed fallback logic that relied on release event data
• Updated the action reference from v6 to v7

Impact: This workflow is now entirely manual — releases must be triggered via the Actions tab rather than automatically on release publication.

What reviewers should know

Start here: Review the removed release trigger first to understand the shift from event-driven to manual releases. Then check the input changes (especially the removal of releaseId and the new version format requirement of "full version including build number").

Non-obvious point: The v7 action appears to have a simplified API that no longer requires a separate release ID, and the workflow now depends entirely on manual execution rather than GitHub's release event. Verify with your release process documentation that manual-only releases are the intended new behavior.

---

• Generate Walkthrough
• Generate Diagram

🗣️ Give feedback

[hashicorp-vault-sonar-prod]

RUST-142

[sonarqube-next]

Quality Gate passed for 'sonar-rust'

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

[saberduck]

@erwan-serandour is this ready?

[sonar-review-alpha]

Clean, focused change — but there's one important question to resolve before approving: the removal of the automatic release: types: [published] trigger means the release pipeline is no longer end-to-end automated. Previously, automated-release.yml would create a GitHub release and that publication event would automatically kick off release.yml. Now someone must manually navigate to the Actions tab and trigger release.yml after the automated release completes. If this is intentional (e.g., v7 of gh-action_release is designed to be triggered differently, or the team wants an explicit human gate), it's fine — but it should be confirmed, and the team's runbook / release documentation should be updated to reflect the new manual step.

🗣️ Give feedback

[sonar-review-alpha]

The removal of the release: types: [published] trigger converts the release pipeline from fully automated to semi-manual. Previously, automated-release.yml created a GitHub release → that publication event fired this workflow automatically. Now a human must go to the Actions tab and run this workflow after the automated release completes.

Before merging, please confirm:

• Is this intentional? (e.g., v7 of gh-action_release provides its own trigger mechanism, or the team wants an explicit gate?)
• Has the release runbook / CONTRIBUTING docs been updated to document the new manual step?
• Are there any internal automation tools (e.g. Jira release automations, internal bots) that relied on this workflow firing automatically on release publication that would now silently break?