docs: fix published setup guidance gaps#2860
Conversation
|
Note Reviews pausedIt looks like this branch is under active development. To avoid overwhelming you with review comments due to an influx of new commits, CodeRabbit has automatically paused this review. You can configure this behavior by changing the Use the following commands to manage reviews:
Use the checkboxes below for quick actions:
WalkthroughDocumentation links and guidance were updated across multiple docs: Pro links point to the Pro docs page; RSC migration instructions were refactored to reference an infrastructure runbook and upgrade checklist; Node renderer, image asset, and i18n docs were revised to prefer root-level scripts/imports and clarify launcher/config patterns. Changes
Estimated code review effort🎯 3 (Moderate) | ⏱️ ~20 minutes Poem
🚥 Pre-merge checks | ✅ 3✅ Passed checks (3 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 |
|
Reviewed the three changed files. Changes are correct and well-scoped:
No issues found. LGTM. |
Greptile SummaryThis is a docs-only PR that fixes two dead Pro links and replaces a stale RSC migration section with a concise runbook pointer.\n\n- Fixes Confidence Score: 5/5Safe to merge — docs-only changes with no code, no tests, and no runtime impact. All three changes are minimal, targeted documentation fixes. Dead links are replaced with verified live URLs, and the removed stale migration steps are superseded by correct cross-references whose target files all exist in the repo. No files require special attention. Important Files Changed
Flowchart%%{init: {'theme': 'neutral'}}%%
flowchart TD
A[User reads OSS SSR or Config docs] -->|dead link before PR| B["pro.reactonrails.com ❌"]
A -->|fixed link after PR| C["reactonrails.com/docs/pro/ ✅"]
D[User reads Pro RSC purpose-and-benefits] -->|old path| E[Manual ruby initializer + webpack snippet\nincomplete / skips Node Renderer]
D -->|new path| F[Install Node Renderer]
F --> G["rails generate react_on_rails:rsc"]
G --> H[upgrading-existing-pro-app.md full checklist]
H --> I[Gradual Component Migration]
Reviews (1): Last reviewed commit: "docs: refresh stale setup instructions" | Re-trigger Greptile |
justin808
changed the title
![claude[bot]](https://avatars.githubusercontent.com/in/1236702?s=60&v=4){kind=small}
Review: docs: fix published setup guidance gapsOverall this is a clean, well-scoped docs-only PR. The motivation is solid and the changes are accurate. A couple of things worth addressing before merge: Incomplete stale-link fixThe PR correctly updates
These are in the unchanged banner at the top of each file so they didn't show in the diff, but they're the same class of broken link the PR set out to fix. A grep shows ~10 other occurrences across the docs tree that could be addressed here or in a follow-up. Path inconsistency between heroku.md and js-configuration.mdThe new Minor observations (non-blocking)
|
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Inline comments:
In `@docs/pro/react-server-components/purpose-and-benefits.md`:
- Around line 138-146: Update the broken anchor in the markdown link in
purpose-and-benefits.md: replace the existing link target
"#install-react-on-rails-pro-node-renderer" in the "[Pro
Installation](../installation.md#install-react-on-rails-pro-node-renderer)" link
with the correct anchor "#node-renderer-installation" that matches the "Node
Renderer Installation" heading in the installation doc so the link resolves
properly.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Organization UI
Review profile: CHILL
Plan: Pro
Run ID: 21be3d69-cdae-4f2d-92d3-c94b1c8ca854
📒 Files selected for processing (3)
docs/oss/configuration/README.mddocs/oss/core-concepts/react-server-rendering.mddocs/pro/react-server-components/purpose-and-benefits.md
There was a problem hiding this comment.
🧹 Nitpick comments (2)
docs/oss/building-features/node-renderer/heroku.md (2)
43-43: Clarify the wording for package manager substitution.The phrase "equivalent script command" might be unclear. The actual change is simply replacing
pnpmwithnpmoryarnin the Procfile.web line.✏️ Suggested rewording
-If you use `npm` or `yarn` instead of `pnpm`, use the equivalent script command in `Procfile.web`. +If you use `npm` or `yarn` instead of `pnpm`, replace `pnpm` with your package manager in the `Procfile.web` line above (e.g., `npm run node-renderer` or `yarn run node-renderer`).🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@docs/oss/building-features/node-renderer/heroku.md` at line 43, Reword the sentence to clearly instruct replacing the package manager token in Procfile.web: instead of saying "equivalent script command", state that you should replace "pnpm" with "npm" or "yarn" in the Procfile.web line (e.g., change the command starting with "pnpm" to start with "npm" or "yarn"); reference the Procfile.web entry and the tokens "pnpm", "npm", and "yarn" so readers know exactly what to change.
30-30: Consider showing all three package manager variants for clarity.While line 43 mentions npm/yarn alternatives, showing explicit examples for all three package managers (npm, yarn, pnpm) would align with the package-manager-agnostic documentation pattern used elsewhere in end-user docs.
📝 Suggested enhancement
-renderer: pnpm run node-renderer +renderer: pnpm run node-renderer # or: npm run node-renderer, or: yarn run node-rendererOr show all three as separate options:
-renderer: pnpm run node-renderer +# Choose one based on your package manager: +renderer: npm run node-renderer +# renderer: yarn run node-renderer +# renderer: pnpm run node-renderer🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@docs/oss/building-features/node-renderer/heroku.md` at line 30, Replace the single package-manager-specific line "renderer: pnpm run node-renderer" with three explicit variants so readers can copy the command for their tool of choice; update the section to show "renderer: npm run node-renderer", "renderer: yarn run node-renderer" (or "yarn node-renderer" if preferred), and "renderer: pnpm run node-renderer" so all three package managers are represented consistently with other docs.
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Nitpick comments:
In `@docs/oss/building-features/node-renderer/heroku.md`:
- Line 43: Reword the sentence to clearly instruct replacing the package manager
token in Procfile.web: instead of saying "equivalent script command", state that
you should replace "pnpm" with "npm" or "yarn" in the Procfile.web line (e.g.,
change the command starting with "pnpm" to start with "npm" or "yarn");
reference the Procfile.web entry and the tokens "pnpm", "npm", and "yarn" so
readers know exactly what to change.
- Line 30: Replace the single package-manager-specific line "renderer: pnpm run
node-renderer" with three explicit variants so readers can copy the command for
their tool of choice; update the section to show "renderer: npm run
node-renderer", "renderer: yarn run node-renderer" (or "yarn node-renderer" if
preferred), and "renderer: pnpm run node-renderer" so all three package managers
are represented consistently with other docs.
ℹ️ Review info
⚙️ Run configuration
Configuration used: Organization UI
Review profile: CHILL
Plan: Pro
Run ID: a1bc8742-6d9a-4b3d-8fb3-f9ebe7bfc671
📒 Files selected for processing (4)
docs/oss/building-features/i18n.mddocs/oss/building-features/images.mddocs/oss/building-features/node-renderer/heroku.mddocs/oss/building-features/node-renderer/js-configuration.md
✅ Files skipped from review due to trivial changes (2)
- docs/oss/building-features/i18n.md
- docs/oss/building-features/node-renderer/js-configuration.md
|
Good docs hygiene PR. The changes are accurate and correctly modernize the setup instructions. A few issues worth addressing. Dead links remain in modified files: heroku.md and js-configuration.md both still carry the dead pro.reactonrails.com link in their Pro Feature callout banner (line 4 of each file). Since the PR's stated goal is fixing dead Pro destination links, these two 'Get a license' links in the files you're already touching should be updated to https://reactonrails.com/docs/pro/ for consistency with the other fixes in this PR. heroku.md — pnpm assumed in Procfile example before the caveat: The Procfile.web example leads with 'pnpm run node-renderer', and only the following paragraph explains that npm/yarn users must substitute. Readers who copy-paste before reading further will get a broken Procfile if they're not on pnpm. A short note before the snippet would help. Scope — many other pro.reactonrails.com links remain: There are ~20+ other occurrences of pro.reactonrails.com in the docs directory not touched by this PR. That's expected for a targeted fix, but worth a follow-up issue to track the full cleanup. |
Review: docs: fix published setup guidance gapsOverall this is a solid, low-risk docs cleanup that correctly redirects dead Pro links and modernises the node-renderer setup guidance. Three issues worth addressing before merge: Critical — ESM/CJS mismatch in
|
CLAUDE.mdTool-specific guidance for Claude Code in this repository. Source of Truth
If this file conflicts with Behavioral Defaults
Git Safety
Claude-Specific WorkflowUse these docs for Claude-oriented operational guidance:
For Pro-package specifics, also read |
Review: docs: fix published setup guidance gapsOverall this is a well-scoped, low-risk docs cleanup. Changes are accurate and the direction (root-level Incomplete dead-link sweepThe PR description says it fixes links that still send readers to the dead
These can be a follow-up PR, but since the stated goal was fixing dead Pro links it's worth tracking.
|
There was a problem hiding this comment.
Actionable comments posted: 1
🧹 Nitpick comments (1)
docs/oss/building-features/node-renderer/js-configuration.md (1)
100-100: Prefer explicit npm/yarn/pnpm run commands here.Line 100 says “equivalent npm/yarn command,” but showing the exact alternatives inline improves copy/paste reliability for end users.
Based on learnings: In all end-user documentation under
docs/, package-manager-agnostic instructions should explicitly include npm, yarn, and pnpm examples.🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@docs/oss/building-features/node-renderer/js-configuration.md` at line 100, Replace the ambiguous "equivalent npm/yarn command" text and the single example "pnpm run node-renderer" with explicit, copy-pasteable commands for all supported package managers: show "pnpm run node-renderer", "npm run node-renderer", and the yarn equivalent (e.g., "yarn run node-renderer" or "yarn node-renderer") inline where the current line contains pnpm run node-renderer so readers can directly copy the exact command for their package manager.
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Inline comments:
In `@docs/oss/building-features/node-renderer/heroku.md`:
- Around line 47-50: The Windows note implies the shown script uses inline env
syntax though the package.json snippet doesn't — reword the paragraph that
mentions `RENDERER_PORT=3800` to be a general caveat: state "If you use inline
environment variable assignment (e.g., RENDERER_PORT=3800 ...) on Windows, use
cross-env or set RENDERER_PORT separately" and add a short qualifier that the
example uses a fixed port while separate Heroku apps should use
`process.env.PORT`; update the referenced sentence containing `RENDERER_PORT`
and the following sentence to this phrasing so readers won't assume the snippet
includes inline env assignment.
---
Nitpick comments:
In `@docs/oss/building-features/node-renderer/js-configuration.md`:
- Line 100: Replace the ambiguous "equivalent npm/yarn command" text and the
single example "pnpm run node-renderer" with explicit, copy-pasteable commands
for all supported package managers: show "pnpm run node-renderer", "npm run
node-renderer", and the yarn equivalent (e.g., "yarn run node-renderer" or "yarn
node-renderer") inline where the current line contains pnpm run node-renderer so
readers can directly copy the exact command for their package manager.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Organization UI
Review profile: CHILL
Plan: Pro
Run ID: 07cecf74-98cc-4b49-ab89-7a7c02a70cae
📒 Files selected for processing (3)
docs/oss/building-features/images.mddocs/oss/building-features/node-renderer/heroku.mddocs/oss/building-features/node-renderer/js-configuration.md
🚧 Files skipped from review as they are similar to previous changes (1)
- docs/oss/building-features/images.md
Review: docs: fix published setup guidance gapsGood cleanup overall. The dead pro.reactonrails.com link replacements are correct, the i18n client/package.json to root package.json fix is accurate, and replacing the manual RSC migration steps with a pointer to the generator-based runbook is the right call. Three issues worth addressing: 1. heroku.md lines 47-50 - Note references a port example that is not shown The blockquote says this fixed-port example and mentions the RENDERER_PORT=3800 inline syntax, but the package.json script shown above it is just node client/node-renderer.js with no port at all. The Windows/cross-env caveat is irrelevant to what was shown. Either add the port to the script or rewrite the note to say the default comes from the renderer config (RENDERER_PORT || 3800). Inline comment posted. 2. js-configuration.md - CJS vs ESM inconsistency The Simple example was correctly converted to CommonJS (require()), but the Custom Fastify Configuration section still uses ESM import statements. Since the prose now says the generator emits a CJS file that runs with bare node, these two sections conflict. Either convert the Fastify section to CJS or add a callout that it needs a .mjs extension or type:module in package.json. Inline comment posted. 3. images.md - indentation regression in webpack snippet The diff removed the leading space from the resolve: line but left the children indented, producing a malformed-looking code block. A fix suggestion was posted inline. |
|
Addressed the latest CodeRabbit notes in |
|
Review: docs: fix published setup guidance gaps Overall a solid documentation cleanup. The dead-link fixes, CommonJS migration, and i18n root-package.json correction are all correct and well-executed. A few focused observations: heroku.md: incomplete Procfile.web example The new text says 'keep the puma line' but never shows what that line looks like. A first-time deployer won't know the exact text (the original showed 'puma: bundle exec puma -C config/puma.rb'). Consider showing the full Procfile.web with both lines after the table. images.md: path assumption may mislead older-layout apps The example now assumes images live at app/javascript/images (Webpacker/Shakapacker layout). Apps still using the Rails asset pipeline with app/assets/images would be misled. A one-liner noting the path matches the Shakapacker generator layout and should be adjusted for other structures would prevent confusion. js-configuration.md: serverBundleCachePath depth is correct but implicit Changing ./.node-renderer-bundles to ../.node-renderer-bundles is right: with the file at client/node-renderer.js, __dirname points to client/ and ../ resolves to the app root. A brief inline comment such as 'resolves to app root: one level up from client/' would help users who place the file at a different depth. Links verified
Safe to merge. The items above are clarity suggestions, not blockers. |
|
Test comment - please ignore |
|
Test comment - please ignore - DUPLICATE TO DELETE |
Review: docs: fix published setup guidance gapsClean, well-scoped docs-only PR. The direction is correct throughout. One code-block formatting issue to fix, and a note on an existing review comment that appears to be incorrect. Inline fix needed — images.md webpack alias indentation The diff dropped a leading space from CodeRabbit's broken anchor claim is incorrect CodeRabbit requested changes citing a broken anchor Everything else looks good
|
The previous commit replaced the full Procfile.web code block with a package-manager table showing only the renderer line. This left readers without the puma line, which they need to copy-paste a working file. Adds a complete example after the table so the page remains self-contained. Co-Authored-By: Claude Opus 4.6 (1M context) <[email protected]>
## Summary - Stamped `### [16.5.1] - 2026-03-27` with two Pro fixes (PRs #2872, #2768) - Removed the `### [16.5.0.rc.0]` section (was already released as 16.5.0 stable) - Consolidated the 16.5.0 section with full entries (previously just said "no changes from rc.0") - Updated diff links at bottom of file ## Skipped PRs (docs/internal only) #2856, #2860, #2857, #2859, #2864, #2870, #2863, #2868, #2827, #2862, #2850, #2851, #2852, #2831, #2610, #2848 ## Test plan - [ ] Verify CHANGELOG.md formatting and diff links are correct - [ ] Run `rake release` (no args) after merge to publish 16.5.1 🤖 Generated with [Claude Code](https://claude.com/claude-code) <!-- CURSOR_SUMMARY --> --- > [!NOTE] > **Low Risk** > Low risk: changes are limited to `CHANGELOG.md` release notes and version/compare links with no runtime code modifications. > > **Overview** > Documents the `16.5.1` release by adding a new section under *Unreleased* with two **[Pro]** fixes (missing packaged rake tasks and avoiding duplicated bundles during remote renderer asset uploads). > > Cleans up the `16.5.0` entry by removing the `16.5.0.rc.0` section and updating the compare-link footer so `unreleased` now starts from `v16.5.1` and `16.5.0` compares from `v16.4.0`. > > <sup>Written by [Cursor Bugbot](https://cursor.com/dashboard?tab=bugbot) for commit 9a6b224. This will update automatically on new commits. Configure [here](https://cursor.com/dashboard?tab=bugbot).</sup> <!-- /CURSOR_SUMMARY --> <!-- This is an auto-generated comment: release notes by coderabbit.ai --> ## Summary by CodeRabbit * **Documentation** * Updated changelog to document version 16.5.1 release with consolidated version history and updated comparison links. <!-- end of auto-generated comment: release notes by coderabbit.ai --> Co-authored-by: Claude Opus 4.6 (1M context) <[email protected]>
…olve-2835 * origin/main: Bump version to 16.5.1 Update CHANGELOG.md for 16.5.1 (#2873) fix: include lib/tasks/ in pro gem so rake tasks are available (#2872) docs: clarify how React on Rails compares to alternatives (#2856) docs: fix published setup guidance gaps (#2860) docs: refresh setup and runtime guidance (#2857) docs: refresh pro upgrade examples (#2859) docs: modernize dependency update commands (#2864) Update spec/dummy Gemfile.lock for async >= 2.29 (#2870) # Conflicts: # CHANGELOG.md
…olve-2849 * origin/main: Bump version to 16.5.1 Update CHANGELOG.md for 16.5.1 (#2873) fix: include lib/tasks/ in pro gem so rake tasks are available (#2872) docs: clarify how React on Rails compares to alternatives (#2856) docs: fix published setup guidance gaps (#2860) docs: refresh setup and runtime guidance (#2857) docs: refresh pro upgrade examples (#2859) docs: modernize dependency update commands (#2864) Update spec/dummy Gemfile.lock for async >= 2.29 (#2870) # Conflicts: # CHANGELOG.md
…olve-2828 * origin/main: Bump version to 16.5.1 Update CHANGELOG.md for 16.5.1 (#2873) fix: include lib/tasks/ in pro gem so rake tasks are available (#2872) docs: clarify how React on Rails compares to alternatives (#2856) docs: fix published setup guidance gaps (#2860) docs: refresh setup and runtime guidance (#2857) docs: refresh pro upgrade examples (#2859) docs: modernize dependency update commands (#2864) Update spec/dummy Gemfile.lock for async >= 2.29 (#2870) # Conflicts: # CHANGELOG.md
…olve-2834 * origin/main: Bump version to 16.5.1 Update CHANGELOG.md for 16.5.1 (#2873) fix: include lib/tasks/ in pro gem so rake tasks are available (#2872) docs: clarify how React on Rails compares to alternatives (#2856) docs: fix published setup guidance gaps (#2860) docs: refresh setup and runtime guidance (#2857) docs: refresh pro upgrade examples (#2859) docs: modernize dependency update commands (#2864) Update spec/dummy Gemfile.lock for async >= 2.29 (#2870) # Conflicts: # CHANGELOG.md
…olve-2833 * origin/main: Bump version to 16.5.1 Update CHANGELOG.md for 16.5.1 (#2873) fix: include lib/tasks/ in pro gem so rake tasks are available (#2872) docs: clarify how React on Rails compares to alternatives (#2856) docs: fix published setup guidance gaps (#2860) docs: refresh setup and runtime guidance (#2857) docs: refresh pro upgrade examples (#2859) docs: modernize dependency update commands (#2864) Update spec/dummy Gemfile.lock for async >= 2.29 (#2870) # Conflicts: # CHANGELOG.md
…olve-2661 * origin/main: Clarify streaming narrative in RSC docs (#2813) (#2814) Bump version to 16.5.1 Update CHANGELOG.md for 16.5.1 (#2873) fix: include lib/tasks/ in pro gem so rake tasks are available (#2872) docs: clarify how React on Rails compares to alternatives (#2856) docs: fix published setup guidance gaps (#2860) docs: refresh setup and runtime guidance (#2857) docs: refresh pro upgrade examples (#2859) docs: modernize dependency update commands (#2864) Update spec/dummy Gemfile.lock for async >= 2.29 (#2870) # Conflicts: # docs/oss/migrating/rsc-data-fetching.md
## Summary - fix remaining live OSS docs links that still send readers to the dead `pro.reactonrails.com` destination - replace the stale manual RSC migration section in `purpose-and-benefits.md` with the current generator + Node Renderer upgrade path - refresh stale runnable setup instructions that still assume `client/package.json`, `cd client`, or a standalone `node-renderer` CLI - clarify that the images guide does not get a default `images` alias from current generators ## Why These came from another published-site walkthrough on `reactonrails.com` using persona paths: - OSS developers evaluating server rendering and configuration still hit dead Pro destinations on live pages - Pro evaluators could land on the live RSC purpose page and follow an incomplete setup path that skipped the Node Renderer prerequisite and the current `rails generate react_on_rails:rsc` workflow - existing-app integrators could copy commands from live Node Renderer, Heroku, images, and i18n pages that no longer match the current app layout or package-script conventions ## Testing - `pnpm exec prettier --check docs/oss/core-concepts/react-server-rendering.md docs/oss/configuration/README.md docs/pro/react-server-components/purpose-and-benefits.md docs/oss/building-features/node-renderer/js-configuration.md docs/oss/building-features/node-renderer/heroku.md docs/oss/building-features/images.md docs/oss/building-features/i18n.md` - `git diff --check` - `lychee --offline --no-progress --format compact docs/oss/core-concepts/react-server-rendering.md docs/oss/configuration/README.md docs/pro/react-server-components/purpose-and-benefits.md docs/oss/building-features/node-renderer/js-configuration.md docs/oss/building-features/node-renderer/heroku.md docs/oss/building-features/images.md docs/oss/building-features/i18n.md` - `pnpm run lint` - `pnpm start format.listDifferent` ## RuboCop - `bundle exec rubocop` still reports large pre-existing repo baseline failures in generated/bin and legacy files unrelated to this docs-only change <!-- CURSOR_SUMMARY --> --- > [!NOTE] > **Low Risk** > Docs-only changes that update links and setup instructions; low implementation risk, with only potential for minor confusion if any guidance is still out of date. > > **Overview** > Fixes multiple docs pages that had **stale or incorrect setup guidance** and **dead Pro links**. > > Updates i18n, images, and Node Renderer docs to match current generator layouts (root `package.json`, no default `images` alias, and running the renderer via a root `node-renderer` script rather than `cd client`/a bundled CLI), including clearer Heroku `Procfile.web` examples and port notes. > > Replaces the React Server Components “Migration Guide” section with the current generator-driven runbook (Node Renderer prerequisite + `rails generate react_on_rails:rsc`) and updates remaining `pro.reactonrails.com` links to `reactonrails.com/docs/pro`. > > <sup>Written by [Cursor Bugbot](https://cursor.com/dashboard?tab=bugbot) for commit 9a3b1bb. This will update automatically on new commits. Configure [here](https://cursor.com/dashboard?tab=bugbot).</sup> <!-- /CURSOR_SUMMARY --> <!-- This is an auto-generated comment: release notes by coderabbit.ai --> ## Summary by CodeRabbit * **Documentation** * Updated Pro links to point to dedicated Pro documentation pages * Reworked React Server Components migration guide into an infrastructure setup runbook with generator-driven setup and an upgrade checklist * Clarified i18n installation to use the project root package manifest * Updated image-asset guidance to prefer relative imports and explicit webpack aliases * Revised Node renderer and Heroku guidance to use root-level launch scripts and explicit port configuration <!-- end of auto-generated comment: release notes by coderabbit.ai --> --------- Co-authored-by: ihabadham <[email protected]> Co-authored-by: Claude Opus 4.6 (1M context) <[email protected]>
## Summary - Stamped `### [16.5.1] - 2026-03-27` with two Pro fixes (PRs #2872, #2768) - Removed the `### [16.5.0.rc.0]` section (was already released as 16.5.0 stable) - Consolidated the 16.5.0 section with full entries (previously just said "no changes from rc.0") - Updated diff links at bottom of file ## Skipped PRs (docs/internal only) #2856, #2860, #2857, #2859, #2864, #2870, #2863, #2868, #2827, #2862, #2850, #2851, #2852, #2831, #2610, #2848 ## Test plan - [ ] Verify CHANGELOG.md formatting and diff links are correct - [ ] Run `rake release` (no args) after merge to publish 16.5.1 🤖 Generated with [Claude Code](https://claude.com/claude-code) <!-- CURSOR_SUMMARY --> --- > [!NOTE] > **Low Risk** > Low risk: changes are limited to `CHANGELOG.md` release notes and version/compare links with no runtime code modifications. > > **Overview** > Documents the `16.5.1` release by adding a new section under *Unreleased* with two **[Pro]** fixes (missing packaged rake tasks and avoiding duplicated bundles during remote renderer asset uploads). > > Cleans up the `16.5.0` entry by removing the `16.5.0.rc.0` section and updating the compare-link footer so `unreleased` now starts from `v16.5.1` and `16.5.0` compares from `v16.4.0`. > > <sup>Written by [Cursor Bugbot](https://cursor.com/dashboard?tab=bugbot) for commit 9a6b224. This will update automatically on new commits. Configure [here](https://cursor.com/dashboard?tab=bugbot).</sup> <!-- /CURSOR_SUMMARY --> <!-- This is an auto-generated comment: release notes by coderabbit.ai --> ## Summary by CodeRabbit * **Documentation** * Updated changelog to document version 16.5.1 release with consolidated version history and updated comparison links. <!-- end of auto-generated comment: release notes by coderabbit.ai --> Co-authored-by: Claude Opus 4.6 (1M context) <[email protected]>
2 participants
Summary
pro.reactonrails.comdestinationpurpose-and-benefits.mdwith the current generator + Node Renderer upgrade pathclient/package.json,cd client, or a standalonenode-rendererCLIimagesalias from current generatorsWhy
These came from another published-site walkthrough on
reactonrails.comusing persona paths:rails generate react_on_rails:rscworkflowTesting
pnpm exec prettier --check docs/oss/core-concepts/react-server-rendering.md docs/oss/configuration/README.md docs/pro/react-server-components/purpose-and-benefits.md docs/oss/building-features/node-renderer/js-configuration.md docs/oss/building-features/node-renderer/heroku.md docs/oss/building-features/images.md docs/oss/building-features/i18n.mdgit diff --checklychee --offline --no-progress --format compact docs/oss/core-concepts/react-server-rendering.md docs/oss/configuration/README.md docs/pro/react-server-components/purpose-and-benefits.md docs/oss/building-features/node-renderer/js-configuration.md docs/oss/building-features/node-renderer/heroku.md docs/oss/building-features/images.md docs/oss/building-features/i18n.mdpnpm run lintpnpm start format.listDifferentRuboCop
bundle exec rubocopstill reports large pre-existing repo baseline failures in generated/bin and legacy files unrelated to this docs-only changeNote
Low Risk
Docs-only changes that update links and setup instructions; low implementation risk, with only potential for minor confusion if any guidance is still out of date.
Overview
Fixes multiple docs pages that had stale or incorrect setup guidance and dead Pro links.
Updates i18n, images, and Node Renderer docs to match current generator layouts (root
package.json, no defaultimagesalias, and running the renderer via a rootnode-rendererscript rather thancd client/a bundled CLI), including clearer HerokuProcfile.webexamples and port notes.Replaces the React Server Components “Migration Guide” section with the current generator-driven runbook (Node Renderer prerequisite +
rails generate react_on_rails:rsc) and updates remainingpro.reactonrails.comlinks toreactonrails.com/docs/pro.Written by Cursor Bugbot for commit 9a3b1bb. This will update automatically on new commits. Configure here.
Summary by CodeRabbit