kettle-dev 2.0.0 → 2.0.2

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 1c27526850f356cd31b634aa7a0ea70c4f96664c2979629ecfdabcf128f6b437
-  data.tar.gz: dca1af6fba35002062780e10688a42181eeb577804d48f3a367399fcf8da3262
+  metadata.gz: c3bad017c27149d9c7bf639bf70347f639d9301b3ce355c9a20eb7466f959df0
+  data.tar.gz: 8c96fb38ea79b64d55d2813725120518e1e3bcf2dda8396c8b2da1e3aa699d23
 SHA512:
-  metadata.gz: 16221f6055e6d28aa959d11a8b57c047218565538b55b6066a0656b5b8c45273c78f7ee1521369c247b9c8b296a485da22e4fa99c92ed276a67e39997281a14e
-  data.tar.gz: 71f4a045813776fba247aa28b728aaef9b4bfcc9013a806fdd9f5b49d99551aae505b34e8278c591e3a9c1d65bfb9581718460c10cf9a2354f17839fe0e6e191
+  metadata.gz: 21ad36073bf15fd42f052958148f8129138e4ab79195d524457ba5c29e206fd261f283b9b6616e7a41cc46b6455c27e1d763167f8b8e75655acf2cdaa1a5c713
+  data.tar.gz: fcef88758871ad5eb760e0671972c6ef389dd3d9037f5006ddd65d2d07c651c7778a86dd344e86815b37b0451833544ba10ef895db28c6fa5dd0221502013d95

data/CHANGELOG.md

@@ -30,6 +30,95 @@ Please file a bug if you notice a violation of semantic versioning.
 
 ### Security
 
+## [2.0.2] - 2026-05-27
+
+- TAG: [v2.0.2][2.0.2t]
+- COVERAGE: 94.71% -- 2937/3101 lines in 23 files
+- BRANCH COVERAGE: 78.23% -- 1200/1534 branches in 23 files
+- 76.40% documented
+
+### Changed
+
+- **BREAKING**: Raised the minimum Ruby version to 2.4.0, matching
+  `kettle-test` 2.x and its runtime `turbo_tests2` dependency.
+- `kettle-test` is now declared as a runtime dependency because the shipped rake
+  and changelog tasks invoke `bundle exec kettle-test`.
+- Refreshed generated template output for README badge formatting and
+  Ruby 2.4-targeted RuboCop LTS style dependencies.
+
+### Removed
+
+- Removed Ruby 2.3 and JRuby 9.1 CI workflows and appraisal gemfiles.
+
+### Fixed
+
+- `ci:act` and release CI monitoring now detect GitHub and GitLab repositories
+  when remotes use `git+ssh://` or `ssh://` URLs.
+- Appraisal-based CI gemfiles now load the version-appropriate VCR/WebMock
+  recording dependencies required by the spec helper without falling back to the
+  root Gemfile.
+- Reek, RuboCop-LTS, and coverage task specs now run in coverage CI without
+  requiring style-only dependencies.
+- Reek rake task specs no longer change the process working directory, avoiding
+  cross-spec project root leakage under turbo workers.
+- `rake reek:update` now raises a normal task error on unexpected reek exits
+  instead of calling `Kernel.abort`, so specs can assert the failure path without
+  poisoning the process exit status.
+- Coverage CI thresholds now match the repository `mise.toml` thresholds instead
+  of requiring unreachable 100% line and branch coverage.
+- `kettle-changelog` now fails closed when `kettle-test` does not produce the
+  expected collated `coverage/coverage.json`, instead of merging worker coverage
+  files itself and hiding a coverage integration failure.
+- Regenerated templating now keeps `kettle-test` as a runtime dependency only
+  instead of duplicating it as both runtime and development dependency.
+- Replaced non-capturing `=~` checks with `Regexp#match?` so unlocked/style CI
+  stays clean with newer RuboCop performance cops.
+- Cleared the remaining `rubocop_gradual` backlog and removed the lock file.
+
+## [2.0.1] - 2026-05-25
+
+- TAG: [v2.0.1][2.0.1t]
+- COVERAGE: 94.88% -- 2911/3068 lines in 21 files
+- BRANCH COVERAGE: 78.43% -- 1200/1530 branches in 21 files
+- 76.25% documented
+
+### Added
+
+- Added `kettle-changelog --update-prep` to refresh the most recent prepared
+  release section in place, including date, coverage, documentation stats, and
+  any follow-up Unreleased notes.
+
+### Changed
+
+- `kettle-changelog` now generates strict coverage data with
+  `bundle exec kettle-test`, preserving the faster `turbo_tests2` runner.
+- `kettle-changelog` now treats configured coverage thresholds as a changelog
+  preparation gate by default; use `--no-coverage-threshold` or
+  `K_CHANGELOG_COVERAGE_HARD=false` to generate changelog metadata without
+  threshold enforcement.
+- The shared `rake spec` task now delegates to `bundle exec kettle-test`, so
+  projects using kettle-dev automatically pick up kettle-test's default
+  `turbo_tests2` runner and summary output.
+- The shared `:yard` task now installs `yard-fence` and `yard-timekeeper` integrations explicitly so documentation prep and post-processing only run during `rake yard`
+
+- Refreshed generated kettle-jem templates, CI workflows, curated binstubs, and
+  local modular Gemfile wiring.
+- `kettle-changelog` now auto-selects the correct no-argument action by
+  comparing `version.rb`, the latest live release, and the most recent
+  CHANGELOG.md release section before prompting for confirmation.
+- Updated the development dependency on `kettle-test` to require 2.0.1 or newer.
+
+### Fixed
+
+- Loading YARD during unrelated rake tasks no longer triggers documentation plugin side effects that rewrite or clear `docs/`
+
+- `rake reek:update` now resolves the Reek gem executable directly instead of
+  shelling through `bundle exec reek`, avoiding stale project binstubs, and no
+  longer fails the default task solely because Reek reported smells while
+  refreshing the `REEK` backlog file.
+- `rake reek:update` now keeps `REEK` zero-byte when Reek reports no smells
+  instead of writing a single blank line.
+
 ## [2.0.0] - 2026-02-25
 
 - TAG: [v2.0.0][2.0.0t]
