Update documentation for public package distribution

Following PR #1901's switch from GitHub Packages to public distribution,
update all documentation to reflect that React on Rails Pro packages are
now publicly available on npmjs.org and RubyGems.org.

Changes:
- Remove all GitHub Personal Access Token requirements
- Remove .npmrc and gem credentials configuration steps
- Simplify installation to standard gem/npm commands
- Update releasing docs to show all 5 packages as public
- Remove "private repository" language throughout
- Update troubleshooting to remove token-related issues

Files updated:
- react_on_rails_pro/docs/installation.md (major simplification)
- docs/contributor-info/releasing.md
- react_on_rails_pro/docs/contributors-info/releasing.md
- react_on_rails_pro/docs/contributors-info/onboarding-customers.md
- react_on_rails_pro/docs/troubleshooting.md
- react_on_rails_pro/docs/ruby-api.md
- react_on_rails_pro/docs/code-splitting-loadable-components.md
- react_on_rails_pro/docs/node-renderer/basics.md
- react_on_rails_pro/docs/node-renderer/error-reporting-and-tracing.md

Author: claude

docs/contributor-info/releasing.md

@@ -58,9 +58,9 @@ The release task publishes 5 packages with unified versioning:
 
 1. **react-on-rails** - NPM package
 2. **react-on-rails-pro** - NPM package
-3. **react_on_rails** - RubyGem
-
-**PRIVATE (GitHub Packages):** 4. **@shakacode-tools/react-on-rails-pro-node-renderer** - NPM package 5. **react_on_rails_pro** - RubyGem
+3. **@shakacode-tools/react-on-rails-pro-node-renderer** - NPM package
+4. **react_on_rails** - RubyGem
+5. **react_on_rails_pro** - RubyGem
 
 ### Version Synchronization
 
@@ -147,39 +147,17 @@ After a successful release, you'll see instructions to:
 
 ### NPM Publishing
 
-You must be logged in and have publish permissions:
-
-**For public packages (npmjs.org):**
+You must be logged in to npmjs.org and have publish permissions:
 
 ```bash
 npm login
 ```
 
-**For private packages (GitHub Packages):**
-
-- Get a GitHub personal access token with `write:packages` scope
-- Add to `~/.npmrc`:
-  ```ini
-  //npm.pkg.github.com/:_authToken=<TOKEN>
-  always-auth=true
-  ```
-- Set environment variable:
-  ```bash
-  export GITHUB_TOKEN=<TOKEN>
-  ```
+All NPM packages are published to npmjs.org.
 
 ### 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>
-  ```
+Standard RubyGems credentials via `gem push`. All gems are published to rubygems.org.
 
 ### Ruby Version Management
 

react_on_rails_pro/docs/code-splitting-loadable-components.md

@@ -270,7 +270,6 @@ reactOnRailsProNodeRenderer(config);
 
 ## Making HMR Work
 To make HMR work, it's best to disable loadable-components when using the Dev Server.
-Note: you will need access to our **private** React on Rails Pro repository to open the following links.
 
 Take a look at the code searches for ['imports-loadable'](https://github.com/shakacode/react_on_rails_pro/search?q=imports-loadable&type=code) and ['imports-hmr'](https://github.com/shakacode/react_on_rails_pro/search?q=imports-hmr&type=code)
 
@@ -297,8 +296,6 @@ And compare:
 
 ### Routes file
 
-Note: you will need access to our **private** React on Rails Pro repository to open the following links.
-
 - [spec/dummy/client/app/components/Loadable/routes/Routes.imports-hmr.jsx](https://github.com/shakacode/react_on_rails_pro/blob/master/spec/dummy/client/app/components/Loadable/routes/Routes.imports-hmr.jsx)
 - [spec/dummy/client/app/components/Loadable/routes/Routes.imports-loadable.jsx](https://github.com/shakacode/react_on_rails_pro/blob/master/spec/dummy/client/app/components/Loadable/routes/Routes.imports-loadable.jsx)
 

react_on_rails_pro/docs/contributors-info/onboarding-customers.md

@@ -1,6 +1,6 @@
-# Creating a github OAuth Token
+# Customer Onboarding
 
-*[Document for ShakaCode Staff](https://docs.google.com/document/d/10snzXEWgkorcai76_OxlhjQcDae_WoxRfBCdVbmcQoU/edit)*
+React on Rails Pro packages are now publicly available. No GitHub tokens or special access required.
 
 # Customer Steps
-See [Installation](../installation.md).
+See [Installation](../installation.md) for public package installation instructions.

react_on_rails_pro/docs/contributors-info/releasing.md

@@ -33,8 +33,8 @@ rake release[17.0.0,false,verdaccio]
 ```
 
 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)
+- react-on-rails (NPM, npmjs.org)
+- react-on-rails-pro (NPM, npmjs.org)
+- @shakacode-tools/react-on-rails-pro-node-renderer (NPM, npmjs.org)
+- react_on_rails (RubyGem, rubygems.org)
+- react_on_rails_pro (RubyGem, rubygems.org)

