Skip to content

Update React on Rails 17.0.0-rc.2 stack#765

Merged
justin808 merged 1 commit into
masterfrom
jg-codex/ror-17-rc2-legacy-tutorial
Jun 11, 2026
Merged

Update React on Rails 17.0.0-rc.2 stack#765
justin808 merged 1 commit into
masterfrom
jg-codex/ror-17-rc2-legacy-tutorial

Conversation

@justin808

@justin808 justin808 commented Jun 11, 2026

Copy link
Copy Markdown
Member

Summary

Updates the legacy source-backed tutorial app to the React on Rails 17.0.0-rc.2 release stack for the React on Rails 17 RC batch.

References shakacode/react_on_rails#3898.

Updated versions

  • react_on_rails gem: 17.0.0.rc.2 via react_on_rails_pro
  • react_on_rails_pro gem: 17.0.0.rc.2
  • react-on-rails npm package: 17.0.0-rc.2 via react-on-rails-pro
  • react-on-rails-pro npm package: 17.0.0-rc.2
  • react-on-rails-pro-node-renderer npm package: 17.0.0-rc.2
  • react-on-rails-rsc npm package: 19.0.5-rc.7
  • shakapacker remains at 10.1.0

Verification

  • bin/conductor-exec bundle install -> passed
  • bin/conductor-exec yarn install -> passed
  • bin/conductor-exec bundle check -> passed
  • bin/conductor-exec yarn install --frozen-lockfile --non-interactive -> passed
  • git diff --check -> passed
  • bin/conductor-exec bundle exec rubocop -> passed, 57 files inspected, no offenses
  • bin/conductor-exec yarn test:client -> passed, 4 suites / 16 tests
  • bin/conductor-exec bundle exec rake react_on_rails:locale && RAILS_ENV=test bin/conductor-exec bin/rails react_on_rails:generate_packs && bin/conductor-exec yarn res:build && bin/conductor-exec yarn build:test -> passed, webpack completed with existing DefinePlugin warnings
  • bin/conductor-exec yarn lint:eslint -> failed on existing JS/format/generated-pack lint violations unrelated to this dependency-only diff
  • bin/conductor-exec yarn lint:prettier -> failed on existing formatting differences unrelated to this dependency-only diff
  • RAILS_ENV=test bin/conductor-exec bundle exec rails db:prepare && bin/conductor-exec bundle exec rspec -> failed after DB setup because the Pro Node renderer was not running on 127.0.0.1:3800 with matching RENDERER_PASSWORD; 47/48 failures were renderer auth/connection failures

Notes

Local version confirmation:

  • Bundler lock: react_on_rails 17.0.0.rc.2, react_on_rails_pro 17.0.0.rc.2, shakapacker 10.1.0
  • Yarn lock: react-on-rails 17.0.0-rc.2, react-on-rails-pro 17.0.0-rc.2, react-on-rails-pro-node-renderer 17.0.0-rc.2, react-on-rails-rsc 19.0.5-rc.7, shakapacker 10.1.0

Note

Medium Risk
Major-version bump of SSR/RSC integration gems and npm packages can change renderer behavior; scope is limited to version pins with verified bundle/client tests but full RSpec needs the Pro Node renderer running.

Overview
Bumps the tutorial app to the React on Rails 17.0.0-rc.2 release line across Ruby and JavaScript, with no application source changes.

Ruby: react_on_rails_pro in Gemfile moves from 16.7.0.rc.3 to 17.0.0.rc.2, which pulls react_on_rails to the same version in Gemfile.lock.

npm: react-on-rails-pro, react-on-rails-pro-node-renderer, and transitive react-on-rails go to 17.0.0-rc.2; react-on-rails-rsc goes from 19.0.5-rc.6 to 19.0.5-rc.7. shakapacker stays at 10.1.0.

Docs: README.md version targets are updated to match the new pins.

Reviewed by Cursor Bugbot for commit 4c1bbe3. Bugbot is set up for automated code reviews on this repo. Configure here.

Summary by CodeRabbit

  • Chores
    • Updated React on Rails Pro framework dependencies to version 17.0.0-rc.2 (includes Ruby gem and npm packages)
    • Updated React on Rails RSC package to version 19.0.5-rc.7
    • Updated project documentation to reflect new dependency versions and targets

@github-actions

Copy link
Copy Markdown

🚀 Quick Review App Commands

Welcome! Here are the commands you can use in this PR:
They require the repository to have cpflow review apps configured, including the CPLN_TOKEN_STAGING secret.

