shakacode/react_on_rails v17.2.0.rc.2

on GitHub

Changed

• [Pro] React 19.3 support now requires stable react-on-rails-rsc 19.3.1: The Pro packages build and
  test against stable react-on-rails-rsc 19.3.1 (npm latest) with React/React DOM 19.3.0, replacing the
  19.3.1-rc.0 release candidate that 17.2.0.rc.0 and 17.2.0.rc.1 used. The react-on-rails-pro optional peer
  range is >=19.2.1 <20.0.0 again; the temporary ~19.3.1-rc.0 alternative is removed. The node renderer
  startup check and react_on_rails:doctor accept only stable react-on-rails-rsc releases: 19.2.x with
  React 19.2.7+, 19.3.0 with React 19.2.8+, and 19.3.x from 19.3.1 with React 19.3.x. Action required for upgraders:
  apps that installed react-on-rails-rsc 19.3.1-rc.0 or 19.3.1-rc.1 while testing a 17.2.0 release candidate
  must install stable 19.3.1 (React/React DOM stay on 19.3.0). The node renderer refuses those prereleases at
  startup, and both its error and Doctor's Fix name 19.3.1. Apps on stable 19.2.x or 19.3.0 need no change.
  #5162 by
  justin808.

• [Pro] New RSC apps install the React 19.3 line: rails g react_on_rails:install --rsc,
  rails g react_on_rails:rsc, and create-react-on-rails-app --rsc now install react-on-rails-rsc 19.3.1 with
  react@~19.3.0 and react-dom@~19.3.0. The 17.0 generator installed react-on-rails-rsc 19.2.1 with
  React 19.2.7, and apps on that set keep working unchanged. Apps generated by 17.1.0 pin the superseded
  19.3.0-rc.4, which the node renderer refuses at startup: install react-on-rails-rsc 19.3.0 with React/React DOM
  19.2.8+, or 19.3.1 with React/React DOM 19.3.0. Running
  rails g react_on_rails:rsc on an existing Pro app that is still on React 19.2.x now warns that the installed
  react-on-rails-rsc 19.3.1 needs React 19.3.x; upgrade React and React DOM to ~19.3.0, or keep React 19.2.x
  and pin react-on-rails-rsc@19.2.1 yourself. When Doctor has no closer match, its Fix now recommends the same
  19.3.1 / React 19.3.0 set the generator installs.
  #5164 by
  justin808.

Fixed

• [Pro] Doctor no longer reports a superseded prerelease as newer: react_on_rails:doctor warned that
  an installed stable react-on-rails-rsc was behind the npm next dist-tag even when next pointed at a
  release candidate that stable latest had already replaced (for example next 19.3.1-rc.1 with latest
  19.3.1), a prerelease this version rejects. Doctor now skips a next or rc tag that is not newer than
  latest.
  #5164 by
  justin808.

• [Pro] Rejected react-on-rails-rsc prereleases now say why: When the node renderer startup check or
  react_on_rails:doctor rejects a prerelease such as 19.3.2-rc.0, the message now reads
  >= 19.2.1 (stable releases only). The previous >= 19.2.1 label was satisfied by the prerelease it rejected.
  #5168 by
  justin808.