version_gem 1.1.9 → 1.1.12

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: cd4a5c38f28eb3f9c215684dfeb3d7b8eed4e26a76e5a5fbab98937aa17a147c
-  data.tar.gz: 494810d3d25c269eb3867fa9c600df69354c45438c35bae8087912e3165e086c
+  metadata.gz: 036c36e35a1bba8fb12b5a2e8ad2fb960070487462f56a906e07abc1f269a8f0
+  data.tar.gz: 49e719e30a2e23747b5ca0f262926da0f3dbac329cdb9bf441c063fbca985565
 SHA512:
-  metadata.gz: e85bc0c821117c19ed6c08427b4dee64792b49453bad2885d03e195236ba863c2048eba779fab77c15efefcbba8eccff20eaca9f1465adba96736b3081e4cef8
-  data.tar.gz: d1e488c79e04c025dd1cb6fe33d6908513b3e15275d8f4e682a7f61ce258ec7d8b6d47e9f948f9bb1c10ad86cf63f0855ec9aa2c3605112b77470da3c91d6bca
+  metadata.gz: 100e2c8fd944bdbcbb4630b1a6cdf1f18c1e84812a7660d0d96b919b9f0a82f4fa7ece31fa44980c2c4e73622be5d7efc7f8af2bc455af90135d8c6bfad0b5bf
+  data.tar.gz: d7f870ceea407bf03a615ba0fe27deedcf4db724bd7a0f4380a6d8d4dbfacbc28462a28820cf339b7f8986d2a09ea86318ce0624a33b8928c5983ee5ecd8cd5e

data/CHANGELOG.md

@@ -17,34 +17,135 @@ Please file a bug if you notice a violation of semantic versioning.
 [📗keep-changelog-img]: https://img.shields.io/badge/keep--a--changelog-1.0.0-FFDD67.svg?style=flat
 
 ## [Unreleased]
+
 ### Added
+
 ### Changed
+
 ### Deprecated
+
 ### Removed
+
 ### Fixed
+
 ### Security
 
+## [1.1.12] - 2026-06-14
+
+- TAG: [v1.1.12][1.1.12t]
+- COVERAGE: 100.00% -- 58/58 lines in 2 files
+- BRANCH COVERAGE: 0.00% -- 0/0 branches in 2 files
+- 85.19% documented
+
+### Changed
+
+- Retemplated repository metadata, workflows, modular gemfiles, and documentation
+  scaffolding with the current `kettle-jem` template.
+
+### Fixed
+
+- Restored `docs/CNAME` so the generated documentation site keeps its custom domain.
+- Corrected misspelled contact metadata to use `galtzo.com`.
+
+## [1.1.11] - 2026-06-06
+
+- TAG: [v1.1.11][1.1.11t]
+- COVERAGE: 100.00% -- 58/58 lines in 2 files
+- BRANCH COVERAGE: 0.00% -- 0/0 branches in 2 files
+- 85.19% documented
+
+### Added
+
+- Added the generated `appraisal2` binstub.
+
+### Changed
+
+- Refreshed generated CI workflows, README support badges, gemspec development
+  dependency floors, and template metadata from the current kettle-jem
+  template.
+- Updated generated Appraisal2 integration to use the `appraisal2-rubocop`
+  plugin DSL and raised the generated `appraisal2` / `appraisal2-rubocop`
+  dependency floors.
+
+## [1.1.10] - 2026-06-02
+
+- TAG: [v1.1.10][1.1.10t]
+- COVERAGE: 100.00% -- 58/58 lines in 2 files
+- BRANCH COVERAGE: 0.00% -- 0/0 branches in 2 files
+- 85.19% documented
+
+### Added
+
+- StructuredMerge-managed template configuration under `.structuredmerge/`,
+  including semantic Git diff driver settings and kettle-drift integration.
+- `rubocop-gradual` baseline tracking for style checks.
+
+### Changed
+
+- Re-templated the project with the current kettle-jem / StructuredMerge
+  template.
+- Development and test dependency floors now use current template floors:
+  `kettle-dev` 2.0.7, `kettle-test` 2.0.3, `kettle-soup-cover` 2.0.0,
+  `turbo_tests2` 3.1.1, `rubocop-lts` 8.3.0, and
+  `rubocop-lts-rspec` 1.0.3.
+- Development and test tooling now targets Ruby 2.4 or newer while the
+  published runtime Ruby requirement remains Ruby 2.2 or newer.
+- RSpec setup now loads `kettle-test` helpers and kettle-soup-cover coverage
+  bootstrap from `spec/spec_helper.rb`.
+- Templating dependencies now load only when `K_JEM_TEMPLATING=true`, with
+  local StructuredMerge and Kettle workspace dependencies wired through
+  `SMORG_RB_DEV`, `KETTLE_RB_DEV`, and `nomono`.
+- Gem metadata and packaging inventory were refreshed by the template,
+  including homepage, wiki, license-file, and packaged file handling.
+
+### Removed
+
+- Removed the obsolete `.yard_gfm_support.rb` documentation hook; YARD setup now
+  uses the current template-managed plugin configuration.
+- Removed obsolete CI workflows for Ruby 2.3, JRuby 9.1, TruffleRuby 23.2,
+  CodeQL, framework CI, and Discord notifications.
+- Removed legacy generated binstubs in favor of the current curated
+  `kettle-check-eof`, `kettle-test`, and retained documentation binstubs.
+
+### Fixed
+
+- logo at top of README.md
+
+- Fixed the Style workflow RBS validation command so CI uses the bundled `rbs`
+  executable instead of the non-executable `bin/rbs` binstub.
+- Fixed the Coverage workflow so Codecov repository-registration/upload errors
+  do not fail CI after local coverage reports have already been generated and
+  verified.
+
 ## [1.1.9] - 2025-09-02
