GHA-191 Add bump version functionality to automated release workflow

[nils-werner-sonarsource]

• Introduced inputs for version bumping, including options for PR labels and exclusions.
• Updated workflow to conditionally bump the version and create a PR based on user input.
• Enhanced documentation to reflect new version bumping capabilities.

Proof-of-concept

• Action run: https://github.com/SonarSource/sonar-pli/actions/runs/22303444723
• Bump version PR: https://github.com/SonarSource/sonar-pli/pull/288

[hashicorp-vault-sonar-prod]

GHA-191

[sonarqubecloud]

SonarQube reviewer guide

Summary: Refactor version bumping from a separate workflow into the main automated-release workflow with optional toggle and label support.

Review Focus:

• The version bump logic moved from bump-versions.yaml (removed) to a conditional job within automated-release.yml. Verify the new bump-version job correctly passes inputs (bump-version-pr-lables, bump-version-exlusions) to the reusable action.
• Check for typos in input names: bump-version-pr-lables (should be labels?) and bump-version-exlusions (should be exclusions?).
• Ensure Step 1c's file extension detection logic is properly implemented in the skill execution.

Start review at: .claude/skills/automated-release-setup/SKILL.md. This is the primary documentation file that defines the setup process; it clarifies the architectural change from two separate workflows to one conditional workflow, and confirms the extension detection mechanism is documented correctly.

💬 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