Fix gem bump to properly update version (#188)

* Add simplified gem release process

This commit adds a streamlined release process for the cypress-on-rails gem,
removing the npm package release steps that were present in the react_on_rails
version.

Key changes:
- Add lib/tasks/release.rake with gem-only release automation
- Add docs/RELEASE.md with comprehensive release documentation
- Simplify process by removing release-it and npm publishing steps
- Keep essential features: version bumping, git tagging, and gem publishing

The release task handles:
- Checking for uncommitted changes
- Pulling latest changes
- Bumping version using gem-release
- Publishing to RubyGems with OTP support
- Providing post-release instructions for CHANGELOG updates

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <noreply@anthropic.com>

* Fix gem bump to properly update version

The previous implementation used --no-commit which prevented gem bump
from properly updating the version. Now gem bump will:
- Update the version in lib/cypress_on_rails/version.rb
- Create a commit with the version change
- Create a git tag (e.g., v1.19.0)

Then the task explicitly pushes the commit and tags before publishing
to RubyGems. This matches the standard gem-release workflow.

Also added --skip-ci flag to prevent CI from running on version bumps.

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <noreply@anthropic.com>

---------

Co-authored-by: Claude <noreply@anthropic.com>

Author: justin808

docs/RELEASE.md

@@ -84,12 +84,13 @@ The release task automates the following steps:
 
 1. Checks for uncommitted changes (will abort if found)
 2. Pulls the latest changes from the repository
-3. Bumps the version number in `lib/cypress_on_rails/version.rb`
-4. Creates a git commit with the version bump
-5. Creates a git tag for the new version
-6. Pushes the commit and tag to GitHub
-7. Builds the gem
-8. Publishes the gem to RubyGems
+3. Bumps the version number in `lib/cypress_on_rails/version.rb` using `gem bump`
+4. Creates a git commit with the version bump message
+5. Creates a git tag for the new version (e.g., `v1.19.0`)
+6. Pushes the commit to GitHub
+7. Pushes the tag to GitHub
+8. Builds the gem
+9. Publishes the gem to RubyGems (requires OTP)
 
 ## Troubleshooting
 

lib/tasks/release.rake

@@ -32,10 +32,19 @@ task :release, %i[gem_version dry_run] do |_t, args|
 
   # See https://github.com/svenfuchs/gem-release
   sh_in_dir(gem_root, "git pull --rebase")
-  sh_in_dir(gem_root, "gem bump --no-commit #{%(--version #{gem_version}) unless gem_version.strip.empty?}")
 
-  # Release the new gem version
-  puts "Carefully add your OTP for Rubygems. If you get an error, run 'gem release' again."
+  # Bump version, commit, and tag (gem bump does all of this)
+  bump_command = "gem bump"
+  bump_command << " --version #{gem_version}" unless gem_version.strip.empty?
+  bump_command << " --skip-ci" # Skip CI on version bump commit
+  sh_in_dir(gem_root, bump_command)
+
+  # Push the commit and tag
+  sh_in_dir(gem_root, "git push") unless is_dry_run
+  sh_in_dir(gem_root, "git push --tags") unless is_dry_run
+
+  # Release the new gem version to RubyGems
+  puts "\nCarefully add your OTP for Rubygems. If you get an error, run 'gem release' again."
   sh_in_dir(gem_root, "gem release") unless is_dry_run
 
   msg = <<~MSG