Consider merging Pro changelog into main CHANGELOG.md

[justin808]

Summary

Currently we maintain two separate changelogs:

• /CHANGELOG.md - Open source React on Rails
• /react_on_rails_pro/CHANGELOG.md - Pro features

Proposal

Merge Pro entries into the main CHANGELOG.md with a #### Pro subcategory under each release version.

Benefits

1. Fix diff links - Currently diff links between versions don't work correctly across separate files
2. Marketing benefit - Users see Pro features in the same changelog and may want to upgrade
3. Simpler maintenance - One file to update instead of two
4. Better discoverability - Pro users see all changes in one place

Implementation

• Add #### Pro subcategory under each release version in CHANGELOG.md
• Move relevant Pro entries from react_on_rails_pro/CHANGELOG.md
• Potentially deprecate the separate Pro changelog
• Update documentation about changelog conventions in CLAUDE.md

Context

This came up during changelog curation for v16.2.0.beta.13 release, where Pro-only PRs (#2139, #2137) needed to be tracked separately, and the diff links between versions were problematic.

---

Filed from branch jg/changelog-beta13

[coderabbitai]

📝 CodeRabbit Plan Mode

Generate an implementation plan and agent prompts for this issue.

• Create Plan

Examples

• Example 1
• Example 2

🔗 Similar & Duplicate Issues

Related Issues

• shakacode/react_on_rails#1874
• shakacode/react_on_rails#1871
• shakacode/react_on_rails#1876
• shakacode/react_on_rails#2113
• shakacode/react_on_rails#2103

🔗 Related PRs

#1855 - Move Pro Ruby code to MIT license [merged]
#1987 - Comprehensive rewrite of React on Rails Pro README [merged]
#1993 - Claude/remove pro warning badge [merged]
#2048 - Consolidate beta releases into v16.2.0.beta.8 [merged]
#2050 - Consolidate beta changelog entries into v16.2.0.beta.8 [merged]

👤 Suggested Assignees

• AbanoubGhadban
• justin808

---

🧪 Issue enrichment is currently in early access.

To disable automatic issue enrichment, add the following to your .coderabbit.yaml:

issue_enrichment:
  auto_enrich:
    enabled: false