Update release documentation and remove deprecated pro-specific release files

Documentation updates:
- Update root releasing.md with all 5 packages and 4 parameters
- Add comprehensive requirements section (NPM, RubyGems, GitHub Packages auth)
- Add Ruby version management documentation
- Add Testing with Verdaccio section
- Update version synchronization to include all files
- Clarify public vs private package publishing

- Update pro CONTRIBUTING.md to reference root release task
- Replace pro releasing.md with redirect to root documentation
- Delete deprecated pro rakelib/release.rake
- Delete deprecated pro script/release

All release documentation now correctly reflects unified versioning
and the single release script at repository root.

Author: AbanoubGhadban

docs/contributor-info/releasing.md

@@ -1,6 +1,6 @@
 # Install and Release
 
-We're releasing this as a combined Ruby gem plus two NPM packages. We keep the version numbers in sync across all packages.
+We're releasing this as a unified release with 5 packages total. We keep the version numbers in sync across all packages using unified versioning.
 
 ## Testing the Gem before Release from a Rails App
 
@@ -13,41 +13,72 @@ Run `rake -D release` to see instructions on how to release via the rake task.
 ### Release Command
 
 ```bash
-rake release[gem_version,dry_run]
+rake release[version,dry_run,registry,skip_push]
 ```
 
 **Arguments:**
 
-- `gem_version`: The new version in rubygem format (no dashes). Pass no argument to automatically perform a patch version bump.
-- `dry_run`: Optional. Pass `true` to see what would happen without actually releasing.
+1. **`version`** (required): Version bump type or explicit version
+   - Bump types: `patch`, `minor`, `major`
+   - Explicit: `16.2.0` (rubygem format, no dashes)
 
-**Example:**
+2. **`dry_run`** (optional): `true` to preview changes without releasing
+   - Default: `false`
+
+3. **`registry`** (optional): Publishing registry for testing
+   - `verdaccio`: Publish all NPM packages to local Verdaccio (skips RubyGems)
+   - `npm`: Normal release to npmjs.org + rubygems.org (default)
+
+4. **`skip_push`** (optional): Skip git push to remote
+   - `skip_push`: Don't push commits/tags to remote
+   - Default: pushes to remote
+
+**Examples:**
 
 ```bash
-rake release[16.2.0]        # Release version 16.2.0
-rake release[16.2.0,true]   # Dry run to preview changes
-rake release                # Auto-bump patch version
+rake release[patch]                          # Bump patch version (16.1.1 → 16.1.2)
+rake release[minor]                          # Bump minor version (16.1.1 → 16.2.0)
+rake release[major]                          # Bump major version (16.1.1 → 17.0.0)
+rake release[16.2.0]                         # Set explicit version
+rake release[16.2.0,true]                    # Dry run to preview changes
+rake release[16.2.0,false,verdaccio]         # Test with local Verdaccio
+rake release[patch,false,npm,skip_push]      # Release but don't push to GitHub
 ```
 
 ### What Gets Released
 
-The release task publishes three packages with the same version number:
+The release task publishes 5 packages with unified versioning:
+
+**PUBLIC (npmjs.org + rubygems.org):**
+1. **react-on-rails** - NPM package
+2. **react-on-rails-pro** - NPM package
+3. **react_on_rails** - RubyGem
 
-1. **react-on-rails** NPM package
-2. **react-on-rails-pro** NPM package
-3. **react_on_rails** Ruby gem
+**PRIVATE (GitHub Packages):**
+4. **@shakacode-tools/react-on-rails-pro-node-renderer** - NPM package
+5. **react_on_rails_pro** - RubyGem
 
 ### Version Synchronization
 
 The task updates versions in all the following files:
 
-- `lib/react_on_rails/version.rb` (source of truth)
+**Core package:**
+- `lib/react_on_rails/version.rb` (source of truth for all packages)
 - `package.json` (root workspace)
 - `packages/react-on-rails/package.json`
