No actionable comments were generated in the recent review. 🎉

Walkthrough

Updated release/changelog docs: /update-changelog accepts rc/beta and explicit versions (skips auto-version when explicit); prerelease index for beta/rc comes from git tags only; prerelease sections are collapsed/deduped; the task now auto-commits, pushes, and opens a PR; branch checks and compare links use main and v-prefixed tags.

Changes

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Poem

🐇 I hop through tags and count each one,
I fold old betas till the churn is done,
I commit, push, open a PR with glee,
Merge it in and tidy history,
A rabbit’s changelog, neat as can be.

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 help to get the list of available commands and usage tips.}

Review: Documentation accuracy — LGTM with one minor note

The changes correctly sync releasing.md with the actual current behavior of the /update-changelog automation. Spot-checked against the rake task (update_changelog.rake) and the slash command (.claude/commands/update-changelog.md):

• update-changelog.md fix (line 163): Accurate — compute_auto_version calls prerelease_indices_from_tags only; changelog headers are never consulted for the prerelease index.
• Explicit version support: Correctly documented; the rake task handles non-keyword inputs via normalize_version_string.
• Auto collapse + dedup: Accurate — collapse_prerelease_series + consolidate_changelog_blocks/deduplicate_block_entries confirm this.
• Auto-commit/push/PR: Correct — Step 5 of the slash command spec documents this as the expected behavior for versioned invocations.
• v prefix on compare links: Accurate — update_changelog_links in the rake task always emits v<version> in the generated URLs.

One small inaccuracy flagged inline (auto-compute bullet does not apply when an explicit version is supplied).

Potential follow-up (pre-existing, out of scope for this PR): .claude/commands/update-changelog.md line 29 still reads "Commit and push CHANGELOG.md" as a manual step in the "Before a release" section, which contradicts the auto-commit/push/PR behavior documented in its own Step 5. Worth a follow-up pass to remove that stale instruction.

Greptile Summary

This documentation-only PR syncs releasing.md and .claude/commands/update-changelog.md with three recent automation improvements to update_changelog.rake: explicit version support, prerelease section collapse/deduplication, and auto-commit/push/PR. It also adds the v-prefix requirement for CHANGELOG compare links and corrects the branch name in the auto-commit guard from master to main.

Key changes:

• releasing.md step 1 now lists all argument forms (release, rc, beta, explicit version), documents the auto-PR flow, and removes the now-obsolete manual "commit and push" step
• New note in releasing.md § 4 ("Version Format") documents the v-prefix requirement for compare links — consistent with update_changelog_links in the rake task
• releasing.md Option A post-release catch-up correctly switches to /update-changelog 16.5.0 (explicit version, which triggers auto-PR) followed by sync_github_release
• update-changelog.md rake-task summary bullet corrected: prerelease index is determined solely from git tags, not changelog headers (confirmed in compute_auto_version)
• update-changelog.md step 5 branch guard updated from master to main (the repo default branch)
• Minor pre-existing inconsistency: several other master references in update-changelog.md process steps (lines 232–233, 268) and the example link on line 209 were not updated in this pass

Confidence Score: 5/5

• Documentation-only PR with accurate changes verified against the rake task source; safe to merge.
• All documented behaviors were cross-checked against update_changelog.rake: the git-tags-only prerelease index (compute_auto_version), the v-prefix compare link generation (update_changelog_links), the main branch reference (cleanup_collapsed_prerelease_links), and the auto-commit/push flow (step 5 instructions). The sole issue is a handful of pre-existing master references in process-step prose that this PR didn't sweep — low-priority cleanup for a follow-up.
• No files require special attention; the pre-existing master references in update-changelog.md lines 232–233 and 268 are worth a follow-up cleanup but do not block merge.

Important Files Changed

Sequence Diagram

sequenceDiagram
    participant Dev as Developer
    participant CC as Claude Code<br/>/update-changelog
    participant Rake as update_changelog.rake
    participant GH as GitHub

    Dev->>CC: /update-changelog release<br/>(or rc / beta / explicit version)
    CC->>Rake: bundle exec rake update_changelog[mode]
    Note over Rake: git tags → latest stable version<br/>changelog headings → bump type<br/>git tags only → prerelease index
    Rake-->>CC: CHANGELOG.md stamped with version header<br/>+ v-prefixed compare links updated
    CC->>CC: Verify working tree clean<br/>Verify branch is main
    CC->>GH: git push (new branch changelog-X.Y.Z)
    CC->>GH: gh pr create (changelog diff as body)
    GH-->>Dev: PR opened for review
    Dev->>GH: Review + merge changelog PR
    Dev->>Dev: bundle exec rake release
    Note over Dev: rake release reads version from CHANGELOG.md<br/>auto-creates GitHub release

_{Reviews (2): Last reviewed commit: "Address review feedback on release docs ..." | Re-trigger Greptile}

Review: Sync release docs with recent changelog automation changes

