typical_sort 0.0.2.pre.rc → 0.0.2

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: b87dbf5641b61d4d91226f1e1ac41d0023111feff95e66ecafe556811d1ba35a
-  data.tar.gz: c8938919d3aacb024d5b053e2e447d9c1431dd41f1be11b9face066a1c7c9676
+  metadata.gz: e562e9296dbb12e4cf437144bfe2b108fe07409f8b70bf844e20f69de7193908
+  data.tar.gz: 9c3565e404b3b5bcd6eacb58ff52061b0c7f09a3a4be8350c80f48c96d3e1964
 SHA512:
-  metadata.gz: 59552e79bd79dd6467be238ecabdcccf64bccba01877718e1a6d00178011ba93926eb57af60bb61d8834f77161e154e1db01f510e18954319b6c654050dbca97
-  data.tar.gz: 3ef98d235347bb12e36532bc9314b97981c8ed9e99ca477563e617f394065ac20db1b32baab503c2c7a347315a2361710e1a872eaf371a650041c34c67564f5e
+  metadata.gz: 215dd94a7bb316c864574d106b8fae4980e8a36383408bbbdf038d6d538ac9c52e22b82d0e9f8c7d7b2e7569ea4223a250f1650ac14433aa8d8c0cbbb86b3642
+  data.tar.gz: 4039750518702381bbe6dedffe1618dd44544307f30e46692a6204f9310099e48ef2645e858719d6beae2cf785e74474c695e8b12dcfcb88e8360b21c5906c25

data/README.md

@@ -194,18 +194,35 @@ bundle exec appraisal rspec
 bundle exec standardrb
 ```
 
-### Releasing
+## Releases
 
-Create a release from `main`:
+Releases are driven by git tags. The version lives in `lib/typical_sort/version.rb`, and the gemspec reads `TypicalSort::VERSION`.
 
-```sh
-bin/release {major|minor|patch|pre}
-git push --follow-tags
+
+```bash
+bundle install
+bin/release patch # or: minor, major
+```
+
+To publish an RC for a specific version:
+
+```bash
+bin/release rc 1.2.0
 ```
 
-The release script validates the repository, bumps the version, creates a git tag.
+This sets the version to `1.2.0-rc` and tags it as `v1.2.0-rc`.
+
+Prereleases can also use `bump`'s native `pre` increment:
+
+```bash
+bin/release pre
+```
+
+`pre` cycles prerelease labels in order: `alpha`, `beta`, `rc`, then the final version. For example, `1.2.0-rc` becomes `1.2.0`, tagged as `v1.2.0`.
+
+`bin/release` uses `bump`, commits the version file, creates a `v<version>` tag, pushes the branch, and pushes the tag.
 
-Publishing to RubyGems and creating a GitHub Release are handled automatically by GitHub Actions.
+GitHub Actions publishes only when a `v*` tag is pushed. The publish workflow builds the gem and pushes it to RubyGems with `RUBYGEMS_API_KEY`.
 
 ## Contributing
 

data/lib/typical_sort/version.rb

@@ -1,5 +1,5 @@
 # frozen_string_literal: true
 
 module TypicalSort
-  VERSION = "0.0.2-rc"
+  VERSION = "0.0.2"
 end

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: typical_sort
 version: !ruby/object:Gem::Version
-  version: 0.0.2.pre.rc
+  version: 0.0.2
 platform: ruby
 authors:
 - Wyatt Kirby