RUST-132 Normalize Cargo version in bump workflow

[sebastien-marichal]

Epic: SKUNK-1662

Initial Prompt

This is failing because the version does not contains the PATCH number.
Can you update the job so it handle adding the patch when not present when updating Cargo.toml file?

Summary

Normalize the Cargo manifest version in the bump workflow when the release pipeline provides only a major/minor version.

Changes

• append .0 before updating analyzer/Cargo.toml when the incoming version matches major.minor
• emit a GitHub Actions notice when the workflow normalizes the Cargo version

[hashicorp-vault-sonar-prod]

RUST-132

[sonar-review-alpha]

Summary

Handles missing PATCH component in Cargo version string. The release pipeline sometimes provides only major.minor versions (e.g., '1.2'), but Cargo.toml requires semantic versioning with all three components. This change detects the two-component pattern and appends '.0' before updating the manifest, with a GitHub Actions notice to track when normalization occurs.

What reviewers should know

The only change is in .github/workflows/bump-version.yml (lines 46-52). The regex ^[0-9]+\.[0-9]+$ correctly matches exactly two numeric components and will skip normalization if the version already has a patch component. Verify that the notice message provides adequate visibility for the release team. The change does not affect versions already in major.minor.patch format, so existing releases remain unaffected.

---

• Generate Walkthrough
• Generate Diagram

🗣️ Give feedback

[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