feat: update release command, with easier pr structure, updating release PR#1058
Merged
Conversation
mblos
commented
Jul 16, 2026
mblos
commented
Collaborator
- simplifies the /release workflow from three deliverables (separate bump PR + changelog PR + description update) to two: a single prep PR combining chart bumps and changelog
- updates the release PR description and title
mblos
requested review from
PhilippMatthes,
SoWieMarkus,
auhlig,
juliusclausnitzer and
umswmayj
as code owners
|
Warning Review limit reached
Next review available in: 31 minutes Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. How can I continue?After more reviews become available, a review can be triggered using the 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 reviews. How do review 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 refer docs for additional details. Review details⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (1)
📝 WalkthroughWalkthroughThe release command now creates one preparation PR containing Helm chart and changelog changes, then updates the release PR description to reference that preparation PR. Version extraction, phase instructions, local changelog handling, and summary output were updated. ChangesRelease orchestration
Estimated code review effort: 2 (Simple) | ~10 minutes Sequence Diagram(s)sequenceDiagram
participant ReleaseOrchestrator
participant WorkingTree
participant PullRequestCreator
participant ReleasePR
ReleaseOrchestrator->>WorkingTree: Write CHANGELOG.md and retain Helm edits
ReleaseOrchestrator->>PullRequestCreator: Open release/prepare-<PR_NUMBER>
PullRequestCreator-->>ReleaseOrchestrator: Return preparation PR URL
ReleaseOrchestrator->>ReleasePR: Update description with preparation PR dependency
Possibly related PRs
Suggested reviewers: 🚥 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: 4
🤖 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/commands/release.md:
- Line 171: Update the file-reading restriction in the release workflow
instructions to explicitly permit mechanically reading and replacing an existing
CHANGELOG.md entry during the Phase 5 update-run path, while preserving the
prohibition on using chart files or CHANGELOG.md for analysis.
- Line 21: Update both shell code fences in the release instructions, including
the occurrence near line 133, to specify a language identifier such as sh or
bash after the opening fence. Leave the fenced command content unchanged.
- Line 13: Update the `/release` orchestrator instructions so it only applies
uncommitted edits and dispatches `pull-request-creator`; remove its stated
ownership of git operations such as branch management, commits, and pushes.
Preserve the read-only roles of `release-digest`, `release-bump-planner`, and
`release-changelog-writer`, and defer all commit and push ownership to
`pull-request-creator`.
- Around line 105-108: Update the existing-entry detection in the changelog
workflow to use a literal/fixed-string search for the exact `[#<PR_NUMBER>]`
heading, rather than regex character-class matching. Preserve the first-run
prepend behavior and the update path that replaces the matching `##` entry.
🪄 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: CHILL
Plan: Pro
Run ID: 00d34634-5d9a-40a1-8333-514de4e878cd
📒 Files selected for processing (1)
.claude/commands/release.md
SoWieMarkus
approved these changes
Jul 16, 2026
…ase PR Signed-off-by: mblos <marcel.gute@sap.com>
Signed-off-by: mblos <marcel.gute@sap.com>
Contributor
Test Coverage ReportTest Coverage 📊: 70.3% |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.