-- `packages/react-on-rails-pro/package.json` (both version field and react-on-rails dependency)
+- `Gemfile.lock` (root)
 - `spec/dummy/Gemfile.lock`
 
-**Note:** The `react-on-rails-pro` package declares an exact version dependency on `react-on-rails` (e.g., `"react-on-rails": "16.2.0"`). This ensures users install compatible versions of both packages.
+**Pro package:**
+- `react_on_rails_pro/lib/react_on_rails_pro/version.rb` (VERSION only, not PROTOCOL_VERSION)
+- `react_on_rails_pro/package.json` (node-renderer)
+- `packages/react-on-rails-pro/package.json` (+ dependency version)
+- `react_on_rails_pro/Gemfile.lock`
+- `react_on_rails_pro/spec/dummy/Gemfile.lock`
+
+**Note:**
+- `react_on_rails_pro.gemspec` dynamically references `ReactOnRails::VERSION`
+- `react-on-rails-pro` NPM dependency is pinned to exact version (e.g., `"react-on-rails": "16.2.0"`)
 
 ### Pre-release Versions
 
@@ -107,14 +138,77 @@ After a successful release, you'll see instructions to:
 
 ## Requirements
 
-This task depends on the `gem-release` Ruby gem, which is installed via `bundle install`.
+### NPM Publishing
 
-For NPM publishing, you must be logged in to npm and have publish permissions for both packages:
+You must be logged in and have publish permissions:
 
+**For public packages (npmjs.org):**
 ```bash
 npm login
 ```
 
+**For private packages (GitHub Packages):**
+- Get a GitHub personal access token with `write:packages` scope
+- Add to `~/.npmrc`:
+  ```
+  //npm.pkg.github.com/:_authToken=<TOKEN>
+  always-auth=true
+  ```
+- Set environment variable:
+  ```bash
+  export GITHUB_TOKEN=<TOKEN>
+  ```
+
+### RubyGems Publishing
+
+**For public gem (rubygems.org):**
+- Standard RubyGems credentials via `gem push`
+
+**For private gem (GitHub Packages):**
+- Add to `~/.gem/credentials`:
+  ```
+  :github: Bearer <GITHUB_TOKEN>
+  ```
+
+### Ruby Version Management
+
+The script automatically detects and switches Ruby versions when needed:
+- Supports: RVM, rbenv, asdf
+- Set via `RUBY_VERSION_MANAGER` environment variable (default: `rvm`)
+- Example: Pro dummy app requires Ruby 3.3.7, script auto-switches from 3.3.0
+
+### Dependencies
+
+This task depends on the `gem-release` Ruby gem, which is installed via `bundle install`.
+
+## Testing with Verdaccio
+
+Before releasing to production, test the release process locally:
+
+1. Install and start Verdaccio:
+   ```bash
+   npm install -g verdaccio
+   verdaccio
+   ```
+
+2. Run release with verdaccio registry:
+   ```bash
+   rake release[patch,false,verdaccio]
+   ```
+
+3. This will:
+   - Publish all 3 NPM packages to local Verdaccio
+   - Skip RubyGem publishing
+   - Update version files (revert manually after testing)
+
+4. Test installing from Verdaccio:
+   ```bash
+   npm set registry http://localhost:4873/
+   npm install [email protected]
+   # Reset when done:
+   npm config delete registry
+   ```
+
 ## Troubleshooting
 
 ### Dry Run First

react_on_rails_pro/CONTRIBUTING.md

