feat: add /release skill for guided releases - #845
Conversation
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>
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>
- Remove jumpstarter_types.go update step (operator resolves image tags at runtime now) - Add AUTO_CONFIRM=1 for non-interactive make contribute - Add gh pr create commands for community-operators PRs - Add branch protection ruleset reminder for new release branches - Add gh run rerun suggestion on CI failure - Document API fallback for creating protected release branches - Add cherry-pick infrastructure fixes reminder Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (2)
✅ Files skipped from review due to trivial changes (2)
📝 WalkthroughWalkthroughAdded a release skill guide covering branch creation, version bumping, tagging, CI monitoring, bundle contribution, and post-release steps. Updated operator release rule docs to remove e2e test references from version-bump and commit guidance. ChangesRelease process guidance
Estimated code review effort: 2 (Simple) | ~10 minutes Possibly related PRs
Suggested reviewers: Poem
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
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. Comment |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 5
Caution
Some comments are outside the diff and can’t be posted inline due to platform limitations.
⚠️ Outside diff range comments (2)
.cursor/rules/releasing-operator.mdc (2)
40-52: 🗄️ Data Integrity & Integration | 🟠 Major | ⚖️ Poor tradeoffRemove stale
jumpstarter_types.goupdate instructions.This section contradicts the release skill (
.claude/skills/release/SKILL.mdline 24) which explicitly says "Do NOT modifyjumpstarter_types.go". Since the operator resolves:latestdefaults at runtime, updating kubebuilder defaults here is unnecessary and creates stale documentation. Remove this entire subsection and its code example.🤖 Prompt for 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. In @.cursor/rules/releasing-operator.mdc around lines 40 - 52, Remove the stale `jumpstarter_types.go` update subsection from the releasing operator rules document, including the kubebuilder default image tag example and the note about `make manifests`/`make bundle`. The release guidance should align with the `release` skill and avoid instructing changes to `jumpstarter_types.go`, since the operator uses runtime resolution for `:latest` defaults.
82-85: 🗄️ Data Integrity & Integration | 🟡 Minor | ⚡ Quick winRemove or update stale CRD default verification grep.
Line 83 greps for
default: quayin the CRD YAML to verify kubebuilder defaults propagated. Ifjumpstarter_types.gois no longer updated (per the skill), this verification step is stale and will confuse users. Remove this grep or replace with a check relevant to the remaining version-bump files.🤖 Prompt for 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. In @.cursor/rules/releasing-operator.mdc around lines 82 - 85, The release verification steps include a stale grep for the CRD default value that depends on kubebuilder-generated defaults, which no longer aligns with the current release workflow. Update the checks in releasing-operator.mdc by removing the `default: quay` verification tied to the CRD manifest, and replace it with a validation that matches the remaining release artifacts such as the CSV image references or release-config version bumps. Use the existing `grep` commands in the release checklist as the location to adjust.
🧹 Nitpick comments (2)
.claude/skills/release/SKILL.md (2)
28-30: 📐 Maintainability & Code Quality | 🔵 Trivial | 💤 Low valueAdd language specifier to fenced code block.
- ``` + ```text Makefile update → commit → tag push → [CI builds images] → GitHub Release → make bundle → make contribute<details> <summary>🤖 Prompt for AI Agents</summary>Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.In @.claude/skills/release/SKILL.md around lines 28 - 30, The fenced code block
in SKILL.md is missing a language specifier; update the workflow snippet to use
a text code fence. Locate the release flow example near the plain “Makefile
update → commit → tag push → [CI builds images] → GitHub Release → make bundle →
make contribute” sequence and change the surrounding fence to a labeled one so
the markdown renderer can apply proper formatting.</details> <!-- cr-comment:v1:96ec03141dbe51bf9d0fa7f4 --> _Source: Linters/SAST tools_ --- `155-166`: _📐 Maintainability & Code Quality_ | _🔵 Trivial_ | _💤 Low value_ **Clarify that `gh run watch` blocks until completion.** `gh run watch` already blocks and polls until the run completes, making the subsequent "monitor periodically" instruction redundant and confusing. Simplify to: ```diff # Watch the run until it completes (use the databaseId from above) gh run watch <RUN_ID> - Monitor the run periodically using `gh run view <RUN_ID> --json status,conclusion` until it completes. If it fails, offer to re-trigger with `gh run rerun <RUN_ID>`. If it fails again, show the user the failure details with `gh run view <RUN_ID> --log-failed` and stop. + When `watch` returns, check the conclusion. If the run failed, offer to re-trigger with `gh run rerun <RUN_ID>`. If it fails again, show the failure details with `gh run view <RUN_ID> --log-failed` and stop.🤖 Prompt for 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. In @.claude/skills/release/SKILL.md around lines 155 - 166, The monitoring steps around gh run watch are redundant because gh run watch already blocks until the workflow finishes. Update the instructions in the release skill to make gh run watch the primary wait step, then only describe the post-completion checks using gh run view or rerun handling if the run fails. Keep the guidance centered on the tag-triggered CI run flow and the build-images workflow so the sequence is clear and non-duplicative.
🤖 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 @.claude/skills/release/SKILL.md:
- Around line 230-243: The PR creation commands in the release guide are using
the literal GITHUB_USER token in the gh pr create --head argument instead of
expanding the environment variable. Update the command examples so they
reference the shell variable form consistently in both community-operators and
community-operators-prod flows, and add the export reminder before these
commands in the release workflow section using the same GITHUB_USER symbol so
readers can copy/paste it correctly.
- Around line 78-80: The release SKILL example still uses the literal
`repos/{owner}/{repo}` placeholder in the `gh api` command, which will fail if
copied as-is. Update the executable snippet in the release workflow guidance to
use a real repository path or a dynamic lookup via `gh repo view`, and make sure
the `gh api .../git/refs` example references the resolved repository variable
rather than placeholder syntax.
- Line 24: The release guidance is contradictory because the skill forbids
changing jumpstarter_types.go while the cursor rule still tells users to update
kubebuilder defaults there. Update the releasing-operator rule so it no longer
instructs edits to controller/deploy/operator/api/v1alpha1/jumpstarter_types.go,
and remove the related CRD default verification grep that depends on that file.
Keep the rest of the release workflow intact and ensure the instructions in
.cursor/rules/releasing-operator.mdc match the SKILL.md guidance.
- Line 11: The referenced rule path in the release skill instructions is
incorrect, so update the guidance in SKILL.md to point to the existing
releasing-operator rule file. Use the existing instruction text around the
reference to `.claude/rules/releasing-operator.md` and change it to the correct
`.cursor/rules/releasing-operator.mdc` path so the release workflow points to
the right operator-specific documentation.
In @.cursor/rules/releasing-operator.mdc:
- Line 88: The commit description still mentions “types” as part of the files to
commit, but that item should be removed from the release instructions. Update
the commit description in releasing-operator.mdc so it only references the
intended Makefile, CRD, and kustomization changes, and keep the guidance
consistent with the fact that bundle/ is not committed.
---
Outside diff comments:
In @.cursor/rules/releasing-operator.mdc:
- Around line 40-52: Remove the stale `jumpstarter_types.go` update subsection
from the releasing operator rules document, including the kubebuilder default
image tag example and the note about `make manifests`/`make bundle`. The release
guidance should align with the `release` skill and avoid instructing changes to
`jumpstarter_types.go`, since the operator uses runtime resolution for `:latest`
defaults.
- Around line 82-85: The release verification steps include a stale grep for the
CRD default value that depends on kubebuilder-generated defaults, which no
longer aligns with the current release workflow. Update the checks in
releasing-operator.mdc by removing the `default: quay` verification tied to the
CRD manifest, and replace it with a validation that matches the remaining
release artifacts such as the CSV image references or release-config version
bumps. Use the existing `grep` commands in the release checklist as the location
to adjust.
---
Nitpick comments:
In @.claude/skills/release/SKILL.md:
- Around line 28-30: The fenced code block in SKILL.md is missing a language
specifier; update the workflow snippet to use a text code fence. Locate the
release flow example near the plain “Makefile update → commit → tag push → [CI
builds images] → GitHub Release → make bundle → make contribute” sequence and
change the surrounding fence to a labeled one so the markdown renderer can apply
proper formatting.
- Around line 155-166: The monitoring steps around gh run watch are redundant
because gh run watch already blocks until the workflow finishes. Update the
instructions in the release skill to make gh run watch the primary wait step,
then only describe the post-completion checks using gh run view or rerun
handling if the run fails. Keep the guidance centered on the tag-triggered CI
run flow and the build-images workflow so the sequence is clear and
non-duplicative.
🪄 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: Organization UI
Review profile: CHILL
Plan: Pro
Run ID: 4f6571ec-bdf6-4b73-a05e-f94877ed41e0
📒 Files selected for processing (2)
.claude/skills/release/SKILL.md.cursor/rules/releasing-operator.mdc
- Remove jumpstarter_types.go step from releasing-operator.mdc (was
contradicting the skill's "do not modify" instruction)
- Remove "types" from commit description in releasing-operator.mdc
- Use dynamic repo lookup instead of {owner}/{repo} placeholder
- Fix GITHUB_USER shell variable expansion in gh pr create commands
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
|
Not a review, just a small note. might be worth mentioning that permissions need to be granted in the community-operators repository prior to submitting the bundle update: https://github.com/k8s-operatorhub/community-operators/blob/main/operators/jumpstarter-operator/ci.yaml. Though I suspect everyone would eventually figure that out with minimal effort, but I'm not sure if the agent has that context. |
true, otherwise it will get ignored. |
4 participants
Summary
/releaseClaude 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-operatorsvX.Y.Z-rc.Ntag naming conventiondefaultControllerImageuses:latest, not a pinned version)Improvements from real v0.9.0-rc.1 release:
jumpstarter_types.goupdate step (operator resolves image tags at runtime via feat: operator auto-detects version for controller/router image defaults #844)AUTO_CONFIRM=1for non-interactivemake contributegh pr createcommands for community-operators PRsgh run rerunsuggestion on CI failureTest plan
/releaseloads and asks the right initial questions🤖 Generated with Claude Code