Update React on Rails to 17.0.0.rc.3 (#163)

Update React on Rails and React on Rails Pro packages/gems to RC3, refresh lockfiles, and update current RC stack docs.\n\nLocal verification:\n- bundle update react_on_rails react_on_rails_pro\n- pnpm install\n- pnpm run test:router-shim\n- pnpm run repro:rspack-rsc\n- bin/test smoke\n- bin/test production-precompile\n\nGitHub checks passed for head 0072ce4.

Author: justin808

Gemfile

@@ -65,9 +65,9 @@ group :test do
   gem "selenium-webdriver"
 end
 
-gem "react_on_rails", "17.0.0.rc.2"
+gem "react_on_rails", "17.0.0.rc.3"
 
-gem "react_on_rails_pro", "17.0.0.rc.2"
+gem "react_on_rails_pro", "17.0.0.rc.3"
 
 gem "shakapacker", "10.1.0"
 

Gemfile.lock

@@ -123,7 +123,7 @@ GEM
       logger (~> 1.5)
     concurrent-ruby (1.3.6)
     connection_pool (3.0.2)
-    console (1.35.1)
+    console (1.36.0)
       fiber-annotation
       fiber-local (~> 1.1)
       json
@@ -170,7 +170,7 @@ GEM
     jbuilder (2.15.1)
       actionview (>= 7.0.0)
       activesupport (>= 7.0.0)
-    json (2.19.7)
+    json (2.19.9)
     jwt (3.2.0)
       base64
     kamal (2.11.0)
@@ -215,7 +215,7 @@ GEM
       drb (~> 2.0)
       prism (~> 1.5)
     msgpack (1.8.0)
-    net-imap (0.6.4)
+    net-imap (0.6.4.1)
       date
       net-protocol
     net-pop (0.1.2)
@@ -272,7 +272,7 @@ GEM
       protocol-hpack (~> 1.4)
       protocol-http (~> 0.62)
     protocol-url (0.4.0)
-    psych (5.3.1)
+    psych (5.4.0)
       date
       stringio
     public_suffix (7.0.5)
@@ -328,22 +328,22 @@ GEM
       erb
       psych (>= 4.0.0)
       tsort
-    react_on_rails (17.0.0.rc.2)
+    react_on_rails (17.0.0.rc.3)
       addressable
       connection_pool
       execjs (~> 2.5)
       rails (>= 5.2)
       rainbow (~> 3.0)
       shakapacker (>= 6.0)
-    react_on_rails_pro (17.0.0.rc.2)
+    react_on_rails_pro (17.0.0.rc.3)
       addressable
       async (>= 2.29)
       async-http (~> 0.95)
       execjs (~> 2.9)
       io-endpoint (~> 0.17.0)
       jwt (>= 2.5, < 4)
       rainbow
-      react_on_rails (= 17.0.0.rc.2)
+      react_on_rails (= 17.0.0.rc.3)
     regexp_parser (2.12.0)
     reline (0.6.3)
       io-console (~> 0.5)
@@ -453,7 +453,7 @@ GEM
       bindex (>= 0.4.0)
       railties (>= 8.0.0)
     websocket (1.2.11)
-    websocket-driver (0.8.0)
+    websocket-driver (0.8.1)
       base64
       websocket-extensions (>= 0.1.0)
     websocket-extensions (0.1.5)
@@ -491,8 +491,8 @@ DEPENDENCIES
   puma (>= 5.0)
   rack-attack (~> 6.8)
   rails (~> 8.1.3)
-  react_on_rails (= 17.0.0.rc.2)
-  react_on_rails_pro (= 17.0.0.rc.2)
+  react_on_rails (= 17.0.0.rc.3)
+  react_on_rails_pro (= 17.0.0.rc.3)
   rspec-rails (~> 8.0)
   rubocop-rails-omakase
   selenium-webdriver

README.md

@@ -83,7 +83,7 @@ via `SHAKAPACKER_ASSETS_BUNDLER=webpack`.
 
 | Component | Version |
 | --- | --- |
-| React on Rails / Pro | `17.0.0.rc.2` |
+| React on Rails / Pro | `17.0.0.rc.3` |
 | Shakapacker / Shakapacker Rspack | `10.1.0` |
 | React | `19.0.6` |
 | Rails | `8.1.x` |

SPIKE.md

@@ -15,7 +15,7 @@ The remaining limitation is separate from the bundler: `/hello_server`'s client
 island still waits on the upstream React on Rails Pro streaming CSP nonce fix in
 strict production CSP mode. See `docs/11-rsc-csp-nonce-spike.md`.
 
-The app was bootstrapped with `create-react-on-rails-app --rsc --rspack --package-manager pnpm` and the current release stack targets React on Rails Pro `17.0.0-rc.2` with Shakapacker `10.1.0`. Shakapacker stays on `10.1.0` because public `11.1.0` artifacts are not visible in the registries consumed by the starter. The Rails/Rspack/React on Rails Pro setup passes `react_on_rails:doctor` with the expected warning that both Rspack and Webpack configs are present.
+The app was bootstrapped with `create-react-on-rails-app --rsc --rspack --package-manager pnpm` and the current release stack targets React on Rails Pro `17.0.0-rc.3` with Shakapacker `10.1.0`. Shakapacker stays on `10.1.0` because public `11.1.0` artifacts are not visible in the registries consumed by the starter. The Rails/Rspack/React on Rails Pro setup passes `react_on_rails:doctor` with the expected warning that both Rspack and Webpack configs are present.
 
 ## Validation Goals
 
@@ -27,7 +27,7 @@ The app was bootstrapped with `create-react-on-rails-app --rsc --rspack --packag
 ## What Worked
 
 - Rails 8.1 app scaffolded with PostgreSQL and SolidQueue.
-- React on Rails and React on Rails Pro release stack: `17.0.0.rc.2`.
+- React on Rails and React on Rails Pro release stack: `17.0.0.rc.3`.
 - Shakapacker launch stack: `10.1.0`.
 - Rspack builds complete successfully and emit the RSC client-reference
   manifests with `react-on-rails-rsc@19.0.5-rc.2`.
@@ -45,7 +45,7 @@ manifests present.
 Current stance:
 
 - Keep Rspack as the bundler.
-- Keep the React on Rails Pro `17.0.0-rc.2` and Shakapacker `10.1.0` release stack.
+- Keep the React on Rails Pro `17.0.0-rc.3` and Shakapacker `10.1.0` release stack.
 - Keep the Rspack/RSC client boundary repro in `pnpm run repro:rspack-rsc`.
 - Keep direct Rspack packages aligned with the Shakapacker Rspack 2 adapter: `@rspack/core` / `@rspack/cli` `2.0.4` and `@rspack/dev-server` `2.0.1`.
 - Keep `react-on-rails-rsc` on `19.0.5-rc.7` or newer when requiring Rspack RSC

docs/01-architecture.md

@@ -1,6 +1,6 @@
 # Architecture
 
-This starter begins from `create-react-on-rails-app --rsc --rspack` and currently targets the React on Rails Pro `17.0.0-rc.2` RC stack with Shakapacker `10.1.0`.
+This starter begins from `create-react-on-rails-app --rsc --rspack` and currently targets the React on Rails Pro `17.0.0-rc.3` RC stack with Shakapacker `10.1.0`.
 
 Shakapacker remains on `10.1.0` because public `11.1.0` artifacts are not visible in the registries this starter consumes. Rspack is the checked-in local and deploy default. `react-on-rails-rsc@19.0.5-rc.7` provides the Rspack RSC manifest support this starter needs, while Webpack remains an opt-in bridge/comparison path.
 

docs/06-tested-modes.md

@@ -1,7 +1,7 @@
 # Tested Modes
 
 This starter keeps the TanStack dashboard on Rspack and the launch RC stack:
-React on Rails Pro `17.0.0-rc.2` with Shakapacker `10.1.0`.
+React on Rails Pro `17.0.0-rc.3` with Shakapacker `10.1.0`.
 Shakapacker is intentionally not documented as `11.1.0` because public
 `11.1.0` artifacts are not visible in the registries consumed by the starter.
 Rspack is the default local and deploy bundler in the checked-in matrix.

package.json

@@ -44,8 +44,8 @@
     "prop-types": "15.8.1",
     "react": "19.0.6",
     "react-dom": "19.0.6",
-    "react-on-rails-pro": "17.0.0-rc.2",
-    "react-on-rails-pro-node-renderer": "17.0.0-rc.2",
+    "react-on-rails-pro": "17.0.0-rc.3",
+    "react-on-rails-pro-node-renderer": "17.0.0-rc.3",
     "react-on-rails-rsc": "19.0.5-rc.7",
     "rspack-manifest-plugin": "5.2.1",
     "sass": "1.99.0",

pnpm-lock.yaml

@@ -11,7 +11,7 @@ overrides:
 minimumReleaseAgeExclude:
   - shakapacker-rspack@10.1.0
   - shakapacker@10.1.0
-  - react-on-rails-pro-node-renderer@17.0.0-rc.2
-  - react-on-rails-pro@17.0.0-rc.2
-  - react-on-rails@17.0.0-rc.2
+  - react-on-rails-pro-node-renderer@17.0.0-rc.3
+  - react-on-rails-pro@17.0.0-rc.3
+  - react-on-rails@17.0.0-rc.3
   - react-on-rails-rsc