+
 - TAG: [v1.1.9][1.1.9t]
 - COVERAGE: 100.00% -- 118/118 lines in 8 files
 - BRANCH COVERAGE: 100.00% -- 4/4 branches in 8 files
 - 84.62% documented
+
 ### Added
+
 - re-templated gem using kettle-dev v1.1.2
   - new binstubs for changelog, readme, commit message, & release management
   - new CI workflows
   - enhanced project documentation
 - More RBS types
 - docs site: https://version-gem.galtzo.com
+
 ### Fixed
+
 - RBS types are more accurate
 
 ## [1.1.8] 2025-05-06
+
 - TAG: [1.1.8][1.1.8t]
 - COVERAGE: 100.00% -- 118/118 lines in 8 files
 - BRANCH COVERAGE: 100.00% -- 4/4 branches in 8 files
 - 84.62% documented
+
 ### Added
+
 - CITATION.cff (@pboling)
 - Cryptographically signed with new 20-year cert (@pboling)
   - expires 2045-04-29
@@ -53,25 +154,33 @@ Please file a bug if you notice a violation of semantic versioning.
 - GitLab CI, as an addition to existing GHA (@pboling)
 
 ## [1.1.7] 2025-04-15
+
 - TAG: [1.1.7][1.1.7t]
 - Line Coverage: 100.0% (117 / 117)
 - Branch Coverage: 100.0% (4 / 4)
 - 76.92% documented
+
 ### Added
+
 - Support for Epoch Semantic Versioning (@pboling)
   - `extend VersionGem::Epoch` in your library's `MyLib::Version` module
 - Support for JRuby 10 (@pboling)
 - More documentation (@pboling)
+
 ### Removed
+
 - Ruby 2.2 removed from CI, though technically still supported
   - can't run directly in GHA anymore
 
 ## [1.1.6] 2025-02-24
+
 - TAG: [1.1.6][1.1.6t]
 - Line Coverage: 100.0% (77 / 77)
 - Branch Coverage: 100.0% (2 / 2)
 - 77.78% documented
+
 ### Added
+
 - Support for JRuby 9.1, 9.2, 9.3, 9.4, and head (@pboling)
 - Support for Truffle Ruby 22.3, 23.0, 23.1, 24.1, and head (@pboling)
 - Evergreen current latest engine release workflow (@pboling)
@@ -79,19 +188,26 @@ Please file a bug if you notice a violation of semantic versioning.
 - Improved developer experience for contributors (@pboling)
 - More documentation (@pboling)
 - Switch to stone_checksums for checksum generation (@pboling)
+
 ### Changed
+
 - Code of Conduct updated - Contributor Covenant v2.0 => v2.1 (@pboling)
 
 ## [1.1.5] 2025-02-22
+
 - TAG: [1.1.5][1.1.5t]
 - Line Coverage: 100.0% (77 / 77)
 - Branch Coverage: 100.0% (2 / 2)
 - 77.78% documented
+
 ### Added
