Walkthrough

This PR updates documentation across multiple React on Rails guides to reflect version 16.4.0 as the new minimum required version, replacing previous references to 16.0, 16.2, and pre-release versions. Version specifications in dependency manifests (Gemfile, package.json) are also updated to align with this release.

Changes

Poem

🐰 Version bumps and docs aligned,
Sixteen-four-point-oh in mind!
From alpha states to stable ground,
Our docs now match—hooray, we've found
The path to clarity, refined.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~4 minutes

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 @coderabbitai help to get the list of available commands and usage tips.}

Greptile Summary

Docs-only PR that raises the minimum recommended version floor from various older versions (16.0, 16.2, 16.3, and legacy alpha/RC versions) to 16.4.0 across 13 documentation files covering install guides, quick starts, streaming SSR prerequisites, upgrade instructions, and troubleshooting.

• Most changes are clean version string bumps in Gemfile/package.json examples and prerequisite lists
• Removes an outdated "not released yet" note in docs/pro/react-server-components/create-without-ssr.md and updates alpha version pins to 16.4.0
• Aligns React on Rails Pro version references with the unified versioning scheme (replacing old v4.0.0 / v4.0.0.rc.5 references)
• Issue: docs/oss/getting-started/pro-quick-start.md replaces concrete version pins with non-functional placeholder strings ("<same_version_as_react_on_rails_pro>") that would break if copy-pasted
• Minor inconsistency: docs/oss/deployment/troubleshooting-build-errors.md recommends upgrading to 16.4.0 but still states the fix was introduced in 16.2.0 in the same section

Confidence Score: 4/5

• Docs-only changes with one copy-paste-breakable placeholder that should be fixed before merge.
• All changes are documentation-only with no code impact. The vast majority of changes are clean version bumps. One file (pro-quick-start.md) introduces placeholder strings that are not valid Gemfile syntax, which lowers confidence slightly. The troubleshooting inconsistency is minor and non-breaking.
• Pay close attention to docs/oss/getting-started/pro-quick-start.md — the placeholder version strings need to be replaced with concrete version pins before merge.

Important Files Changed

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart TD
    A[PR: Raise docs version floor to 16.4.0] --> B[OSS Getting Started]
    A --> C[OSS Building Features]
    A --> D[OSS Deployment / Upgrading]
    A --> E[Pro Docs]

    B --> B1["quick-start.md\n16.0+ → 16.4.0+"]
    B --> B2["pro-quick-start.md\n⚠️ placeholders instead of versions"]

    C --> C1["streaming-server-rendering.md\nv16.0.0 / v4.0.0.rc.5 → v16.4.0"]
    C --> C2["i18n.md\n16.2+ → 16.4.0+"]
    C --> C3["extensible-precompile-pattern.md\n16.2+ → 16.4.0+"]
    C --> C4["testing-configuration.md\n>= 16.0 → >= 16.4.0"]

    D --> D1["troubleshooting-build-errors.md\n⚠️ fix version inconsistency"]
    D --> D2["upgrading-react-on-rails.md\n~> 16.0 → ~> 16.4"]

    E --> E1["installation.md\n16.0.0 → 16.4.0"]
    E --> E2["streaming-server-rendering.md\nv15.0.0-alpha / v4.0.0 → v16.4.0"]
    E --> E3["create-without-ssr.md\nalpha versions → 16.4.0"]
    E --> E4["updating.md\n16.2 → 16.4"]
    E --> E5["generator-details.md\n16.3.0 → 16.4.0"]

    style B2 fill:#fff3cd,stroke:#ffc107
    style D1 fill:#fff3cd,stroke:#ffc107

_{Last reviewed commit: e2e23e1}

Review: Raise docs version floor to 16.4.0 -- Thanks for cleaning up these stale version references. Four issues noted (inline comments posted for the first three): (1) troubleshooting-build-errors.md has a factual contradiction: the section title and body both say the duplicate-build fix landed in 16.2.0, but the solution block now says 16.4.0+. (2) pro-quick-start.md lines 30-31 introduced non-functional placeholder strings as gem version constraints -- bundle install will fail if pasted verbatim. (3) extensible-precompile-pattern.md says the API has been available since i18n support was added, but then requires 16.4.0+ -- the previous 16.2+ was likely correct. (4) Minor: updating.md now says 'Upgrading to 16.4.0+' but the audience bullet still says '16.2.0-beta.x or earlier', leaving a gap for stable 16.2.0-16.3.x users.

