Repository navigation
BUILD-13176: Move the release workflow to gh-action_release v7 - #143
sonar-platform-bot[bot] wants to merge 1 commit into
Conversation
v7 always resolves to the latest 7.x, which keeps the draft-first release flow that complies with GitHub release immutability, with the later improvements of the action. A dryRun input is added to validate a change without releasing. Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
|
gitar review |
|
Code Review ✅ Approved🟡 Medium risk Moves the release workflow to Verification Rules 3/3 metFunctional validation No results Rules 3 passed
Auto-approval Not enabledFor more verification details, comment OptionsAuto-apply is off → Gitar will not commit updates to this branch. Comment with these commands to change the behavior for this request:
Was this helpful? React with 👍 / 👎 | Gitar |





BUILD-13176 Move the release workflow to
gh-action_releasev7.EngXP squad is moving the repositories that do not publish to Maven Central to the latest
gh-action_releasev7, as announced on Discuss. The upgrade is recommended, not required.v7 keeps the release as a draft until every publication step succeeds, which complies with GitHub release immutability, and receives the later improvements of the action.
Changes
release.yml:gh-action_releasemoves from the7.4.0tag to@v7, which always resolves to the latest 7.x. Thequality-corelang-squadRenovate preset disables Renovate on SonarSource actions and expects the branch ref, so there is no Renovate update to wait for.dryRuninput is added and passed to the action, to validate a change without releasing.Questions
Ask in #ask-platform-eng-xp, or request an update of this pull request there.
Test plan
gh workflow run release.yml --ref chore/jcarsique/BUILD-13176-nodejsMavenPluginMoveReleaseToV7 -f version=24.22.1.10233 -f dryRun=true, theReleasejob succeeded and the publication jobs are skipped, as in any dry run: https://github.com/SonarSource/nodejs-maven-plugin/actions/runs/40351698813.