@@ -1674,7 +1763,11 @@ Please file a bug if you notice a violation of semantic versioning.
   - Selecting will run the selected workflow via `act`
   - This may move to its own gem in the future.
 
-[Unreleased]: https://github.com/kettle-rb/kettle-dev/compare/v2.0.0...HEAD
+[Unreleased]: https://github.com/kettle-rb/kettle-dev/compare/v2.0.2...HEAD
+[2.0.2]: https://github.com/kettle-rb/kettle-dev/compare/v2.0.1...v2.0.2
+[2.0.2t]: https://github.com/kettle-rb/kettle-dev/releases/tag/v2.0.2
+[2.0.1]: https://github.com/kettle-rb/kettle-dev/compare/v2.0.0...v2.0.1
+[2.0.1t]: https://github.com/kettle-rb/kettle-dev/releases/tag/v2.0.1
 [2.0.0]: https://github.com/kettle-rb/kettle-dev/compare/v1.2.5...v2.0.0
 [2.0.0t]: https://github.com/kettle-rb/kettle-dev/releases/tag/v2.0.0
 [1.2.5]: https://github.com/kettle-rb/kettle-dev/compare/v1.2.4...v1.2.5

data/CITATION.cff

@@ -1,19 +1,19 @@
 cff-version: 1.2.0
-title: kettle-dev
+title: "kettle-dev"
 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: floss@galtzo.com
-    affiliation: galtzo.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/kettle-rb/kettle-dev'
-    description: kettle-dev
+    description: "kettle-dev"
 repository-code: 'https://github.com/kettle-rb/kettle-dev'
 abstract: >-
   kettle-dev

data/CONTRIBUTING.md

@@ -8,19 +8,27 @@ 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
 
@@ -42,6 +50,22 @@ There are many Rake tasks available as well. You can see them by running:
 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
 
 Below are the primary environment variables recognized by stone_checksums (and its integrated tools). Unless otherwise noted, set boolean values to the string "true" to enable.
@@ -52,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)
@@ -78,11 +102,16 @@ 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.
+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 `.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
@@ -97,22 +126,20 @@ bin/rake appraisal:reset
 
 When adding an appraisal to CI, check the [runner tool cache][🏃‍♂️runner-tool-cache] to see which runner to use.
 
-## The Reek List
-
-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)
@@ -183,33 +210,34 @@ NOTE: To build without signing the gem set `SKIP_GEM_SIGNING` to any value in th
 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,
+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/kettle-rb/kettle-dev/
+[📜src-gl]: https://gitlab.com/kettle-rb/kettle-dev
 [📜src-cb]: https://codeberg.org/kettle-rb/kettle-dev
 [📜src-gh]: https://github.com/kettle-rb/kettle-dev
 [🧪build]: https://github.com/kettle-rb/kettle-dev/actions
-[🤝conduct]: https://gitlab.com/kettle-rb/kettle-dev/-/blob/main/CODE_OF_CONDUCT.md
+[🤝conduct]: https://github.com/kettle-rb/kettle-dev/blob/main/CODE_OF_CONDUCT.md
 [🖐contrib-rocks]: https://contrib.rocks
 [🖐contributors]: https://github.com/kettle-rb/kettle-dev/graphs/contributors
 [🚎contributors-gl]: https://gitlab.com/kettle-rb/kettle-dev/-/graphs/main
@@ -225,3 +253,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

data/FUNDING.md

@@ -19,7 +19,7 @@ Many paths lead to being a sponsor or a backer of this project. Are you on such
 [🖇polar-img]: https://img.shields.io/badge/polar-donate-a51611.svg?style=flat
 [🖇polar]: https://polar.sh/pboling
 [🖇kofi-img]: https://img.shields.io/badge/ko--fi-%E2%9C%93-a51611.svg?style=flat
-[🖇kofi]: https://ko-fi.com/O5O86SNP4
+[🖇kofi]: https://ko-fi.com/pboling
 [🖇patreon-img]: https://img.shields.io/badge/patreon-donate-a51611.svg?style=flat
 [🖇patreon]: https://patreon.com/galtzo
 [🖇buyme-small-img]: https://img.shields.io/badge/buy_me_a_coffee-%E2%9C%93-a51611.svg?style=flat

data/LICENSE.md

@@ -0,0 +1,12 @@
+# License
+
+This project is made available under the following license.
+Choose the option that best fits your use case:
+
+- [AGPL-3.0-only](AGPL-3.0-only.md)
+
+If none of the above licenses fit your use case, please [contact us](mailto:floss@galtzo.com) to discuss a custom commercial license.
+
+## Copyright Notice
+
+Copyright (c) 2023, 2025-2026 Peter H. Boling