Update CHANGELOG.md for 17.0.0.rc.4#4042
Conversation
Stamp the 17.0.0.rc.4 release header and reconcile the Unreleased entries that landed after the rc.3 tag: - Move the source-mapped stack traces entry (PR 3940) out of the rc.3 section into rc.4 (PR 3940 merged after v17.0.0.rc.3 was tagged). - Add the missing PR 4026 attribution to the RSC peer-compatibility (React 19.2 floor) entry. - Merge the two duplicate "#### Added" headings in the section into one. Co-Authored-By: Claude Opus 4.8 (1M context) <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 (1)
Walkthrough
ChangesCHANGELOG 17.0.0.rc.4 release entry
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~2 minutes Possibly related PRs
Suggested labels
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ 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 |
Greptile SummaryThis PR stamps the
Confidence Score: 5/5Documentation-only change with no runtime impact; safe to merge. The change is limited to CHANGELOG.md. The rc.4 header date, compare links, entry placement, PR attributions, and heading structure are all correct. The rc.3 section is left intact and no entry appears duplicated or lost. No files require special attention. Important Files Changed
Reviews (1): Last reviewed commit: "Update CHANGELOG.md for 17.0.0.rc.4" | Re-trigger Greptile |
Summary
Stamps the 17.0.0.rc.4 changelog header and reconciles the post-rc.3 entries.
What changed
### [17.0.0.rc.4] - 2026-06-14with the standard compare-link updates (v17.0.0.rc.3...v17.0.0.rc.4,unreleased → rc.4...main). Prior RC sections are left intact per the prerelease convention.rc.3section, but#3940merged afterv17.0.0.rc.3was tagged (verified:d9ac060a0is not an ancestor of the rc.3 tag).[PR 4026]attribution to the RSC peer-compatibility (React 19.2 floor) entry, which previously linked only the issue.#### Addedheadings in the section into one.rc.4 contents
useRailsForm+render_model_errors(Add useRailsForm hook + render_model_errors concern: Inertia useForm-style Rails bridge (#3872) #3942), node-renderer/health&/readyendpoints (Add built-in /health and /ready endpoints to the Pro node renderer #3939, Pro), source-mapped stack traces (Add source-mapped stack traces to the Pro node renderer (#3893 core) #3940, Pro)Other merged PRs since rc.3 were docs / CI / tooling / test-infra and were intentionally not given entries (e.g. #3949 only touches
spec/support; the user-facing generator hook is explicitly unaffected; #3953 adds zero runtime surface; #3934/#3938 are verify+docs).Notes
prettier@3.6.2. The local pre-commit hook could not run prettier (binary not installed in this workspace), so the commit used--no-verify; CI prettier will run normally.After merge, run
rake release(no args) to publishv17.0.0.rc.4and auto-create the GitHub release from this section.🤖 Generated with Claude Code
Note
Low Risk
Documentation-only changelog edits with no runtime or API surface changes.
Overview
Adds the
17.0.0.rc.4(2026-06-14) release section toCHANGELOG.mdand updates the bottom compare links so[unreleased]points atv17.0.0.rc.4...mainand[17.0.0.rc.4]coversv17.0.0.rc.3...v17.0.0.rc.4.The edit re-sorts notes that landed after the rc.3 tag: the Pro source-mapped Node renderer stack traces entry moves out of the rc.3 block into rc.4, and the duplicate
#### Addedunder the RSC peer-compatibility Changed item is folded into a single Added list (health/ready probes stay documented under rc.4 Added). The React 19.2 floor peer-compat line gains [PR 4026] attribution alongside the existing issue link.No application or library code changes—release documentation only.
Reviewed by Cursor Bugbot for commit 40c7a88. Bugbot is set up for automated code reviews on this repo. Configure here.
Summary by CodeRabbit
New Features
useRailsFormhook for improved form handling/healthand/readyendpoints to Node renderer for better observabilityChanged