Addressed review comments in commit d185d4e. I switched updated Gemfile and package snippets to exact 16.4.0 pins (no range operators) in generator-details, testing-configuration, pro-quick-start, upgrading-react-on-rails, pro/updating, and troubleshooting-build-errors. Please re-review when convenient.

Review: Raise docs version floor to 16.4.0

Good direction overall. A few issues worth addressing before merging.

1. Pervasive exact-version pinning (most impactful)

The most widespread problem is replacing flexible version constraints with exact pins throughout installation/setup guidance. Users copying these snippets literally will be locked to exactly 16.4.0 and will not pick up patch-level fixes. The correct pattern is >= 16.4.0 or ~> 16.4 in Gemfiles and ^16.4.0 in package.json. Inline comments with suggestions have been left on each affected line.

Files affected: testing-configuration.md, troubleshooting-build-errors.md, upgrading-react-on-rails.md, generator-details.md, pro-quick-start.md, pro/updating.md.

2. Timing: 16.4.0 is not yet released

Both version.rb files currently show 16.4.0.rc.9 (a release candidate). Publishing docs that reference 16.4.0 as a stable install target before the gem/npm package is actually published will cause install failures. Consider merging this PR only when the final release is cut, or add a note that 16.4.0 is forthcoming.

3. Potentially inaccurate min-version bumps

extensible-precompile-pattern.md and i18n.md originally stated React on Rails 16.2+ for the Shakapacker precompile hook feature. This PR raises that floor to 16.4.0+ without explanation. If the feature shipped in 16.2, this is inaccurate and will mislead 16.2/16.3 users. Please verify the true minimum.

4. Confusing placeholder versions in pro-quick-start.md

The older-versions Gemfile example now contains <same_version_as_react_on_rails_pro> and <same_version> as literal strings. These are not copy-paste friendly and are more confusing than concrete version numbers.

5. Pro version scheme change needs explanation (streaming-server-rendering.md)

The old prerequisite was React on Rails Pro v4.0.0.rc.5 or higher. The new value v16.4.0 represents a major versioning realignment for the Pro package. A brief note explaining that Pro adopted the OSS gem version numbering starting from 16.x would prevent reader confusion about the apparent gap between 4.x and 16.x.

Review: Raise docs version floor to 16.4.0

Overall this is a clean, well-scoped docs-only PR. The version bumps are consistent across the guides and the removal of the stale alpha warning in the RSC doc is a good cleanup. A few issues worth addressing:

1. Ambiguous multi-package-manager code block

In docs/pro/react-server-components/create-without-ssr.md, the new install snippet puts yarn, npm, and pnpm commands in a single bash block with no instruction to pick one. A reader following copy-paste will run all three package managers in sequence. These should be split into separate labeled sections or clearly marked as alternatives.

2. Inline note in streaming prerequisites should be a callout block

Both streaming SSR prerequisite lists now contain a bare Note: Pro version numbering was realigned... sentence inside a bullet list. This looks like a dangling sentence. The rest of the docs use GitHub-flavored > [!NOTE] blocks — this should use the same treatment and be placed below the Prerequisites list rather than inside it as a bullet.

3. Gap in the audience definition in docs/pro/updating.md

The guide still says 'On version 16.2.0-beta.x or earlier' while the upgrade target is now 16.4.0. Users on 16.2.0 stable or 16.3.x who are not on the old GitHub Packages system may incorrectly skip this guide, even though Step 3 (adding react-on-rails-pro and renaming the node renderer package) is relevant to anyone upgrading to 16.4.0. Consider broadening the cutoff.

Review: Raise docs version floor to 16.4.0

Documentation-only PR — clean in scope. A few issues worth fixing before merge:

Issues