This is a clean, accurate documentation sync. The changes to releasing.md correctly reflect the current behavior: explicit version support, rc/beta collapsing/deduplication, and the auto-commit/push/PR flow replacing the old manual step. The update-changelog.md fix for the rake task description is also accurate.

One remaining inconsistency

update-changelog.md has a "Before a release" summary block (lines 26–30) that still describes the old manual workflow and was not updated by this PR:

**Before a release** -- Stamp a version header and prepare for release:

- Run `/update-changelog release` (or `rc` or `beta`) to add entries AND stamp the version header
- The version is auto-computed from changelog content (see "Auto-Computing the Next Version" below)
- Commit and push CHANGELOG.md                          ← stale: auto-PR now
- Then run `rake release` (no args needed ...)          ← stale: needs PR merge first

Step 5 of the same file (lines 325–332) already documents the correct auto-commit/push/PR behavior, so this summary block is contradicting the actual instructions. Suggested update:

**Before a release** -- Stamp a version header and prepare for release:

- Run `/update-changelog release` (or `rc`, `beta`, or an explicit version like `16.5.0.rc.10`) to add entries AND stamp the version header
- The version is auto-computed from changes (breaking → major, features → minor, fixes → patch)
- The command automatically commits, pushes, and opens a PR — review and merge it
- Then run `rake release` (no args needed -- it reads the version from CHANGELOG.md)
- The release task automatically creates a GitHub release from the changelog section

This isn't a blocker for merging — the detailed Step 5 instructions are authoritative — but it would prevent the summary block from misleading contributors.

Otherwise LGTM

All three documentation sites (releasing.md steps, the v-prefix requirement note, and the rake task bullet in update-changelog.md) are now accurate and internally consistent with the actual rake task and Step 5 behavior. The PR achieves its stated goal.

Review: Documentation-only sync, correct but partially incomplete

The changes to releasing.md are accurate and well-aligned with the current automation:

• Explicit version support documented correctly
• Auto-compute-skipped-for-explicit-version caveat is accurate
• rc/beta collapse/dedup note is correct
• Auto-commit/push/PR flow properly replaces the old manual commit step
• v prefix requirement for compare links is correct (matches update-changelog.md line 200)
• Option A post-release instructions updated correctly

One gap in .claude/commands/update-changelog.md

The single-line fix ("changelog headings and git tags" → "git tags only") is correct, but the "Before a release" section earlier in the same file still has two stale lines that weren't updated — see the inline comment. They describe the old manual commit/push workflow and still say "auto-computed from changelog content", which directly contradicts the fix made on line 163. Worth addressing in a follow-up (or a quick squash onto this PR) to keep the command file internally consistent.

Addressed the stale "Before a release" summary block in update-changelog.md (lines 26–30) in 27c288a:

• Updated to mention explicit version support (rc, beta, or explicit like 16.5.0.rc.10)
• Replaced "Commit and push CHANGELOG.md" with "The command automatically commits, pushes, and opens a PR — review and merge it"
• Also fixed the master → main branch check on line 327

This addresses the feedback from @claude[bot] and @greptile-apps[bot] about the stale manual workflow instructions contradicting Step 5's auto-PR behavior.

Clean documentation sync. A few notes: (1) Remaining stale master references: This PR fixes line 327 but lines 209, 223, 232-233, 260, 267-269 of update-changelog.md still reference master/origin/master. The repo default branch is main — worth a follow-up. (2) Minor: The Version Stamping section header (line 153) only lists release/rc/beta but not explicit versions, though Step 4 documents them correctly. (3) The actual changes look correct: the git-tags-only description, the explicit-version Option A example in releasing.md, and the v-prefix note for compare links are all accurate.

Review: Sync release docs with recent changelog automation changes

This is a clean documentation-only PR. The changes accurately reflect the current automation behavior.

What's done well

• All master to main references in git commands, compare link examples, and branch checks are updated consistently across both files.
• The prerelease index description fix ("git tags only, not changelog headers") matches the actual compute_auto_version() logic.
• The new Option A post-release flow correctly adds git pull --rebase before sync_github_release.
• The explicit version support (16.5.0.rc.10) is documented at both levels (quick summary and detailed process).

Minor gap: missing branch-switch step after merging the auto-PR

The new auto-PR flow in update-changelog.md ("Before a release" section) goes:

• The command automatically commits, pushes, and opens a PR — review and merge it
• Then run rake release (no args needed...)

After the auto-PR is merged on GitHub, the user is still on the local changelog-X.Y.Z feature branch. Before running rake release, they need to return to main and pull:

git checkout main
git pull --rebase
bundle exec rake release

The same implicit gap exists in releasing.md Step 1 to Step 2 transition — step 3 says "merge", then the release task section jumps straight to rake release with no branch-switch guidance.

rake release does pull latest changes internally, but only from the current branch — being on the feature branch would pull from the wrong upstream. Adding a one-liner note ("checkout main and pull before running the release task") would close this.

This is the only substantive issue; everything else looks correct and well-aligned with the actual automation behavior.