Pin react-on-rails-rsc to stable 19.0.5 (#3634)

Stable react-on-rails-rsc@19.0.5 is now published on npm latest, so flip
every default/published pin from the 19.0.5-rc.7 prerelease to the stable
19.0.5 release. This is the v17 final pin.

- Generator default RSC_PACKAGE_VERSION_PIN -> "19.0.5"; reword the pin
  comment to stable framing and drop the resolved TODO(#3642).
- Update js_dependency_manager_spec assertions and warning-text/literal
  expectations from 19.0.5-rc.7 to 19.0.5 (the unrelated 19.1.0-rc.1
  stub_const is left as-is).
- Root package.json devDependency and pnpm-overrides comment, plus the
  Pro package devDependency, now pin 19.0.5.
- Regenerate pnpm-lock.yaml: the react-on-rails-rsc 19.0.5-rc.7 entries
  become 19.0.5; the intentional 19.2.0-rc.1 soak entries are untouched.
- Reword the Pro RSC install docs (rspack-compatibility, create-without-ssr,
  upgrading-existing-pro-app) to state stable 19.0.5 is the pin.
- Regenerate llms-full-pro.txt to mirror the Pro doc edits.
- Add a [Unreleased] CHANGELOG entry; note the native RSC CSS FOUC fix
  requires react-on-rails-rsc >= 19.0.5.

Intentionally left untouched: the React 19.2 soak pins
(react_on_rails_pro_dummy override + Pro dummy package, 19.2.0-rc.1 /
react 19.2.7), the Pro package peerDependencies "*", and the node-renderer
RSC peer-support files.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>

Author: justin808

CHANGELOG.md

@@ -28,6 +28,10 @@ After a release, run `/update-changelog` in Claude Code to analyze commits, writ
 
 - **Owner Stacks in development error reports**: When a React component throws during rendering, React on Rails now enriches its development error reporting with React 19.1+'s dev-only [`captureOwnerStack`](https://react.dev/reference/react/captureOwnerStack) output — the chain of components that rendered the failing one (e.g. `at Avatar` / `at PostCard` / `at PostList`). On the **server-side rendering** path, the owner stack is captured synchronously inside the Pro streaming `onError` callback and appended to the error's stack, so it flows through to the Rails-side `ReactOnRails::PrerenderError` / `SmartError` (`:server_rendering_error`) output and the streamed shell-error HTML. On the **client**, recoverable hydration mismatches (`onRecoverableError`) automatically gain an owner-stack line in the branded development log, and apps that register their own `onCaughtError`/`onUncaughtError` handler get an additive `[ReactOnRails] Render error ... Owner stack:` line for client render errors. To avoid displacing React's own built-in development diagnostics (component stacks, error-boundary hints), React on Rails does not auto-attach caught/uncaught handlers solely to log owner stacks. Owner-stack capture requires React >= 19.1 running its development build, so it is a strict no-op on older React and in all production builds (no capture, no `captureOwnerStack` call), asserted by tests. The ExecJS rendering path is out of scope (capture must happen JS-side, synchronously, inside React's error callback). Closes [Issue 3887](https://github.com/shakacode/react_on_rails/issues/3887). [PR 4089](https://github.com/shakacode/react_on_rails/pull/4089) by [justin808](https://github.com/justin808).
 
+#### Changed
+
+- **[Pro]** **Pinned `react-on-rails-rsc` to the stable `19.0.5` release**: The generator default, the root and Pro package manifests, the lockfile, and the Pro RSC install docs now pin the stable `react-on-rails-rsc@19.0.5` (previously the `19.0.5-rc.7` prerelease). The native RSC CSS FOUC fix requires `react-on-rails-rsc >= 19.0.5`. Closes [Issue 3634](https://github.com/shakacode/react_on_rails/issues/3634). [PR 4080](https://github.com/shakacode/react_on_rails/pull/4080) by [justin808](https://github.com/justin808).
+
 ### [17.0.0.rc.5] - 2026-06-16
 
 #### Fixed

docs/pro/react-server-components/create-without-ssr.md

@@ -23,19 +23,19 @@ yarn add --exact react-on-rails-pro@VERSION
 bundle add react_on_rails_pro --version="= VERSION"
 ```
 
-Also, install React 19.0.x, React DOM 19.0.x, and the exact `react-on-rails-rsc` release candidate currently used by the generator:
+Also, install React 19.0.x, React DOM 19.0.x, and the exact `react-on-rails-rsc` release currently used by the generator:
 
 ```bash
-yarn add react@~19.0.4 react-dom@~19.0.4 react-on-rails-rsc@19.0.5-rc.7
-# npm install react@~19.0.4 react-dom@~19.0.4 react-on-rails-rsc@19.0.5-rc.7
-# pnpm add react@~19.0.4 react-dom@~19.0.4 react-on-rails-rsc@19.0.5-rc.7
-# bun add react@~19.0.4 react-dom@~19.0.4 react-on-rails-rsc@19.0.5-rc.7
+yarn add react@~19.0.4 react-dom@~19.0.4 react-on-rails-rsc@19.0.5
+# npm install react@~19.0.4 react-dom@~19.0.4 react-on-rails-rsc@19.0.5
+# pnpm add react@~19.0.4 react-dom@~19.0.4 react-on-rails-rsc@19.0.5
+# bun add react@~19.0.4 react-dom@~19.0.4 react-on-rails-rsc@19.0.5
 ```
 
 > [!NOTE]
 > React on Rails Pro RSC currently supports React 19.0.x with patch >= 19.0.4. Do not upgrade generated RSC apps to React 19.1 or 19.2 just because those versions are newer on npm; the RSC bundler APIs used internally can change between React minor versions. See the [React documentation on Server Components](https://react.dev/reference/rsc/server-components#how-do-i-build-support-for-server-components) for details.
 >
-> The example above pins `react-on-rails-rsc@19.0.5-rc.7`, a release candidate. Keep that exact pin until a stable `react-on-rails-rsc@19.0.5` release is published and the generator/package metadata policy is reviewed together.
+> The example above pins the stable `react-on-rails-rsc@19.0.5` release exactly, matching the generator default.
 
 2. Enable support for Server Components in React on Rails Pro configuration:
 

docs/pro/react-server-components/rspack-compatibility.md

@@ -12,7 +12,7 @@ The generator supports Rspack — when `assets_bundler: rspack` is detected in `
 The RSC implementation depends on the `react-on-rails-rsc` npm package, which provides bundler-specific manifest plugins plus a shared loader:
 
 - **WebpackPlugin** (`react-on-rails-rsc/WebpackPlugin`) — generates client/server component manifest files under webpack.
-- **RspackPlugin** (`react-on-rails-rsc/RspackPlugin`) — the rspack-native equivalent (`RSCRspackPlugin`). It emits the **same manifest JSON schema** using only standard rspack public APIs, so the RSC runtime resolves client references identically. Exported by the exact `react-on-rails-rsc@19.0.5-rc.7` pin (switch to 19.0.5 stable once published).
+- **RspackPlugin** (`react-on-rails-rsc/RspackPlugin`) — the rspack-native equivalent (`RSCRspackPlugin`). It emits the **same manifest JSON schema** using only standard rspack public APIs, so the RSC runtime resolves client references identically. Exported by the stable `react-on-rails-rsc@19.0.5` pin.
 - **WebpackLoader** (`react-on-rails-rsc/WebpackLoader`) — transforms `'use client'` files into client reference proxies in the RSC bundle. Works under both webpack and rspack.
 
 ## React and Package Version Policy
@@ -24,8 +24,8 @@ integration can change between React minor releases, so the generator range shou
 advance only after the Webpack and Rspack paths are verified against the new React
 minor.
 
-The generator separately pins `react-on-rails-rsc@19.0.5-rc.7` exactly until a
-stable `react-on-rails-rsc@19.0.5` is published. That package pin is separate from
+The generator separately pins the stable `react-on-rails-rsc@19.0.5` release
+exactly. That package pin is separate from
 the Pro package peer metadata tracked in [issue #3609](https://github.com/shakacode/react_on_rails/issues/3609):
 metadata can allow prerelease RSC packages broadly enough for `npm ls`, while the
 generator still installs the tested React range and exact RSC package pin.

docs/pro/react-server-components/upgrading-existing-pro-app.md

@@ -15,17 +15,17 @@ Before running the generator, verify your environment:
 | React on Rails Pro npm   | `npm ls react-on-rails-pro` / `yarn why react-on-rails-pro` / `pnpm list react-on-rails-pro` / `bun pm why react-on-rails-pro` | Matches gem version                                                                                                         |
 | React version            | `npm ls react` / `yarn why react` / `pnpm list react` / `bun pm why react`                                                     | 19.0.x with patch >= 19.0.4 (see [v16.2.0 release notes](../../oss/upgrading/release-notes/16.2.0.md) for security context) |
 | React DOM version        | `npm ls react-dom` / `yarn why react-dom` / `pnpm list react-dom` / `bun pm why react-dom`                                     | Must match `react` version                                                                                                  |
-| `react-on-rails-rsc`     | `npm ls react-on-rails-rsc` / `yarn why react-on-rails-rsc` / `pnpm list react-on-rails-rsc` / `bun pm why react-on-rails-rsc` | Exact `19.0.5-rc.7` pin until stable `19.0.5` ships                                                                         |
+| `react-on-rails-rsc`     | `npm ls react-on-rails-rsc` / `yarn why react-on-rails-rsc` / `pnpm list react-on-rails-rsc` / `bun pm why react-on-rails-rsc` | Exact stable `19.0.5` pin                                                                                                   |
 | Node.js                  | `node --version`                                                                                                               | 18+                                                                                                                         |
 | Pro initializer exists   | `ls config/initializers/react_on_rails_pro.rb`                                                                                 | File exists                                                                                                                 |
 | Node renderer configured | Check `react_on_rails_pro.rb` for `server_renderer = "NodeRenderer"`                                                           | NodeRenderer enabled                                                                                                        |
 
 If React is outside the supported 19.0.x range or below 19.0.4, upgrade it first:
 
 ```bash
-pnpm add react@~19.0.4 react-dom@~19.0.4 react-on-rails-rsc@19.0.5-rc.7
-# or: yarn add react@~19.0.4 react-dom@~19.0.4 react-on-rails-rsc@19.0.5-rc.7
-# or: npm install react@~19.0.4 react-dom@~19.0.4 react-on-rails-rsc@19.0.5-rc.7
+pnpm add react@~19.0.4 react-dom@~19.0.4 react-on-rails-rsc@19.0.5
+# or: yarn add react@~19.0.4 react-dom@~19.0.4 react-on-rails-rsc@19.0.5
+# or: npm install react@~19.0.4 react-dom@~19.0.4 react-on-rails-rsc@19.0.5
 ```
 
 > **React 19.0.x with patch >= 19.0.4** is recommended. Earlier 19.0.x versions (19.0.0--19.0.3) have known security vulnerabilities — see the [v16.2.0 release notes](../../oss/upgrading/release-notes/16.2.0.md) for details.
@@ -34,7 +34,7 @@ pnpm add react@~19.0.4 react-dom@~19.0.4 react-on-rails-rsc@19.0.5-rc.7
 > The RSC generator intentionally stays on React 19.0.x and does not widen generated apps to React 19.1 or 19.2 yet. React's RSC runtime and bundler APIs can change between minor releases, so advance the React range only when the generator, docs, and package metadata policy are reviewed together.
 
 > [!NOTE]
-> `react-on-rails-rsc@19.0.5-rc.7` is an exact release-candidate pin. Keep that exact pin until a stable `react-on-rails-rsc@19.0.5` release is available. This is separate from the Pro package peer metadata tracked in [issue #3609](https://github.com/shakacode/react_on_rails/issues/3609): metadata can allow prerelease RSC packages broadly enough for `npm ls`, while the generator still installs the tested exact RSC package pin.
+> `react-on-rails-rsc@19.0.5` is the exact stable pin used by the generator. This is separate from the Pro package peer metadata tracked in [issue #3609](https://github.com/shakacode/react_on_rails/issues/3609): metadata can allow RSC packages broadly enough for `npm ls`, while the generator still installs the tested exact RSC package pin.
 
 ## Pre-Migration: Audit Components for Client API Usage
 
@@ -263,8 +263,8 @@ Then run `bundle install` before retrying the generator.
 
 If the RSC bundle build fails but server and client builds succeed, the issue is likely in `rscWebpackConfig.js`. Common causes:
 
-- **Missing `react-on-rails-rsc` package**: Run `pnpm add react-on-rails-rsc@19.0.5-rc.7`
-- **React or `react-on-rails-rsc` version mismatch**: RSC currently requires React 19.0.x with patch >= 19.0.4 and the exact `react-on-rails-rsc@19.0.5-rc.7` pin. Check with `pnpm list react react-dom react-on-rails-rsc`
+- **Missing `react-on-rails-rsc` package**: Run `pnpm add react-on-rails-rsc@19.0.5`
+- **React or `react-on-rails-rsc` version mismatch**: RSC currently requires React 19.0.x with patch >= 19.0.4 and the exact `react-on-rails-rsc@19.0.5` pin. Check with `pnpm list react react-dom react-on-rails-rsc`
 - **Custom webpack config incompatibility**: If your `serverWebpackConfig.js` was heavily customized, the generator's transforms may not apply cleanly. See [Preparing Your App: Step 4](../../oss/migrating/rsc-preparing-app.md#step-4-set-up-the-rsc-webpack-bundle) for the underlying intent of each webpack change
 
 ### Manifest Files Not Generated