1. Contradictory versions in troubleshooting-build-errors.md
The Solution section heading still reads "Upgrade to React on Rails 16.2.0 or later" (unchanged), while the workaround note was bumped to say "Upgrade to 16.4.0+". These two statements now conflict in the same section. Either update the solution heading/example to 16.4.0 with a note that the fix originally landed in 16.2.0, or leave the note at 16.2.0 since that is the version that actually contains the fix.

2. Exact version pins in Gemfile examples are too restrictive
Several files now show gem "react_on_rails", "16.4.0" (exact pin) instead of the pessimistic constraint "~> 16.4". Exact pins prevent users from automatically picking up patch releases when they run bundle update. The existing docs/oss/getting-started/pro-quick-start.md correctly uses "~> 16.4" — the other examples should match.

Affected:

• docs/oss/building-features/testing-configuration.md — "16.4.0" should be "~> 16.4"
• docs/pro/updating.md — Gemfile diff shows "16.4.0" should be "~> 16.4"

3. Feature minimum-version claims may now be inaccurate
extensible-precompile-pattern.md and i18n.md were bumped from "16.2+" to "16.4.0+". If those features actually shipped in 16.2.x, raising the documented minimum misrepresents the compatibility surface. The version floor for install/demo guidance is a separate concern from the version at which a feature became available. Consider keeping the compatibility note at 16.2 (the actual introduction version) and separately noting that 16.4.0 is recommended for new installs.

Minor

docs/pro/installation.md: the pre-release format examples (16.4.0.beta.1) are illustrative of format, not actual releases — changing them from 16.2 to 16.4 is harmless but adds noise. No change needed.

test comment - please ignore

Documentation Guide

React on Rails is one product with two tiers: open source for Rails + React integration, and Pro when you need higher SSR throughput, deeper RSC support, or maintainer-backed help.

Choose the path that matches your app

Starting a new Rails + React app

• Create a new app
• Quick Start
• Tutorial — build a complete app

Adding React to an existing Rails app

• Install into an existing Rails app
• Render your first component

Already using React on Rails OSS?

• Compare OSS and Pro
• Upgrade to Pro

Evaluating Rails + React options

• Examples and migration references
• Compare with alternatives
• Migrate from react-rails

Dive deeper when you need it

• Introduction
• Core Concepts
• API Reference
• Deployment and troubleshooting
• Configuration
• Changelog

Pro features

• React Server Components - RSC with Rails
• Streaming SSR - Progressive server rendering
• Node Renderer - Dedicated Node.js rendering server
• Upgrading to Pro - Switch from OSS to Pro in three steps

Friendly evaluation policy

• You can try React on Rails Pro without a license while evaluating.
• If your organization is budget-constrained, contact us about free licenses.

Need more help?

• GitHub Discussions
• Documentation website

Review summary posted as inline comments. See individual file threads for details.

test2

Review: Raise docs version floor to 16.4.0

Overall this is a reasonable docs-only cleanup, but I found a few issues worth addressing before merging.

Bugs / Inconsistencies

troubleshooting-build-errors.md — The note now says “Upgrade to 16.4.0+ for the proper fix,” but the workaround code immediately above guards on ReactOnRails::VERSION < '16.2.0'. The fix has been in 16.2.0+ all along; bumping the note to 16.4.0 is factually wrong and could cause unnecessary upgrades. See inline comment.

docs/pro/updating.md — The guide is specifically about migrating away from GitHub Packages (private to public distribution), which shipped with 16.2.0. Changing the scope from “16.2.0-beta.x or earlier” to “any version before 16.4.0” means users already on 16.2.x-16.3.x (who completed the PAT migration long ago) will now think this guide applies to them. See inline comment.

Style / Best Practices

testing-configuration.md — Example Gemfile uses an exact pin "16.4.0". Users copying this verbatim will be locked out of future patch releases. Prefer "~> 16.4". See inline comment.

generator-details.md — Showing '16.4.0' with “(or later -- pin to the exact version you want)” is self-contradictory. Either use '>= 16.4.0' or document a concrete version without the hedge. See inline comment.

What Looks Good

• Removing the stale “not yet released” warning from create-without-ssr.md is a clear improvement.
• The multi-package-manager install snippet (yarn/npm/pnpm) is helpful.
• Version format examples in installation.md are fine as illustrative placeholders.