Skip to content

Update CHANGELOG.md for 17.0.0.rc.4#4042

Merged
justin808 merged 1 commit into
mainfrom
jg-conductor/changelog-rc4
Jun 15, 2026
Merged

Update CHANGELOG.md for 17.0.0.rc.4#4042
justin808 merged 1 commit into
mainfrom
jg-conductor/changelog-rc4

Conversation

@justin808

@justin808 justin808 commented Jun 15, 2026

Copy link
Copy Markdown
Member

Summary

Stamps the 17.0.0.rc.4 changelog header and reconciles the post-rc.3 entries.

What changed

  • Stamped ### [17.0.0.rc.4] - 2026-06-14 with 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.
  • Moved the source-mapped stack traces entry (PR 3940) into rc.4. It had been placed inside the already-tagged rc.3 section, but #3940 merged after v17.0.0.rc.3 was tagged (verified: d9ac060a0 is not an ancestor of the rc.3 tag).
  • Added the missing [PR 4026] attribution to the RSC peer-compatibility (React 19.2 floor) entry, which previously linked only the issue.
  • Merged the two duplicate #### Added headings in the section into one.

rc.4 contents

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

  • Verified clean under the repo's pinned 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 publish v17.0.0.rc.4 and 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 to CHANGELOG.md and updates the bottom compare links so [unreleased] points at v17.0.0.rc.4...main and [17.0.0.rc.4] covers v17.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 #### Added under 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

    • Introduced useRailsForm hook for improved form handling
    • Added /health and /ready endpoints to Node renderer for better observability
    • Expanded React 19 support with root error callback registration
    • Enhanced Pro cache tag revalidation capabilities
  • Changed

    • Improved error diagnostics with source-mapped stack traces in Node renderer
    • Extended RSC peer compatibility for React 19.2.7+

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>
@coderabbitai

coderabbitai Bot commented Jun 15, 2026

Copy link
Copy Markdown
Contributor

Review Change Stack

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 9fc98e5e-b235-4ced-9cd6-1386d1ecfd4d

📥 Commits

Reviewing files that changed from the base of the PR and between 3b677e9 and 40c7a88.

📒 Files selected for processing (1)
  • CHANGELOG.md

Walkthrough

CHANGELOG.md gains a new 17.0.0.rc.4 release section dated 2026-06-14 with Added and Changed entries covering Pro cache tag revalidation, React 19 root error callbacks, useRailsForm, node renderer health endpoints, source-mapped stack traces (moved from rc.3), and widened RSC peer compatibility. The bottom compare links are updated accordingly.

Changes

CHANGELOG 17.0.0.rc.4 release entry

Layer / File(s) Summary
17.0.0.rc.4 release block and compare links
CHANGELOG.md
Inserts the 17.0.0.rc.4 section under Unreleased with Added/Changed bullets, removes the source-mapped stack traces entry from 17.0.0.rc.3, and updates footer compare links to point [unreleased] at v17.0.0.rc.4...main while adding a [17.0.0.rc.4] link.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Possibly related PRs

  • shakacode/react_on_rails#3966: Directly overlaps — both PRs involve the 17.0.0.rc.3 changelog section and the "node renderer source-mapped stack traces" entry that this PR moves to 17.0.0.rc.4.
  • shakacode/react_on_rails#3859: Also modifies the same 17.0.0.rc.* changelog sections and [unreleased] compare link baseline.
  • shakacode/react_on_rails#3852: Updates the same CHANGELOG.md version markers and compare-link sections under Unreleased for the 17.0.0.rc.* line.

Suggested labels

review-needed, documentation, P3

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title accurately and concisely describes the main change: updating CHANGELOG.md for a specific release version (17.0.0.rc.4).
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch jg-conductor/changelog-rc4

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.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

@greptile-apps

greptile-apps Bot commented Jun 15, 2026

Copy link
Copy Markdown

Greptile Summary

This PR stamps the 17.0.0.rc.4 release in CHANGELOG.md, reconciling entries that were either misplaced or missing attribution from the post-rc.3 merge window.

  • Stamped [17.0.0.rc.4] - 2026-06-14 with the correct compare links (v17.0.0.rc.3...v17.0.0.rc.4; unreleased advanced to v17.0.0.rc.4...main); prior RC sections are left intact.
  • Moved the source-mapped stack traces entry (PR Add source-mapped stack traces to the Pro node renderer (#3893 core) #3940) from the rc.3 #### Added block into rc.4, and merged the two duplicate #### Added headings that existed in the pre-stamp section into one; also added the missing [PR 4026] attribution to the RSC peer-compatibility entry.

Confidence Score: 5/5

Documentation-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

Filename Overview
CHANGELOG.md Release header, compare links, entry placement, and heading deduplication all look correct; no content was lost or duplicated.

Reviews (1): Last reviewed commit: "Update CHANGELOG.md for 17.0.0.rc.4" | Re-trigger Greptile

@justin808 justin808 merged commit a13cd9f into main Jun 15, 2026
13 checks passed
@justin808 justin808 deleted the jg-conductor/changelog-rc4 branch June 15, 2026 08:23
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant