ci: block releases with open release blockers

[dkropachev]

Summary

• block production releases when an open issue has the release-blocker label
• report blocking issue title and URL
• keep dry-run releases available
• grant the workflow token read-only issue access

Branch coverage

• this PR guards scylla-4.x
• ci: block releases with open release blockers #1078 guards active scylla-3.x

Validation

• actionlint 1.7.12
• guard succeeds when no blocker exists
• guard fails when an open blocker exists
• API failures fail closed

[qodo-scylladb]

Code Review by Qodo

🐞 Bugs (0) 📘 Rule violations (0) 📎 Requirement gaps (0)

Great, no issues found!

Qodo reviewed your code and found no material issues that require review

Tip of the day

💡 Did you know, you can turn these tips off under Display preferences

More tips ↗ | Customize Qodo ↗ | Qodo docs ↗

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: QUIET

Plan: Advanced

Run ID: 0823505d-b4b0-4982-bb7f-2f751185c485

📥 Commits

Reviewing files that changed from the base of the PR and between 76ef5e4 and 74a0070.

📒 Files selected for processing (1)

• .github/workflows/release.yml

Included review availability: Your plan provides up to 1 included review per hour; 0 remain after this review.

---

📝 Walkthrough

Walkthrough

The release job now grants issues: read permission. For non-dry-run releases, it checks open release-blocker issues before checkout and after release-prepare. Either check fails the workflow when a blocker exists.

Merge Risk: ⚪ Minimal · up to 74a00

Non-dry-run production releases are now blocked by open release-blocker issues while dry runs remain unaffected. The change is ready to merge.

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description check	✅ Passed	The description directly covers the release-blocker gate, dry-run behavior, permissions, branch coverage, and validation.
Title check	✅ Passed	The title clearly and concisely describes the main change: blocking releases when open release-blocker issues exist.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0…
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[Copilot]

🟢 Approval recommended

The workflow correctly fails closed for production releases while leaving dry-run behavior unchanged.

Pull request overview

Adds release-blocker enforcement to production releases while preserving dry runs.

Changes:

• Grants read-only issue access.
• Checks for blockers before preparation and immediately before release.
• Reports the blocking issue’s title and URL.

File summaries

File	Description
.github/workflows/release.yml	Adds production release-blocker guards.

Review details

• Files reviewed: 1/1 changed files
• Comments generated: 0
• Review effort level: Balanced

---

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.