Update changelog for 17.0.0.rc.11

[justin808]

Why

React on Rails 17.0.0.rc.11 needs focused release notes for the user-visible changes merged to release/17.0.0 since v17.0.0.rc.10. Stamping the changelog before publishing lets the release task read the intended version and generate the corresponding GitHub release notes.

What changed

• stamped 17.0.0.rc.11 immediately below Unreleased
• moved the existing Pro license/runtime and stable RSC 19.2.1 entries into the new RC section
• updated the compare links from v17.0.0.rc.10 to v17.0.0.rc.11
• left every earlier RC section intact

Classification sweep

PR	Result	Category	Rationale
4660	entry-needed	Pro runtime	Changes published Pro license metadata, packaged terms, attribution behavior, and diagnostics; already represented in the changelog.
4670	entry-needed	Pro runtime	Changes the Pro/RSC package floor, generator output, compatibility checks, and shipped artifact license; already represented in the changelog.
4671	no-entry	perf-reliability	Corrects the still-unreleased 4660 implementation, including regex-timeout safety; the final user-visible behavior is already covered by the 4660 entry.

The mechanical v17.0.0.rc.10..origin/release/17.0.0 sweep returned no UNKNOWN commits.

Verification

• bundle exec rspec spec/react_on_rails/update_changelog_rake_helpers_spec.rb from react_on_rails/: 33 examples, 0 failures
• repository pre-commit checks: trailing newlines, offline Markdown links, and Prettier passed
• script/ci-changes-detector origin/release/17.0.0: documentation-only; no hosted CI jobs recommended
• git diff --check origin/release/17.0.0...HEAD: passed
• structural checks: trailing newline, unique version headings, newest-first placement, and compare-link endpoints passed

Review gate

• Sol/xhigh codex review --base origin/release/17.0.0: no actionable regressions; independently reproduced the stamp from the repository helpers
• Claude Opus/xhigh report-only review with tools disabled: no BLOCKING or DISCUSS findings
• /simplify: skipped as not applicable to a four-line machine-generated changelog header/link diff

Review churn

• follow-up commits after first push: 0
• review-fix rounds before first push: 0
• residual risk: the release task must still bump version metadata and create the v17.0.0.rc.11 tag after this PR merges; that is the normal release action, not part of this changelog-only PR

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 5739da1e-eeca-45fc-b328-8df116691313

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch jg-codex/changelog-17.0.0.rc.11

---

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

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[claude]

Review: Update changelog for 17.0.0.rc.11

This is a small, mechanical, changelog-only PR (1 file, +4/-1). No application code is touched, so there are no correctness, security, or performance concerns in the usual sense. I verified the diff structurally:

What it does

• Inserts a new ### [17.0.0.rc.11] - 2026-07-14 heading directly below ### [Unreleased], which causes the existing Pro license/RSC-19.2.1 #### Changed entries to now fall under the new RC section instead of Unreleased.
• Updates the [unreleased] compare link to diff from v17.0.0.rc.11...main (previously v17.0.0.rc.10...main).
• Adds a new [17.0.0.rc.11]: .../compare/v17.0.0.rc.10...v17.0.0.rc.11 link.
• Leaves all earlier RC sections/links untouched.

Verification performed

• grep -n "17.0.0.rc.11" CHANGELOG.md confirms no duplicate heading/link anchors were introduced.
• Confirmed the new heading sits in correct reverse-chronological order (above rc.10, below Unreleased).
• Confirmed blank-line/heading formatting matches the established pattern used for prior RC sections (e.g. rc.10, rc.9).
• Confirmed the compare-link endpoints are internally consistent (rc.10 → rc.11 for the new link, rc.11 → main for unreleased).

Minor observations (non-blocking)

• Unreleased is now empty (no entries), which is expected/correct once all pending entries are stamped into the RC section — consistent with prior release-stamping PRs in this file.
• Per the PR description, the v17.0.0.rc.11 git tag doesn't exist yet at review time; that's expected to be created by the release task after merge, not part of this PR's scope.

No issues found. The change is internally consistent, matches existing conventions, and the described classification sweep (PRs 4660/4670/4671) looks reasonable given the entries already present in the file.

[claude]

Review: Update changelog for 17.0.0.rc.11

Overview

Straightforward, changelog-only PR: stamps a new [17.0.0.rc.11] section directly beneath the (now-empty) [Unreleased] heading, re-parents the two existing Pro entries (RSC 19.2.1 stable package, accurate commercial-license metadata) under it, and updates the compare links accordingly.

Correctness

• The new heading is inserted directly above #### Changed, so the existing entries are re-parented rather than duplicated — confirmed no content was dropped or copied.
• Compare links are internally consistent: [unreleased] now points v17.0.0.rc.11...main, and the new [17.0.0.rc.11] link correctly spans v17.0.0.rc.10...v17.0.0.rc.11. Every earlier RC link is untouched.
• Heading style (### [x.y.z] - date), reference-link format, and the #### Changed subsection all match the conventions used by the surrounding RC sections (rc.10, rc.9, etc.).

Minor observation

• The stamped date is 2026-07-14, but the PR's only commit is dated 2026-07-15T09:47:12Z (one day later). Worth double-checking this is intentional (e.g., matching an actual planned release/tag date) rather than a stale date carried over from drafting — not blocking, since prior RC entries may follow the same "intended release date" convention rather than commit date.

Risk / scope

• Single-file, additive change to CHANGELOG.md with no code or behavior impact. Verification steps in the PR description (rspec for the changelog helpers, structural checks, offline-link/Prettier pre-commit checks) are appropriate and sufficient for a docs-only change.
• No security, performance, or test-coverage concerns — this is documentation only.

Overall: looks good to merge once the date is confirmed intentional.

[greptile-apps]

Greptile Summary

This PR stamps the changelog for the 17.0.0.rc.11 release. The main changes are:

• Adds the 17.0.0.rc.11 section below Unreleased.
• Moves the current release entries into the new section.
• Advances the Unreleased comparison base to rc.11.
• Adds the rc.10-to-rc.11 comparison link.

Confidence Score: 5/5

This looks safe to merge.

• The release heading matches the format consumed by the release helpers.
• The section is newest-first and contains the intended release entries.
• The comparison links form the expected rc.10-to-rc.11-to-main sequence.
• No blocking issues were found in the changed code.

Important Files Changed

Filename	Overview
CHANGELOG.md	Adds the rc.11 release heading and updates the related comparison links.

_{Reviews (1): Last reviewed commit: "Update changelog for 17.0.0.rc.11" | Re-trigger Greptile}

[claude]

Review

Small, mechanical changelog-only change — verified against the rest of CHANGELOG.md.

What it does: Stamps ### [17.0.0.rc.11] - 2026-07-15 directly below ### [Unreleased], moves the two existing Pro entries (PR 4670, PR 4660) into the new section, and updates the compare links ([unreleased] now v17.0.0.rc.11...main, new [17.0.0.rc.11] link v17.0.0.rc.10...v17.0.0.rc.11).

Checks:

• Version heading placement and link chain are consistent with the existing rc.10/rc.9 pattern.
• Unreleased section is left empty, which is correct since both prior entries were moved out.
• No code, no tests, no security/performance surface — pure docs.

No issues found. LGTM (noting this PR is already merged).