@@ -282,14 +282,51 @@ TRACE_REACT_ON_RAILS=true && foreman start -f Procfile.dev
 ```
 
 # Releasing
-Contact Justin Gordon, [[email protected]](mailto:[email protected]).
 
-> [!NOTE]
-> These files need to include auth tokens to [publish to Github Packages](https://docs.github.com/en/enterprise-server%403.10/packages/working-with-a-github-packages-registry/working-with-the-rubygems-registry):
-> 1. `~/.npmrc`
-> 2. `~/.gem/credentials`
+⚠️ **The release process has moved to the repository root.**
+
+React on Rails Pro is now released together with React on Rails using unified versioning.
+All packages (core + pro) are released together with the same version number.
+
+Contact Justin Gordon, [[email protected]](mailto:[email protected]) for release permissions.
+
+## Prerequisites
+
+You need authentication for both public and private package registries:
+
+**Public packages (npmjs.org + rubygems.org):**
+- NPM: Run `npm login`
+- RubyGems: Standard credentials via `gem push`
+
+**Private packages (GitHub Packages):**
+- Get a GitHub personal access token with `write:packages` scope
+- Configure `~/.npmrc`:
+  ```
+  //npm.pkg.github.com/:_authToken=<TOKEN>
+  always-auth=true
+  ```
+- Configure `~/.gem/credentials`:
+  ```
+  :github: Bearer <GITHUB_TOKEN>
+  ```
+- Set environment variable: `export GITHUB_TOKEN=<TOKEN>`
+
+## Release Command
+
+From the **repository root**, run:
 
-Then run a command like:
 ```bash
-bundle exec rake release\[4.0.0.rc.1\]
+# Full release
+cd /path/to/react_on_rails
+rake release[4.0.0]
+
+# Dry run first
+rake release[4.0.0,true]
+
+# Test with Verdaccio
+rake release[4.0.0,false,verdaccio]
 ```
+
+For complete documentation, see:
+- [Root Release Documentation](../docs/contributor-info/releasing.md)
+- Run `rake -D release` for inline help

react_on_rails_pro/docs/contributors-info/releasing.md

@@ -1,37 +1,40 @@
-# Install and Release
-Github packages and gems are used for distribution from the https://github.com/shakacode-tools/react_on_rails_pro repo.
-1. Check that the CHANGELOG.md is updated
-2. See below for Prerequisites and then run the release command like this
+# Releasing React on Rails Pro
 
-```
-rake release[1.5.7]
-```
+⚠️ **This documentation is outdated.**
 
-or for a beta release. Note the period, not dash, before the 'beta'.
+React on Rails Pro is now released together with React on Rails using a unified release script.
 
-```
-rake release[1.5.6.beta.2]
-```
+## Current Release Process
 
-## Testing the Gem before Release from a Rails App
-See [Contributing](https://github.com/shakacode/react_on_rails_pro/blob/master/CONTRIBUTING.md)
+Please refer to the main release documentation:
 
-### Prerequisites
-Before this command can be run, a bit of setup is required:
+👉 **[/docs/contributor-info/releasing.md](../../../docs/contributor-info/releasing.md)**
 
-1. Get a Github personal access token that provides both Repo and write:packages access
-2. In `~/.npmrc`
-```
-//npm.pkg.github.com/:_authToken=<TOKEN>
-always-auth=true
-```
-3. Ensure that you set the ENV value when you will run the script. A `.envrc` is convenient for this.
+Or run from the repository root:
+
+```bash
+cd .. && rake -D release
 ```
-export GITHUB_TOKEN=<TOKEN>
+
+## Quick Reference
+
+```bash
+# From repository root (not from react_on_rails_pro/)
+cd /path/to/react_on_rails
+
+# Release with version bump
+rake release[4.0.0]
+
+# Dry run first (recommended)
+rake release[4.0.0,true]
+
+# Test with local Verdaccio
+rake release[4.0.0,false,verdaccio]
 ```
 
-### Details
-1. See `/package.json` for how npm release and release-it know how to publish the package to Github
-2. See `/react_on_rails.gemspec` for the gem specification.
-3. See `/rakelib/release.rake` for details on how a release is done. The gem is set to publish to
-   Github by the `gem_push_command`
+This unified script releases all 5 packages together:
+- react-on-rails (NPM)
+- react-on-rails-pro (NPM)
+- react_on_rails (RubyGem)
+- @shakacode-tools/react-on-rails-pro-node-renderer (NPM, GitHub Packages)
+- react_on_rails_pro (RubyGem, GitHub Packages)