njtransit 1.0.1 → 1.0.2

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 824c0e3fd0a5921a775881350ea4436211d185697f3e3c373f6a8376fdc58a4a
-  data.tar.gz: affa507b623dc9cff86521ec28dcbb63ae758f4d186172fa8aed32c284d29ec0
+  metadata.gz: 2abeacafb30ae8fdec421187724fea1c7bfa00df19344984f1138a799d2fc974
+  data.tar.gz: cbd9fda233463cb4897e428c05428069b9f77a2aa68d92ca0aea2c6a29846d15
 SHA512:
-  metadata.gz: 99bd713024ca48637cd4c09de6bdf7e231685887ebab1a5758d4b4f755ffdce2b929abf5ef0933fbdf80ec737072096a3226e3c1a72b4d006d07bd2b95a15928
-  data.tar.gz: db3ea5db5832b6d54fcb832728f7b06711c9860aa05cd266a6f1f059e6b604588da4f1f9e68264dd5a560e678217e10fd677ba0a25ee7020dcdbc25454ae4469
+  metadata.gz: 27c56fd3517b457de75289073ced127401d8e6afd2a585000cead15c96f3a1053536f80ea5ab2c26952ae148687575e25b80a15013a6fd578ecbcbf037b9aa54
+  data.tar.gz: 846130fe78d8db87cae6ba253b639176eea10f75d918dc21ccbcd1454a85ebb7c0208e4c11ddc676d5a4016ff72fe39cf558b33afd9f91e1ff60d26b325b8986

data/CHANGELOG.md

@@ -4,6 +4,17 @@ All notable changes to this project will be documented in this file.
 
 ## [Unreleased]
 
+## [1.0.2] - 2026-03-27
+
+### Added
+
+- `bin/release-watch` — monitors release workflow and confirms gem is live on RubyGems
+
+### Changed
+
+- Updated CLAUDE.md step 8 to use `bin/release-watch`
+- Updated README.md with CI and release tooling documentation
+
 ## [1.0.1] - 2026-03-27
 
 ### Fixed

data/CLAUDE.md

@@ -141,10 +141,20 @@ gh pr merge <pr-number> --merge
 If version was bumped, a release workflow runs automatically on merge to main:
 1. Runs the test suite
 2. Builds the gem
-3. Publishes to RubyGems
+3. Publishes to RubyGems (via Trusted Publishing / OIDC)
 4. Creates a GitHub release with the gem attached
 
-Monitor with: `gh run watch` (select the Release workflow). Confirm gem was published to rubygems.org.
+```bash
+bin/release-watch                # Check once
+bin/release-watch --poll         # Poll every 15s until done
+bin/release-watch --poll 30      # Poll every 30s
+```
+
+Exit codes: `0` = gem published, `1` = workflow failed, `2` = still in progress.
+
+- **Exit 0**: gem is live on RubyGems — proceed to cleanup
+- **Exit 1**: investigate failure, propose fix — do NOT delete branch
+- **Exit 2**: check again later
 
 ### 9. Cleanup (only after release is healthy)
 

data/README.md

@@ -135,10 +135,21 @@ Claude writes and runs Ruby code against the gem to answer your question. It's a
 
 ```sh
 bin/setup          # Install dependencies
-bundle exec rspec  # Run tests (153 specs)
+bundle exec rspec  # Run tests
 bin/console        # Interactive prompt
 ```
 
+### CI & Release
+
+CI runs automatically on pull requests (RuboCop + RSpec on Ruby 3.2/3.3). Merging to main with a version bump triggers the release workflow, which publishes to RubyGems via Trusted Publishing and creates a GitHub release.
+
+```sh
+bin/ci-watch <pr-number>         # Check CI status for a PR
+bin/ci-watch <pr-number> --poll  # Poll until CI completes
+bin/release-watch                # Check release workflow status
+bin/release-watch --poll         # Poll until gem is published
+```
+
 ## Contributing
 
 Bug reports and pull requests are welcome at [github.com/jayrav13/njtransit](https://github.com/jayrav13/njtransit).

data/lib/njtransit/version.rb

@@ -1,5 +1,5 @@
 # frozen_string_literal: true
 
 module NJTransit
-  VERSION = "1.0.1"
+  VERSION = "1.0.2"
 end

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: njtransit
 version: !ruby/object:Gem::Version
-  version: 1.0.1
+  version: 1.0.2
 platform: ruby
 authors:
 - Jay Ravaliya