+review-app-deploy

Deploy your PR branch for testing.

+review-app-delete

Remove the review app when done.

+review-app-help

Show detailed instructions, environment setup, and configuration options.

Comment +review-app-help for full setup details.

@coderabbitai

coderabbitai Bot commented Jun 11, 2026

Copy link
Copy Markdown

Review Change Stack

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 8578c787-8b9a-42ca-88cf-28bcb8a24a23

📥 Commits

Reviewing files that changed from the base of the PR and between e8cdeb4 and 4c1bbe3.

⛔ Files ignored due to path filters (2)
  • Gemfile.lock is excluded by !**/*.lock
  • yarn.lock is excluded by !**/yarn.lock, !**/*.lock
📒 Files selected for processing (3)
  • Gemfile
  • README.md
  • package.json

Walkthrough

This PR updates the React-on-Rails ecosystem package versions across dependency manifests and documentation. The react_on_rails_pro gem and corresponding npm packages are bumped to 17.0.0.rc.2, and react-on-rails-rsc is advanced to 19.0.5-rc.7.

Changes

Dependency Version Update

Layer / File(s) Summary
Gemfile and package.json dependency versions
Gemfile, package.json
Gemfile upgrades react_on_rails_pro gem to 17.0.0.rc.2; package.json updates react-on-rails-pro and react-on-rails-pro-node-renderer to 17.0.0-rc.2 and advances react-on-rails-rsc to 19.0.5-rc.7.
Version targets documentation
README.md
"Version Targets" section lists the updated versions: react_on_rails_pro and react-on-rails-pro* at 17.0.0.rc.2, and react-on-rails-rsc at 19.0.5-rc.7.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Possibly related PRs

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title accurately summarizes the primary change: updating the React on Rails stack to version 17.0.0-rc.2 across multiple files and dependencies.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch jg-codex/ror-17-rc2-legacy-tutorial

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

Comment @coderabbitai help to get the list of available commands and usage tips.

@greptile-apps

greptile-apps Bot commented Jun 11, 2026

Copy link
Copy Markdown

Greptile Summary

This is a dependency-only version bump from 16.7.0.rc.3 to 17.0.0.rc.2 for the React on Rails Pro stack, with react-on-rails-rsc advancing from rc.6 to rc.7. All five changed files — Gemfile, Gemfile.lock, README.md, package.json, and yarn.lock — are internally consistent with one another.

  • Gemfile / Gemfile.lock: react_on_rails_pro and its transitive react_on_rails dependency are both bumped to 17.0.0.rc.2; the lock file's pinned constraint (react_on_rails (= 17.0.0.rc.2)) matches exactly.
  • package.json / yarn.lock: react-on-rails-pro, react-on-rails-pro-node-renderer, and react-on-rails-rsc are all updated with new resolved hashes and integrity digests that correspond to the published packages on the npm registry.
  • README.md: Version targets table updated to reflect the new versions and adds the previously unlisted react-on-rails-rsc entry.

Confidence Score: 5/5

This is a clean dependency-only bump; all five files are internally consistent and no logic was modified.

Every changed file is a version manifest or documentation update. The Gemfile, Gemfile.lock, package.json, and yarn.lock are mutually consistent — pinned constraints match resolved versions, and the yarn.lock hashes correspond to published packages. No application code, configuration logic, or migration files were touched. The known test failures noted in the PR description are infrastructure-related (the Pro Node renderer not running locally) rather than regressions introduced by this diff.

No files require special attention.

Important Files Changed

Filename Overview
Gemfile Single-line bump of react_on_rails_pro from 16.7.0.rc.3 to 17.0.0.rc.2; consistent with lock file.
Gemfile.lock react_on_rails and react_on_rails_pro both updated to 17.0.0.rc.2; pinned constraint in DEPENDENCIES section matches Gemfile.
package.json react-on-rails-pro, react-on-rails-pro-node-renderer bumped to 17.0.0-rc.2 and react-on-rails-rsc bumped to 19.0.5-rc.7; consistent with yarn.lock.
yarn.lock All four npm package entries updated with new resolved URLs and integrity hashes matching the stated versions.
README.md Version Targets table updated to reflect new RC versions; react-on-rails-rsc entry added for completeness.

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart TD
    A[PR: Update RoR 17.0.0-rc.2 stack] --> B[Ruby / Gem changes]
    A --> C[JS / npm changes]

    B --> B1["Gemfile\nreact_on_rails_pro 16.7.0.rc.3 → 17.0.0.rc.2"]
    B1 --> B2["Gemfile.lock\nreact_on_rails 17.0.0.rc.2\nreact_on_rails_pro 17.0.0.rc.2"]

    C --> C1["package.json\nreact-on-rails-pro 17.0.0-rc.2\nreact-on-rails-pro-node-renderer 17.0.0-rc.2\nreact-on-rails-rsc 19.0.5-rc.7"]
    C1 --> C2["yarn.lock\nAll 4 packages: new resolved URLs + integrity hashes"]

    A --> D[Docs]
    D --> D1["README.md\nVersion Targets table updated\nreact-on-rails-rsc entry added"]
Loading

Reviews (1): Last reviewed commit: "Update React on Rails RC stack" | Re-trigger Greptile

@claude

claude Bot commented Jun 11, 2026

Copy link
Copy Markdown

Code Review: Update React on Rails 17.0.0-rc.2 stack

Overview

This is a clean, dependency-only PR that bumps the React on Rails ecosystem from 16.7.0.rc.3 to 17.0.0.rc.2 across both the Ruby gem and JavaScript packages. No application source code is changed.


What looks good

  • Consistency: Version pins are updated uniformly across Gemfile, Gemfile.lock, package.json, and yarn.lock. No stale references.
  • Lockfiles committed: Both Gemfile.lock and yarn.lock are updated, ensuring reproducible installs.
  • Documentation updated: README.md version targets now match the new pins, and react-on-rails-rsc is correctly added to the list since it was previously missing.
  • Thorough verification checklist: The PR body documents which commands passed and why others failed, which makes the blast radius clear.

Concerns

1. Pre-release versions on master (Medium)

All pinned versions (17.0.0.rc.2 / 17.0.0-rc.2) are release candidates. Merging RC dependencies into master means anyone cloning this tutorial repo gets pre-release software by default. If master is meant to track stable releases, this should target a dedicated RC branch. If RC tracking on master is intentional, a note in the README would help set expectations for readers.

2. RSpec suite could not be fully validated (Medium)

The PR body notes 47 out of 48 RSpec tests failed due to the Pro Node renderer not being available at 127.0.0.1:3800. While the root cause is an environment constraint (not a regression), merging without a green test suite means we have no confirmation the new gem versions integrate correctly at the Rails level. Consider running the suite in a CI environment where the renderer can run, or explicitly document this as a known gap.

3. Version divergence between react-on-rails-rsc and the rest of the pro packages (Low)

react-on-rails-rsc is at 19.0.5-rc.7 while react-on-rails-pro and react-on-rails-pro-node-renderer are at 17.0.0-rc.2. These packages use independent versioning schemes, which is architecturally fine, but the major-version gap (19 vs 17) can be surprising to contributors expecting a uniform version across the ecosystem. A brief note in the README or PR description clarifying that RSC is independently versioned would reduce confusion.

4. Pre-existing lint failures (Low / Informational)

Both yarn lint:eslint and yarn lint:prettier fail on unrelated pre-existing violations. These are not introduced by this PR, but since they fail in CI they make it harder to detect future regressions. Worth filing a follow-up issue to clean them up.


Summary

The mechanical version bump is correct and well-documented. The two medium-risk items — RC versions on master and the unvalidated RSpec suite — are worth resolving or explicitly accepting before merging, depending on the branch strategy for this repo.

Comment thread package.json
"react-on-rails-rsc": "19.0.5-rc.6",
"react-on-rails-pro": "17.0.0-rc.2",
"react-on-rails-pro-node-renderer": "17.0.0-rc.2",
"react-on-rails-rsc": "19.0.5-rc.7",

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

react-on-rails-rsc is versioned independently from the rest of the pro packages (17.0.0-rc.2), so the major-version gap (19 vs 17) is intentional. That said, it can be jarring for contributors expecting a uniform version across the ecosystem. Consider adding a short comment in the README's Version Targets section (e.g. "react-on-rails-rsc uses its own versioning scheme and does not track the main react-on-rails major version") to prevent confusion.

@justin808 justin808 merged commit 5d185bc into master Jun 11, 2026
12 checks passed
@justin808 justin808 deleted the jg-codex/ror-17-rc2-legacy-tutorial branch June 11, 2026 10:12
@github-actions

github-actions Bot commented Jun 11, 2026

Copy link
Copy Markdown

✅ Review App Deleted

Review app for PR #765 is deleted

🎮 Control Plane Console
📋 View Workflow Logs

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant