feat(ci): add support rc releases#236
Conversation
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: ASSERTIVE Plan: Enterprise Run ID: 📒 Files selected for processing (2)
📝 WalkthroughWalkthroughThis PR extends the GitHub release workflow to support release candidate (RC) versions with Estimated code review effort🎯 2 (Simple) | ⏱️ ~12 minutes Possibly related PRs
Suggested reviewers
🚥 Pre-merge checks | ✅ 4✅ Passed checks (4 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@docs/release-process.md`:
- Line 108: The example chart artifact filename is inconsistent: the diff shows
chart/v0.16.0-rc1 and version: v0.16.0-rc1 but the filename example omits the
leading "v"; update the filename example to include the "v" prefix (e.g., change
skyhook-operator-0.16.0-rc1.tgz to skyhook-operator-v0.16.0-rc1.tgz) so it
matches the documented version format and the install example (--version
v0.16.0-rc1).
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Path: .coderabbit.yaml
Review profile: ASSERTIVE
Plan: Enterprise
Run ID: a6b9ae50-f639-4333-9dfe-a9020ba21be8
📒 Files selected for processing (2)
.github/workflows/release.ymldocs/release-process.md
Summary
.github/workflows/release.ymlforoperator/,agent/, andchart/tags. Tags matchingv<MAJOR>.<MINOR>.<PATCH>-rc<N>are published with
--prereleaseso they don't become "Latest" on the Releases page.vX.Y.ZandvX.Y.Z-rcNare accepted; any other suffix (-beta,-rc.1,-rc1a, etc.) fails the job with aclear error so the tag format stays predictable.
cli-release.yaml) already auto-detects prereleases viasoftprops/action-gh-release@v3, so no change there.docs/release-process.md(tag commands,Chart.yamlmirroring requirement, Helm OCI behavior,git cliff --latestscoping).Checklist
git commit -s) per the DCO.