react_on_rails_pro/docs/installation.md

@@ -1,5 +1,6 @@
 # Installation
-Since the repository is private, you will get a **GitHub Personal Access Token** and an account that can access the packages. Substitute that value in the commands below. If you dont' have this, ask [justin@shakacode.com](mailto:justin@shakacode.com) to give you one.
+
+React on Rails Pro packages are now publicly available on npmjs.org and RubyGems.org. No authentication or special access is required.
 
 Check the [CHANGELOG](https://github.com/shakacode/react_on_rails_pro/blob/master/CHANGELOG.md) to see what version you want.
 
@@ -9,48 +10,30 @@ For the below docs, find the desired `<version>` in the CHANGELOG. Note, for pre
 
 # Ruby
 ## Gem Installation
-1. Ensure your **Rails** app is using the **react_on_rails** gem, version greater than 11.0.7.
-1. Add the `react_on_rails_pro` gem to your **Gemfile**. Substitute the appropriate version number. 
-   
-## Gemfile Change
 
-Replace the following in the snippet for the Gemfile
-1. `<account>` for the api key
-2. `<api-key>`
-3. `<version>` desired
+1. Ensure your **Rails** app is using the **react_on_rails** gem, version greater than 11.0.7.
+2. Add the `react_on_rails_pro` gem to your **Gemfile**. Substitute the appropriate version number.
 
-```ruby
-source "https://<rorp-account>:<token>@"\
-  "rubygems.pkg.github.com/shakacode-tools" do
-  gem "react_on_rails_pro", "<version>"
-end
-```
+## Gemfile
 
-## Alternate installation keeping the key out of your Gemfile
+Add the following to your Gemfile:
 
 ```ruby
-source "https://rubygems.pkg.github.com/shakacode-tools" do
-  gem "react_on_rails_pro", "<version>"
-end
+gem "react_on_rails_pro", "<version>"
 ```
-Or use the `gem install` command:
+
+Or install via command line:
 
 ```bash
-gem install react_on_rails_pro --version "<version>> --source "https://rubygems.pkg.github.com/shakacode-tools"
+gem install react_on_rails_pro --version "<version>"
 ```
 
-Then edit your permissions for bundler at the command line:
+Then run:
 
-```
-bundle config set rubygems.pkg.github.com <username>:<token>
+```bash
+bundle install
 ```
 
-## Using a branch in your Gemfile
-Note, you should probably use an ENV value for the token so that you don't check this into your source code.
-   ```ruby
-   gem "react_on_rails_pro", version: "<version>", git: "https://[your-github-token]:x-oauth-basic@github.com/shakacode/react_on_rails_pro.git", tag: "<version>"
-   ```
-
 ## Rails Configuration
 You don't need to create an initializer if you are satisfied with the default as described in 
 [Configuration](./configuration.md)
@@ -61,15 +44,8 @@ Note, you only need to install the Node Package if you are using the standalone
 ## Installation
 
 1. Create a subdirectory of your rails project for the Node renderer. Let's use `react-on-rails-pro`.
-   
-2. Create a file `react-on-rails-pro/.npmrc` with the following
-```
-always-auth=true
-//npm.pkg.github.com/:_authToken=<token>
-@shakacode-tools:registry=https://npm.pkg.github.com
-```
 
-3. Create a `react-on-rails-pro/package.json`
+2. Create a `react-on-rails-pro/package.json`
 ```json
 {
   "private": true,
@@ -82,11 +58,15 @@ always-auth=true
 }
 ```
 
-4. Be sure to run `npm i` **and not** `yarn` as only npm seems to work with the private github packages.
+3. Install dependencies using npm or yarn:
 
-If you really want to use yarn, see [Yarn can't find private Github npm registry](https://stackoverflow.com/questions/58316109/yarn-cant-find-private-github-npm-registry)
+```bash
+npm install
+# or
+yarn install
+```
 
-5. You can start the renderer with either the executable `node-renderer` or, preferably, with 
+4. You can start the renderer with either the executable `node-renderer` or, preferably, with
    a startup JS file, say called `react-on-rails-pro/react-on-rails-pro-node-renderer.js` with
    these contents. _Note the use of the namespaced **`@shakacode-tools/react-on-rails-pro-node-renderer`** for the package.
 
@@ -141,43 +121,8 @@ if (env.CI) {
 reactOnRailsProNodeRenderer(config)
 ```
 
-## Instructions for using a branch
-
-Install the node-renderer executable, possibly globally. Substitute the branch name or tag for `master`
-```
-yarn global add https://<your-github-token>:x-oauth-basic@github.com/shakacode/react_on_rails_pro.git\#master
-```
-
-This installs a binary `node-renderer`.
-
-### Using Github packages
-
-Login into npm
-
-```bash
-npm install @shakacode-tools/react-on-rails-pro-node-renderer@<version>
-```                      
-
-or edit package.json directly
-```json
-"@shakacode-tools/react-on-rails-pro-node-renderer": "<version>"
-```                     
-
 ### Configuration
 See [NodeRenderer JavaScript Configuration](./node-renderer/js-configuration.md).
 
 #### Webpack Configuration
-Set your server bundle webpack configuration to use a target of `node` per the [Webpack docs](https://webpack.js.org/concepts/targets/#usage).
-
-## Authentication when using Github packages
-[Auth for the npm package](https://docs.github.com/en/packages/using-github-packages-with-your-projects-ecosystem/configuring-npm-for-use-with-github-packages#authenticating-to-github-packages)
-
-Create a new ~/.npmrc file if one doesn't exist.
-```
-//npm.pkg.github.com/:_authToken=TOKEN
-```                  
-
-To configure bundler if you don't want the token in your Gemfile:
-```
-bundle config https://rubygems.pkg.github.com/OWNER USERNAME:TOKEN
-``` 
+Set your server bundle webpack configuration to use a target of `node` per the [Webpack docs](https://webpack.js.org/concepts/targets/#usage). 

react_on_rails_pro/docs/node-renderer/basics.md

@@ -33,10 +33,10 @@ For the most control over the setup, create a JavaScript file to start the NodeR
    cd renderer-app
    ```
 2. Make sure you have **Node.js** version **14** or higher and **Yarn** installed.
-3. Init node application and yarn add to install `@shakacode-tools/react-on-rails-pro-node-renderer` package.
+3. Init node application and install `@shakacode-tools/react-on-rails-pro-node-renderer` package from npmjs.org.
    ```sh
    yarn init
-   yarn add https://[your-github-token]:x-oauth-basic@github.com/shakacode/react_on_rails_pro.git\#master
+   yarn add @shakacode-tools/react-on-rails-pro-node-renderer
    ```
 4. Configure a JavaScript file that will launch the rendering server per the docs in [Node Renderer JavaScript Configuration](./js-configuration.md). For example, create a file `node-renderer.js`. Here is a simple example that uses all the defaults except for bundlePath:
 

react_on_rails_pro/docs/node-renderer/error-reporting-and-tracing.md

@@ -47,8 +47,7 @@ To enable Sentry Tracing:
 
 ## Other services
 You can create your own integrations in the same way as the provided ones.
-If you have access to the React on Rails Pro repository,
-you can use [their implementations](https://github.com/shakacode/react_on_rails_pro/tree/master/packages/node-renderer/src/integrations) as examples.
+You can use [the provided implementations](https://github.com/shakacode/react_on_rails_pro/tree/master/packages/node-renderer/src/integrations) as examples.
 Import these functions from `@shakacode-tools/react-on-rails-pro-node-renderer/integrations/api`:
 
 ### Error reporting services

react_on_rails_pro/docs/ruby-api.md

@@ -1,7 +1,5 @@
 # Ruby API
 
-Note: you will need access to our **private** React on Rails Pro repository to open the following links.
-
 ## View Helpers
 
 See the [app/helpers/react_on_rails_pro_helper.rb](https://github.com/shakacode/react_on_rails_pro/blob/master/app/helpers/react_on_rails_pro_helper.rb) source.

react_on_rails_pro/docs/troubleshooting.md

@@ -1,24 +1,12 @@
 # Troubleshooting
 
-## Invalid Token Workaround
-On June 27, 2024, tokens mysteriously did not work for a few hours. The problem resolved itself within a few hours.
+## Package Installation Issues
 
-If you do see this problem, get in touch with the package maintainers via Slack. You can also message
-Justin Gordon at +1-808-281-7272.
+React on Rails Pro packages are publicly available on npmjs.org and rubygems.org. No authentication tokens are required.
 
-As an alternative to the token issue, if you have an account with access to the docs and this file, you can
-create a new token and follow these steps.
+If you encounter installation issues:
 
-To create a new token, visit https://github.com/settings/apps:
-1. Developer Settings
-2. Personal access tokens
-3. Tokens (classic)
-4. Generate a new token, classic
-5. 30-day expiration (to be safer)
-6. Repo privileges (not ideal) but shouldn't last long
-
-Then follow these steps to use your token:
-* [Ruby Gem](https://github.com/shakacode/react_on_rails_pro/blob/master/docs/installation.md#using-a-branch-in-your-gemfile)
-* [Node Package](https://github.com/shakacode/react_on_rails_pro/blob/master/docs/installation.md#instructions-for-using-a-branch)
-
-Note that this token gives `repo` access, so you want to revoke this token ASAP.
+1. Ensure you're using the latest version of npm/yarn or bundler
+2. Check that you have network access to npmjs.org and rubygems.org
+3. Verify the package version exists in the [CHANGELOG](https://github.com/shakacode/react_on_rails_pro/blob/master/CHANGELOG.md)
+4. Contact support via Slack or email Justin Gordon at justin@shakacode.com