Skip to content

GHA-174 Add releasability check to automated release workflow#83

Merged
nils-werner-sonarsource merged 1 commit intomasterfrom
nw/add-releasability-check
Feb 5, 2026
Merged

GHA-174 Add releasability check to automated release workflow#83
nils-werner-sonarsource merged 1 commit intomasterfrom
nw/add-releasability-check

Conversation

@nils-werner-sonarsource
Copy link
Contributor

@nils-werner-sonarsource nils-werner-sonarsource commented Feb 4, 2026

This pull request introduces a major enhancement to the automated release workflow by adding an explicit releasability check step. The workflow now verifies the branch's releasability status immediately after freezing it, allowing the process to fail early if the branch is not ready for release. This prevents unnecessary work (like creating Jira release tickets) when a release cannot proceed. The PR also improves documentation and output handling for related actions.

Tested workflow change: https://github.com/SonarSource/sonar-rpg/actions/runs/21690746539

@hashicorp-vault-sonar-prod hashicorp-vault-sonar-prod bot changed the title Add releasability check to automated release workflow GHA-174 Add releasability check to automated release workflow Feb 4, 2026
@hashicorp-vault-sonar-prod
Copy link

hashicorp-vault-sonar-prod bot commented Feb 4, 2026

GHA-174

- Add check-releasability job that runs after freeze-branch
- Use gh-action_releasability@v3 to verify release readiness
- Display failed checks in job summary when verbose mode is enabled
- Remove with-optional-releasability-checks input (no longer needed)
- Update documentation for the new releasability check behavior

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
@sonarqubecloud
Copy link

sonarqubecloud bot commented Feb 4, 2026

SonarQube reviewer guide

Review in SonarQube

Summary: Add releasability status checking to the automated release workflow to validate branch readiness before proceeding with release operations.

Review Focus:

  • The new check-releasability job executes early in the workflow pipeline to fail fast if the branch isn't releasable, preventing unnecessary downstream work.
  • Conditional logic in prepare-release and release-results jobs must correctly handle both success and skipped states for the new job.
  • The check-releasability-status action now exports outputs; verify the output naming and format align with how they're consumed in dependent jobs.

Start review at: .github/workflows/automated-release.yml. This is the core orchestration file where the new job is integrated into the workflow DAG. Pay close attention to job dependencies, conditional execution logic (the if statements), and how outputs flow between check-releasability, prepare-release, and release-results jobs to ensure the workflow logic is sound.

💬 Please send your feedback

Quality Gate Passed 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

@nils-werner-sonarsource nils-werner-sonarsource merged commit 123a106 into master Feb 5, 2026
6 checks passed
@nils-werner-sonarsource nils-werner-sonarsource deleted the nw/add-releasability-check branch February 5, 2026 10:27
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants