Do not auto bump package.json (#328)

## Why

Auto bumping package.json in CI requires pushing to `main`. We should
create a PR to bump version instead.

## What changed

- Remove prepare-release.yml
- Update README

## Versioning

- [ ] Breaking protocol change
- [ ] Breaking ts/js API change

<!-- Kind reminder to add tests and updated documentation if needed -->

Author: daweifeng-replit

.github/workflows/prepare-release.yml

@@ -2,9 +2,8 @@
 name: Build and Publish Package
 
 on:
-  push:
-    tags:
-      - 'v*' # Trigger on tags like v1.0.0, v2.3.4, etc.
+  release:
+    types: [published]
 
 jobs:
   build-and-publish:

.github/workflows/publish.yml

@@ -285,19 +285,26 @@ River uses an automated release process with [Release Drafter](https://github.co
    - Updates the draft release notes with PR titles
    - You can view the draft at [GitHub Releases](../../releases)
 
-2. **When ready to release**:
+2. **When ready to release, create a version bump PR**:
 
-   - Go to [Actions](../../actions/workflows/prepare-release.yml)
-   - Click "Run workflow" to open the configuration dialog
-   - Click "Run workflow" again to confirm and start the process (version is automatically determined from draft release)
+   - Create a PR that bumps the version in `package.json` and `package-lock.json`. You can run `pnpm version --no-git-tag-version <version>` to bump the version.
+   - Use semantic versioning:
+     - `patch` - Bug fixes, small improvements (e.g., 0.208.4 → 0.208.5)
+     - `minor` - New features, backwards compatible (e.g., 0.208.4 → 0.209.0)
+     - `major` - Breaking changes (e.g., 0.208.4 → 1.0.0)
+   - Merge the PR to main
 
-   The version bump is automatically calculated based on PR labels:
+3. **Publish the GitHub release**:
 
-   - `patch` - Bug fixes, small improvements (e.g., 0.208.4 → 0.208.5)
-   - `minor` - New features, backwards compatible (e.g., 0.208.4 → 0.209.0)
-   - `major` - Breaking changes (e.g., 0.208.4 → 1.0.0)
+   - Go to [GitHub Releases](../../releases)
+   - Find the draft release and click "Edit"
+   - Update the tag to match your new version (e.g., `v0.209.0`)
+   - Click "Publish release"
 
-3. **Automation takes over**:
-   - The "Prepare Release" workflow bumps the version and creates a git tag
-   - The git tag automatically triggers the "Build and Publish" workflow
-   - The `river` package is published to NPM and the GitHub release is created
+4. **Automation takes over**:
+
+   - Publishing the release automatically triggers the "Build and Publish" workflow
+   - The `river` package is published to NPM
+
+5. **Manual npm release**:
+   - If the auto-publish workflow failed, you can run `npm run release` locally