CLI-165 Automate install scripts version update on release

[kirill-knize-sonarsource]

No description provided.

[sonar-review-alpha]

Summary

Automates the version update of install scripts during the release process. When a release is cut, the workflow now automatically extracts the new version from git tags and updates the hardcoded version strings in both user-scripts/install.sh (bash) and user-scripts/install.ps1 (PowerShell). This ensures the installation scripts always distribute the correct version without manual intervention.

What reviewers should know

Start with the two new steps added to .github/workflows/full-release.yml (the main change):

1. "Get released version" — fetches tags and extracts the latest version
2. "Update install scripts version" — uses sed to update version variables in bash and PowerShell scripts

Note: These steps run before the existing "bump-version" step. Make sure the sed patterns match the exact syntax in the install scripts (they look for version="X.Y.Z" in bash and $SonarVersion = "X.Y.Z" in PowerShell). If the install scripts use different formatting, the sed commands won't match.

---

• Generate Walkthrough
• Generate Diagram

🗣️ Give feedback

[hashicorp-vault-sonar-prod]

CLI-165

[sonar-review-alpha]

Conclusion: The install scripts version update logic has a bug in the install.sh sed pattern that will corrupt the script on every release.

🗣️ Give feedback

[damien-urruty-sonarsource]

I think it should work but there is a better way to do it IMO

[sonar-review-alpha]

Conclusion: The previous sed pattern issue remains unresolved — the fix from the prior review has not been applied.

🗣️ Give feedback

[sonar-review-alpha]

LGTM! ✅

🗣️ Give feedback

[sonarqubecloud]

SonarQube reviewer guide

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

[sonar-review-alpha]

Conclusion: Clean, focused PR. The sed patterns are correctly scoped, the RELEASED_VERSION env var is properly injected, and the modified files are committed via the existing peter-evans/create-pull-request step at the end of the bump-version job.

🗣️ Give feedback