Skip to content

feat: add /release skill for guided releases#843

Closed
mangelajo wants to merge 3 commits into
mainfrom
add-release-skill
Closed

feat: add /release skill for guided releases#843
mangelajo wants to merge 3 commits into
mainfrom
add-release-skill

Conversation

@mangelajo

Copy link
Copy Markdown
Member

Summary

  • Adds a /release Claude Code skill that interactively guides through the full Jumpstarter release process: creating release branches, tagging releases (RC and final), and contributing operator bundles to community-operators
  • Enforces correct ordering (images must exist before bundle generation), RC-first policy for new branches, and vX.Y.Z-rc.N tag naming convention
  • Fixes operator release docs by removing the incorrect e2e_test.go update step (defaultControllerImage uses :latest, not a pinned version)

Test plan

  • Run /release and verify it asks the right initial questions based on git state
  • Dry-run each scenario: new branch, RC tag, final tag, operator bundle
  • Verify the RC-first guardrail prevents tagging a final without prior RCs

🤖 Generated with Claude Code

Add an interactive release skill that guides through the full
Jumpstarter release process: creating release branches, tagging
releases (RC and final), and contributing operator bundles to
community-operators. The skill enforces correct ordering, RC-first
policy, and tag naming conventions.

Also removes the incorrect e2e_test.go update step from the operator
release docs since defaultControllerImage uses :latest.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
@coderabbitai

coderabbitai Bot commented Jun 26, 2026

Copy link
Copy Markdown
Contributor

Review Change Stack

Warning

Review limit reached

@mangelajo, we couldn't start this review because you've reached your PR review rate limit.

More reviews will be available in 55 minutes and 45 seconds. Learn how PR review limits work.

Your organization has used up its prepaid credits, and credit purchases are no longer available. Enable the review add-on in the billing tab to keep reviews running — you're only billed for reviews past your plan's rate limits ($0.25/file).

⌛ How to resolve this issue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based credits.

🚦 How do rate limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please see our Fair Usage Limits Policy for further information.

ℹ️ Review info
⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 39260953-2c28-47d9-bbee-d45e394ab0d2

📥 Commits

Reviewing files that changed from the base of the PR and between 26aee22 and ad7e777.

📒 Files selected for processing (2)
  • .claude/skills/release/SKILL.md
  • .cursor/rules/releasing-operator.mdc
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch add-release-skill

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

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

mangelajo and others added 2 commits June 26, 2026 15:14
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
The release skill now finds the CI run triggered by the tag push and
monitors it periodically, then automatically proceeds to the operator
bundle step when images are ready.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
@mangelajo

Copy link
Copy Markdown
Member Author

Note: Once #844 lands (operator auto-detects its version for controller/router image defaults), the jumpstarter_types.go update step in this skill (Phase 1, step 1 of "Tag a release") can be removed — the kubebuilder defaults will stay at :latest permanently and the operator will resolve them to its own version tag at runtime.

@mangelajo

Copy link
Copy Markdown
Member Author

Superseded by updated PR with improvements from the v0.9.0-rc.1 release.

@mangelajo mangelajo closed this Jun 26, 2026
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.

1 participant