+
 - Document approach to get code coverage on your gem's version.rb file (@pboling)
 - More documentation, and yard task for documentation (@pboling)
 - Documentation of Ruby version and SemVer support (@pboling)
+
 ### Fixed
+
 - [#3](https://gitlab.com/ruby-oauth/version_gem/-/issues/3) - Allow packaging without signing (@pboling)
   - to support secure linux distros which have alternate means of signing packages within their package managers
 - Code coverage tracking (@pboling)
@@ -99,15 +215,23 @@ Please file a bug if you notice a violation of semantic versioning.
 - Improved gemspec config (@pboling)
 
 ## [1.1.4] 2024-03-21
+
 - TAG: [1.1.4][1.1.4t]
+
 ### Added
+
 - Ruby 3.3 to CI (@pboling)
+
 ### Fixed
+
 - Remove the executable bit from non-executable files (@Fryguy)
 
 ## [1.1.3] 2023-06-05
+
 - TAG: [1.1.3][1.1.3t]
+
 ### Added
+
 - More test coverage (now 100% 🎉) (@pboling)
 - Improved documentation (now 77% 🎉) (@pboling)
 - Gemfile context pattern (@pboling)
@@ -120,58 +244,90 @@ Please file a bug if you notice a violation of semantic versioning.
   - pry-suite
   - debase,  for IDE debugging
 - (dev) Rake task for rubocop_gradual (@pboling)
+
 ### Fixed
+
 - (dev) `yard` documentation task (@pboling)
+
 ### Removed
+
 - Formally drop Ruby 2.2 support
   - Ruby 2.2 was already de facto minimum version supported, which is why this wasn't a 2.0 release.
 
 ## [1.1.2] - 2023-03-17
+
 - TAG: [1.1.2][1.1.2t]
+
 ### Added
+
 - `VersionGem::Ruby` to help library CI integration against many different versions of Ruby (@pboling)
   - Experimental, optional, require (not loaded by default, which is why this can be in a patch)
 - Spec coverage is now 100%, lines and branches, including the fabled `version.rb` (@pboling)
 - Full RBS Signatures (@pboling)
 
 ## [1.1.1] - 2022-09-19
+
 - TAG: [1.1.1][1.1.1t]
+
 ### Added
+
 - Alternatives section to README.md (@pboling)
 - Signing cert for gem releases (@pboling)
 - Mailing List and other metadata URIs (@pboling)
 - Checksums for released gems (@pboling)
+
 ### Changed
+
 - SECURITY.md policy (@pboling)
 - Version methods are now memoized (||=) on initial call for performance (@pboling)
 - Gem releases are now cryptographically signed (@pboling)
 
 ## [1.1.0] - 2022-06-24
+
 - TAG: [1.1.0][1.1.0t]
+
 ### Added
+
 - RSpec Matchers and Shared Example (@pboling)
+
 ### Fixed
+
 - `to_a` uses same type casting as major, minor, patch, and pre (@pboling)
 
 ## [1.0.2] - 2022-06-23
+
 - TAG: [1.0.2][1.0.2t]
+
 ### Added
+
 - Delay loading of library code until after code coverage tool is loaded (@pboling)
 
 ## [1.0.1] - 2022-06-23
+
 - TAG: [1.0.1][1.0.1t]
+
 ### Added
+
 - CI Build improvements (@pboling)
 - Code coverage reporting (@pboling)
 - Documentation improvements (@pboling)
 - Badges! (@pboling)
 
 ## [1.0.0] - 2022-06-21
+
 - TAG: [1.0.0][1.0.0t]
+
 ### Added
+
 - Initial release, with basic version parsing API (@pboling)
 
-[Unreleased]: https://github.com/ruby-oauth/version_gem/compare/v1.1.9...HEAD
+[Unreleased]: https://github.com/ruby-oauth/version_gem/compare/v1.1.12...HEAD
+[1.1.12]: https://github.com/ruby-oauth/version_gem/compare/v1.1.11...v1.1.12
+[1.1.12t]: https://github.com/ruby-oauth/version_gem/releases/tag/v1.1.12
+[1.1.11]: https://github.com/ruby-oauth/version_gem/compare/v1.1.10...v1.1.11
+[1.1.11t]: https://github.com/ruby-oauth/version_gem/releases/tag/v1.1.11
+[1.1.10]: https://github.com/ruby-oauth/version_gem/compare/v1.1.9...v1.1.10
+[1.1.10t]: https://github.com/ruby-oauth/version_gem/releases/tag/v1.1.10
 [1.1.9]: https://github.com/ruby-oauth/version_gem/compare/v1.1.8...v1.1.9
 [1.1.9t]: https://github.com/ruby-oauth/version_gem/releases/tag/v1.1.9
 [1.1.8]: https://gitlab.com/ruby-oauth/version_gem/-/compare/v1.1.7...v1.1.8

data/CITATION.cff

@@ -1,19 +1,19 @@
 cff-version: 1.2.0
-title: version_gem
+title: "version_gem"
 message: >-
   If you use this work and you want to cite it,
   then you can use the metadata from this file.
 type: software
 authors:
-  - given-names: Peter Hurn
-    family-names: Boling
-    email: peter@railsbling.com
-    affiliation: railsbling.com
+  - given-names: "Peter H."
+    family-names: "Boling"
+    email: "floss@galtzo.com"
+    affiliation: "galtzo.com"
     orcid: 'https://orcid.org/0009-0008-8519-441X'
 identifiers:
   - type: url
     value: 'https://github.com/ruby-oauth/version_gem'
-    description: version_gem
+    description: "version_gem"
 repository-code: 'https://github.com/ruby-oauth/version_gem'
 abstract: >-
   version_gem

data/CONTRIBUTING.md

@@ -8,19 +8,63 @@ To submit a patch, please fork the project, create a patch with tests, and send
 
 Remember to [![Keep A Changelog][📗keep-changelog-img]][📗keep-changelog] if you make changes.
 
+## Developer Certificate of Origin
+
+In order to protect users of this project, we require all contributors to comply with the
+[Developer Certificate of Origin](https://developercertificate.org/).
+This ensures that all contributions are properly licensed and attributed.
+
 ## Help out!
 
-Take a look at the `reek` list which is the file called `REEK` and find something to improve.
+Take a look at the open issues and pull requests, or use the gem and find something to improve.
 
 Follow these instructions:
 
-1. Fork the repository
-2. Create a feature branch (`git checkout -b my-new-feature`)
-3. Make some fixes.
-4. Commit changes (`git commit -am 'Added some feature'`)
-5. Push to the branch (`git push origin my-new-feature`)
-6. Make sure to add tests for it. This is important, so it doesn't break in a future release.
-7. Create new Pull Request.
+1. Join the Discord: [![Live Chat on Discord][✉️discord-invite-img]][✉️discord-invite]
+2. Fork the repository
+3. Create your feature branch (`git checkout -b my-new-feature`)
+4. Make some fixes.
+5. Commit your changes (`git commit -am 'Added some feature'`)
+6. Push to the branch (`git push origin my-new-feature`)
+7. Make sure to add tests for it. This is important, so it doesn't break in a future release.
+8. Create new Pull Request.
+9. Announce it in the channel for this org in the [Discord][✉️discord-invite]!
+
+## Executables vs Rake tasks
+
+Executables shipped by dependencies, such as kettle-dev, and stone_checksums, are available
+after running `bin/setup`. These include:
+
+- gem_checksums
+- kettle-changelog
+- kettle-commit-msg
+- kettle-dev-setup
+- kettle-dvcs
+- kettle-pre-release
+- kettle-readme-backers
+- kettle-release
+
+There are many Rake tasks available as well. You can see them by running:
+
+```shell
+bin/rake -T
+```
+
+## Code quality checks
+
+Run the Reek task when you want a smell check that fails on current findings:
+
+```shell
+bin/rake reek
+```
+
+Refresh the checked-in `REEK` backlog through the rake task, not by redirecting
+the raw `reek` executable output. The rake task uses the project bundle and
+avoids stale generated binstubs shadowing the Reek gem executable:
+
+```shell
+bin/rake reek:update
+```
 
 ## Environment Variables for Local Development
 
@@ -32,7 +76,7 @@ General/runtime
 - CI: When set to true, adjusts default rake tasks toward CI behavior
 
 Coverage (kettle-soup-cover / SimpleCov)
-- K_SOUP_COV_DO: Enable coverage collection (default: true in .envrc)
+- K_SOUP_COV_DO: Enable coverage collection (default: true in `mise.toml`)
 - K_SOUP_COV_FORMATTERS: Comma-separated list of formatters (html, xml, rcov, lcov, json, tty)
 - K_SOUP_COV_MIN_LINE: Minimum line coverage threshold (integer, e.g., 100)
 - K_SOUP_COV_MIN_BRANCH: Minimum branch coverage threshold (integer, e.g., 100)
@@ -48,7 +92,9 @@ GitHub API and CI helpers
 Releasing and signing
 - SKIP_GEM_SIGNING: If set, skip gem signing during build/release
 - GEM_CERT_USER: Username for selecting your public cert in `certs/<USER>.pem` (defaults to $USER)
-- SOURCE_DATE_EPOCH: Reproducible build timestamp. `kettle-release` will set this automatically for the session.
+- SOURCE_DATE_EPOCH: Reproducible build timestamp.
+  - `kettle-release` will set this automatically for the session.
+  - Not needed on bundler >= 2.7.0, as reproducible builds have become the default.
 
 Git hooks and commit message helpers (exe/kettle-commit-msg)
 - GIT_HOOK_BRANCH_VALIDATE: Branch name validation mode (e.g., `jira`) or `false` to disable
@@ -56,43 +102,66 @@ Git hooks and commit message helpers (exe/kettle-commit-msg)
 - GIT_HOOK_FOOTER_SENTINEL: Required when footer append is enabled — a unique first-line sentinel to prevent duplicates
 - GIT_HOOK_FOOTER_APPEND_DEBUG: Extra debug output in the footer template (true/false)
 
-For a quick starting point, this repository’s `.envrc` shows sane defaults, and `.env.local` can override them locally.
+Git diff driver setup
+- Local setup writes repository `.gitattributes` entries and local Git `diff.smorg-*` command config so this checkout uses StructuredMerge semantic diffs.
+- Global setup registers `diff.smorg-*` commands once in the user Git config; use it when you work across several StructuredMerge-enabled repositories.
+- Include-file setup writes `.git/smorg/config` and includes it from local Git config, keeping command registrations out of the repository files.
+- Git hosting forges generally ignore external diff drivers, so pull request views may still show raw textual diffs even when local `git diff` uses semantic drivers.
+
+```console
+K_JEM_TEMPLATING=true bundle exec kettle-jem install
+```
+
+Troubleshooting Git diffs
+- Use `git diff --no-ext-diff` to compare against Git's built-in diff output.
+- Use `git diff --no-textconv` when a textconv projection obscures the raw file bytes you need to inspect.
+- If Git reports a missing `smorg-*` executable, rerun `bundle install` and the setup command above, then check `git config --local --get-regexp '^diff\.smorg-'`.
+- To remove managed local entries, run `K_JEM_TEMPLATING=true bundle exec kettle-jem install --undo`; remove global command registrations with `git config --global --unset-all diff.smorg-ruby.command`.
+
+For a quick starting point, this repository’s `mise.toml` defines the shared defaults, and `.env.local` can override them locally. Copy `.env.local.example` to `.env.local`, use `KEY=value` lines, and either activate `mise` in your shell or run commands through `mise exec -C /path/to/project -- ...`.
 
 ## Appraisals
 
 From time to time the [appraisal2][🚎appraisal2] gemfiles in `gemfiles/` will need to be updated.
+Generated appraisal and CI workflow floors are controlled by `ruby.test_minimum`
+in `.structuredmerge/kettle-jem.yml`; this project was templated with `ruby.test_minimum: 2.4`.
+That value describes the lowest Ruby version expected to run the test/development
+toolchain, and it may be higher than the gemspec runtime floor.
+
 They are created and updated with the commands:
 
 ```console
 bin/rake appraisal:update
 ```
 
-When adding an appraisal to CI, check the [runner tool cache][🏃‍♂️runner-tool-cache] to see which runner to use.
+If you need to reset all gemfiles/*.gemfile.lock files:
+
+```console
+bin/rake appraisal:reset
+```
 
-## The Reek List
+When adding an appraisal to CI, check the [runner tool cache][🏃‍♂️runner-tool-cache] to see which runner to use.
 
-Take a look at the `reek` list which is the file called `REEK` and find something to improve.
+## Run Tests
 
-To refresh the `reek` list:
+Run tests via `kettle-test` (provided by `kettle-test`). It runs RSpec, writes the full log to
+`tmp/kettle-test/rspec-TIMESTAMP.log`, and prints a compact highlight block with timing, seed,
+pass/fail count, failing example list, and SimpleCov coverage percentages.
 
 ```console
-bundle exec reek > REEK
+bundle exec kettle-test
 ```
 
-## Run Tests
-
-To run all tests
+For targeted runs, disable the hard coverage threshold to avoid false failures:
 
 ```console
-bundle exec rake test
+K_SOUP_COV_MIN_HARD=false bundle exec kettle-test spec/path/to/spec.rb
 ```
 
 ### Spec organization (required)
 
-- One spec file per class/module. For each class or module under `lib/`, keep all of its unit tests in a single spec file under `spec/` that mirrors the path and file name exactly: `lib/version_gem/release_cli.rb` -> `spec/version_gem/release_cli_spec.rb`.
-- Never add a second spec file for the same class/module. Examples of disallowed names: `*_more_spec.rb`, `*_extra_spec.rb`, `*_status_spec.rb`, or any other suffix that still targets the same class. If you find yourself wanting a second file, merge those examples into the canonical spec file for that class/module.
+- One spec file per class/module. For each class or module under `lib/`, keep all of its unit tests in a single spec file under `spec/` that mirrors the path and file name exactly: `lib/version_gem/my_class.rb` -> `spec/version_gem/my_class_spec.rb`.
 - Exception: Integration specs that intentionally span multiple classes. Place these under `spec/integration/` (or a clearly named integration folder), and do not directly mirror a single class. Name them after the scenario, not a class.
-- Migration note: If a duplicate spec file exists, move all examples into the canonical file and delete the duplicate. Do not leave stubs or empty files behind.
 
 ## Lint It
 
@@ -115,7 +184,7 @@ For more detailed information about using RuboCop in this project, please see th
 Never add `# rubocop:disable ...` / `# rubocop:enable ...` comments to code or specs (except when following the few existing `rubocop:disable` patterns for a rule already being disabled elsewhere in the code). Instead:
 
 - Prefer configuration-based exclusions when a rule should not apply to certain paths or files (e.g., via `.rubocop.yml`).
-- When a violation is temporary and you plan to fix it later, record it in `.rubocop_gradual.lock` using the gradual workflow:
+- When a violation is temporary, and you plan to fix it later, record it in `.rubocop_gradual.lock` using the gradual workflow:
   - `bundle exec rake rubocop_gradual:autocorrect` (preferred)
   - `bundle exec rake rubocop_gradual:force_update` (only when you cannot fix the violations immediately)
 
@@ -138,7 +207,7 @@ Also see GitLab Contributors: [https://gitlab.com/ruby-oauth/version_gem/-/graph
 **IMPORTANT**: To sign a build,
 a public key for signing gems will need to be picked up by the line in the
 `gemspec` defining the `spec.cert_chain` (check the relevant ENV variables there).
-All releases to RubyGems.org are signed releases.
+All releases are signed releases.
 See: [RubyGems Security Guide][🔒️rubygems-security-guide]
 
 NOTE: To build without signing the gem set `SKIP_GEM_SIGNING` to any value in the environment.
@@ -147,47 +216,49 @@ NOTE: To build without signing the gem set `SKIP_GEM_SIGNING` to any value in th
 
 #### Automated process
 
-1. Update version.rb to contian the correct version-to-be-released.
+1. Update version.rb to contain the correct version-to-be-released.
 2. Run `bundle exec kettle-changelog`.
 3. Run `bundle exec kettle-release`.
+4. Stay awake and monitor the release process for any errors, and answer any prompts.
 
 #### Manual process
 
 1. Run `bin/setup && bin/rake` as a "test, coverage, & linting" sanity check
 2. Update the version number in `version.rb`, and ensure `CHANGELOG.md` reflects changes
 3. Run `bin/setup && bin/rake` again as a secondary check, and to update `Gemfile.lock`
-4. Run `git commit -am "🔖 Prepare release v<VERSION>"` to commit the changes
-5. Run `git push` to trigger the final CI pipeline before release, and merge PRs
+4. Run `bin/rake yard` to regenerate the docs site using the canonical docs task
+5. Run `git commit -am "🔖 Prepare release v<VERSION>"` to commit the changes
+6. Run `git push` to trigger the final CI pipeline before release, and merge PRs
     - NOTE: Remember to [check the build][🧪build].
-6. Run `export GIT_TRUNK_BRANCH_NAME="$(git remote show origin | grep 'HEAD branch' | cut -d ' ' -f5)" && echo $GIT_TRUNK_BRANCH_NAME`
-7. Run `git checkout $GIT_TRUNK_BRANCH_NAME`
-8. Run `git pull origin $GIT_TRUNK_BRANCH_NAME` to ensure latest trunk code
-9. Optional for older Bundler (< 2.7.0): Set `SOURCE_DATE_EPOCH` so `rake build` and `rake release` use the same timestamp and generate the same checksums
+7. Run `export GIT_TRUNK_BRANCH_NAME="$(git remote show origin | grep 'HEAD branch' | cut -d ' ' -f5)" && echo $GIT_TRUNK_BRANCH_NAME`
+8. Run `git checkout $GIT_TRUNK_BRANCH_NAME`
+9. Run `git pull origin $GIT_TRUNK_BRANCH_NAME` to ensure latest trunk code
+10. Optional for older Bundler (< 2.7.0): Set `SOURCE_DATE_EPOCH` so `rake build` and `rake release` use the same timestamp and generate the same checksums
     - If your Bundler is >= 2.7.0, you can skip this; builds are reproducible by default.
     - Run `export SOURCE_DATE_EPOCH=$EPOCHSECONDS && echo $SOURCE_DATE_EPOCH`
     - If the echo above has no output, then it didn't work.
     - Note: `zsh/datetime` module is needed, if running `zsh`.
     - In older versions of `bash` you can use `date +%s` instead, i.e. `export SOURCE_DATE_EPOCH=$(date +%s) && echo $SOURCE_DATE_EPOCH`
-10. Run `bundle exec rake build`
-11. Run `bin/gem_checksums` (more context [1][🔒️rubygems-checksums-pr], [2][🔒️rubygems-guides-pr])
+11. Run `bundle exec rake build`
+12. Run `bin/gem_checksums` (more context [1][🔒️rubygems-checksums-pr], [2][🔒️rubygems-guides-pr])
     to create SHA-256 and SHA-512 checksums. This functionality is provided by the `stone_checksums`
     [gem][💎stone_checksums].
     - The script automatically commits but does not push the checksums
-12. Sanity check the SHA256, comparing with the output from the `bin/gem_checksums` command:
+13. Sanity check the SHA256, comparing with the output from the `bin/gem_checksums` command:
     - `sha256sum pkg/<gem name>-<version>.gem`
-13. Run `bundle exec rake release` which will create a git tag for the version,
-    push git commits and tags, and push the `.gem` file to [rubygems.org][💎rubygems]
+14. Run `bundle exec rake release` which will create a git tag for the version,
+    push git commits and tags, and push the `.gem` file to the gem host configured in the gemspec.
 
-[📜src-gl]: https://gitlab.com/ruby-oauth/version_gem/
+[📜src-gl]: https://gitlab.com/ruby-oauth/version_gem
 [📜src-cb]: https://codeberg.org/ruby-oauth/version_gem
 [📜src-gh]: https://github.com/ruby-oauth/version_gem
 [🧪build]: https://github.com/ruby-oauth/version_gem/actions
-[🤝conduct]: https://gitlab.com/ruby-oauth/version_gem/-/blob/main/CODE_OF_CONDUCT.md
+[🤝conduct]: https://github.com/ruby-oauth/version_gem/blob/main/CODE_OF_CONDUCT.md
 [🖐contrib-rocks]: https://contrib.rocks
 [🖐contributors]: https://github.com/ruby-oauth/version_gem/graphs/contributors
 [🚎contributors-gl]: https://gitlab.com/ruby-oauth/version_gem/-/graphs/main
 [🖐contributors-img]: https://contrib.rocks/image?repo=ruby-oauth/version_gem
-[💎rubygems]: https://rubygems.org
+[💎gem-coop]: https://gem.coop
 [🔒️rubygems-security-guide]: https://guides.rubygems.org/security/#building-gems
 [🔒️rubygems-checksums-pr]: https://github.com/rubygems/rubygems/pull/6022
 [🔒️rubygems-guides-pr]: https://github.com/rubygems/guides/pull/325
@@ -198,3 +269,4 @@ NOTE: To build without signing the gem set `SKIP_GEM_SIGNING` to any value in th
 [📌major-versions-not-sacred]: https://tom.preston-werner.com/2022/05/23/major-version-numbers-are-not-sacred.html
 [🚎appraisal2]: https://github.com/appraisal-rb/appraisal2
 [🏃‍♂️runner-tool-cache]: https://github.com/ruby/ruby-builder/releases/tag/toolcache
+[✉️discord-invite]: https://discord.gg/3qme4XHNKN