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.}

Greptile Summary

This PR promotes the v10.0.0-rc.1 CHANGELOG section to stable v10.0.0, updating the section header date (April 7 → April 8, 2026) and correcting the version comparison links at the bottom of the file. The lib/shakapacker/version.rb and package.json files intentionally remain at 10.0.0.rc.1 — the custom rake release task reads the CHANGELOG version, detects it is greater than the current gem version, and bumps those files automatically as part of publishing.

Confidence Score: 5/5

Safe to merge — documentation-only change with four correct, consistent line edits.

All four changed lines are correct: section header renamed, date updated, and both version comparison links updated. The custom release rake task handles bumping version files post-merge, so intentionally leaving them at rc.1 is correct. No logic, code, or security implications.

No files require special attention.

Important Files Changed

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart TD
    A["Merge this PR\n(CHANGELOG.md: v10.0.0-rc.1 → v10.0.0)"] --> B["bundle exec rake release"]
    B --> C["extract_latest_changelog_version()\nreturns '10.0.0'"]
    C --> D{"changelog_version >\ncurrent_gem_version?\n10.0.0 > 10.0.0.rc.1 ✓"}
    D -->|Yes| E["Prompt: Release 10.0.0?"]
    E --> F["Update lib/shakapacker/version.rb\n10.0.0.rc.1 → 10.0.0"]
    F --> G["Update package.json\n10.0.0-rc.1 → 10.0.0"]
    G --> H["Push gem to RubyGems\nPush npm package\nCreate GitHub release"]

_{Reviews (1): Last reviewed commit: "Update CHANGELOG.md for v10.0.0" | Re-trigger Greptile}

Review: CHANGELOG.md promotion to v10.0.0

Overall: Clean, minimal changelog-only PR. The changes are correct.

What the PR does

• Renames the v10.0.0-rc.1 section header to v10.0.0 - April 8, 2026
• Updates the bottom compare links from v10.0.0-rc.1 to v10.0.0

Release instruction verification

The PR description says to run bundle exec rake release with no args after merging. I verified this is correct:

The release task's extract_latest_changelog_version reads CHANGELOG.md and finds v10.0.0 as the first versioned section. Since Gem::Version.new("10.0.0") > Gem::Version.new("10.0.0.rc.1"), the task will use 10.0.0 as the target — triggering gem bump --no-commit --version 10.0.0 to update version.rb and package.json automatically. The no-args flow works as documented.

Notes

• The compare link [v10.0.0]: .../compare/v9.7.0...v10.0.0 references a tag that doesn't exist yet — it will resolve correctly once rake release creates the v10.0.0 git tag. This is expected behavior.
• The header date is April 8 (the PR was opened yesterday); if this merges today (April 9) the date will be slightly off. Minor nit, not a blocker.

Verdict: LGTM. Ready to merge.