appraisal2 3.0.6 → 3.0.7

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: d133d78a6198d0a3b26dd959c3c1f70e7106ca48c188639db816b594cbe821ed
-  data.tar.gz: 03e9f36d0704cd7f3c8bb6b9a79d318f5793a587e3e719084066f9cf91f395a4
+  metadata.gz: 2fd7b2532897ffc8ec3482977b8ac3e7f5dadc6330f03ad5c18fa5350b70d300
+  data.tar.gz: b956dae24c70033a97c9473e260ce4b12853d6f349170ce92365a10ad1681650
 SHA512:
-  metadata.gz: e9d4d82c677bd83ba21c8590f6a92c5fd475bb9374243744fceb353f3acd985f99fd8ec28b9309b5ffca09f25db5ddef76850fb5f8163f105353b41d7b1abf3a
-  data.tar.gz: d65eb45d17fd233ac1de8b36d34b186b9f6f8bf82fcc106f16c045df1c943a65fb017f739c9da2a3a01027934a3e9f0d6afb5044531caecffcd86788708b25a8
+  metadata.gz: 3d86e28bfe079c7e27e04f4ca77ee341dc6d34702e45a12ea1683faa634c148c0687543d8b8e39c3d11d1120347e8c044167518b4d1232d2a89465b311bec4db
+  data.tar.gz: 0fa994040fd7b1df01da2f0294e191002229fa44e3eb5b6d3b0e0f5ab6e181622735a2da4a9f958a8ec79d27e95196cf828d69c1d130c1012d3dd3c17ee5af9c

data/CHANGELOG.md

@@ -1,9 +1,20 @@
 # Changelog
 
-This file documents all notable changes to this project.
+[![SemVer 2.0.0][📌semver-img]][📌semver] [![Keep-A-Changelog 1.0.0][📗keep-changelog-img]][📗keep-changelog]
 
-Format: [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
-Versioning: [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
+All notable changes to this project will be documented in this file.
+
+The format is based on [Keep a Changelog][📗keep-changelog],
+and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html),
+and [yes][📌major-versions-not-sacred], platform and engine support are part of the [public API][📌semver-breaking].
+Please file a bug if you notice a violation of semantic versioning.
+
+[📌semver]: https://semver.org/spec/v2.0.0.html
+[📌semver-img]: https://img.shields.io/badge/semver-2.0.0-FFDD67.svg?style=flat
+[📌semver-breaking]: https://github.com/semver/semver/issues/716#issuecomment-869336139
+[📌major-versions-not-sacred]: https://tom.preston-werner.com/2022/05/23/major-version-numbers-are-not-sacred.html
+[📗keep-changelog]: https://keepachangelog.com/en/1.0.0/
+[📗keep-changelog-img]: https://img.shields.io/badge/keep--a--changelog-1.0.0-FFDD67.svg?style=flat
 
 ## [Unreleased]
 
@@ -17,8 +28,84 @@ Versioning: [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
 
 ### Fixed
 
+- Fixed acceptance test Bundler pinning so CI uses `BUNDLER_VERSION` instead of
+  RubyGems `_version_` selector arguments that staged `bin/bundle` binstubs do
+  not support.
+
 ### Security
 
+## [3.0.7] - 2026-06-05
+
+- TAG: [v3.0.7][3.0.7t]
+- COVERAGE: 89.69% -- 748/834 lines in 28 files
+- BRANCH COVERAGE: 80.61% -- 133/165 branches in 28 files
+- 42.69% documented
+
+### Added
+
+- Added `Appraisal2::Version` / `Appraisal2::VERSION` constants backed by
+  `version_gem`, including an RBS signature for the version namespace.
+- Added appraisal and CI coverage for runtime dependency HEADs, templating
+  self-tests, license scanning, Open Collective backer updates, and
+  per-engine/per-version Ruby workflows.
+- Added generated local-development support files, including `mise.toml`,
+  `.env.local.example`, StructuredMerge git driver configuration, and refreshed
+  contributor/operator guides.
+
+### Changed
+
+- Refreshed project automation and CI templates with the current `kettle-jem`
+  template output.
+- CI now runs appraisals through `Appraisal.root.gemfile`, installs each
+  appraisal with retry handling, and uses `kettle-test` as the default test
+  runner.
+- Runtime dependency matrix handling now includes extracted stdlib gem
+  appraisals for `erb`, `mutex_m`, and `stringio`, with version-specific
+  stdlib gemfiles selected by the active Ruby version.
+- Development tooling floors were refreshed, including `kettle-dev` 2.x,
+  `kettle-test` 2.x, `kettle-soup-cover` 2.x, `gitmoji-regex` 2.x, current
+  documentation gems, and `turbo_tests2` as the default test runner.
+- Gem metadata now uses the generated `licenses` field, GitHub source,
+  changelog, bug tracker, wiki, and funding URLs, and a generated version-gem
+  loader in the gemspec.
+- Documentation was refreshed for contributor setup, local environment
+  variables, appraisal maintenance, test execution, RuboCop Gradual, Reek, and
+  generated project automation.
+
+### Removed
+
+- Removed the Ruby 2.3 CI appraisal/workflow and replaced dashed Ruby workflow
+  filenames with dotted Ruby-version workflow names.
+- Removed the legacy CodeQL and Discord notifier workflows from the generated
+  workflow set.
+
+- Removed the stale duplicate Runtime Deps @ HEAD workflow that bypassed the
+  generated `dep-heads` appraisal workflow.
+
+### Fixed
+
+- Fixed local `kettle-test` acceptance spec isolation so parallel workers use
+  process-specific Bundler, gem build, and stage directories instead of
+  deleting each other's temporary workspaces.
+
+- Rendered generated `LICENSE.md` copyright notice lines as a Markdown list.
+
+- Fixed appraisal install commands so lockfiles with `BUNDLED WITH` install and
+  select that Bundler version instead of rewriting the lockfile with the parent
+  process Bundler.
+- Fixed local acceptance test isolation so `kettle-test` workers do not mix
+  Bundler versions or share user-level installer cache state.
+- Fixed JRuby 9.2 CI bootstrapping by installing RubyGems 3.3.27 and Bundler
+  2.3.27 instead of using the default JRuby toolchain versions.
+- Fixed CI failures by preserving Bundler-generated `bin/bundle` test binstubs
+  instead of replacing them with custom bundle wrappers.
+- Fixed Ruby 3.0 and 3.1 appraisal stdlib gemfiles so they do not load
+  conflicting `erb` version constraints.
+- Fixed TruffleRuby 23.1 CI bootstrapping by routing that workflow through the
+  Ruby 3.2 appraisal Gemfile, which applies the `json` ceiling only on
+  TruffleRuby 23.1, and by running the test command directly once that Gemfile
+  is active.
+
 ## [3.0.6] - 2026-02-17
 
 - TAG: [v3.0.6][3.0.6t]
@@ -205,7 +292,9 @@ Versioning: [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
   - code coverage tracked with Coveralls, QLTY.sh, and the kettle-soup-cover gem
   - other minor fixes and improvements
 
-[Unreleased]: https://github.com/appraisal-rb/appraisal2/compare/v3.0.6...HEAD
+[Unreleased]: https://github.com/appraisal-rb/appraisal2/compare/v3.0.7...HEAD
+[3.0.7]: https://github.com/appraisal-rb/appraisal2/compare/v3.0.6...v3.0.7
+[3.0.7t]: https://github.com/appraisal-rb/appraisal2/releases/tag/v3.0.7
 [3.0.6]: https://github.com/appraisal-rb/appraisal2/compare/v3.0.5...v3.0.6
 [3.0.6t]: https://github.com/appraisal-rb/appraisal2/releases/tag/v3.0.6
 [3.0.5]: https://github.com/appraisal-rb/appraisal2/compare/v3.0.4...v3.0.5

data/CITATION.cff

@@ -0,0 +1,20 @@
+cff-version: 1.2.0
+title: "appraisal2"
+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 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/pboling/appraisal2'
+    description: "appraisal2"
+repository-code: 'https://github.com/pboling/appraisal2'
+abstract: >-
+  appraisal2
+license: See license file

data/CODE_OF_CONDUCT.md

@@ -1,4 +1,3 @@
-
 # Contributor Covenant Code of Conduct
 
 ## Our Pledge
@@ -61,7 +60,7 @@ representative at an online or offline event.
 
 Instances of abusive, harassing, or otherwise unacceptable behavior may be
 reported to the community leaders responsible for enforcement at
-[![Contact BDFL][🚂bdfl-contact-img]][🚂bdfl-contact].
+[![Contact Maintainer][🚂maint-contact-img]][🚂maint-contact].
 All complaints will be reviewed and investigated promptly and fairly.
 
 All community leaders are obligated to respect the privacy and security of the
@@ -131,5 +130,5 @@ For answers to common questions about this code of conduct, see the FAQ at
 [Mozilla CoC]: https://github.com/mozilla/diversity
 [FAQ]: https://www.contributor-covenant.org/faq
 [translations]: https://www.contributor-covenant.org/translations
-[🚂bdfl-contact]: http://www.railsbling.com/contact
-[🚂bdfl-contact-img]: https://img.shields.io/badge/Contact-BDFL-0093D0.svg?style=flat&logo=rubyonrails&logoColor=red
+[🚂maint-contact]: http://www.railsbling.com/contact
+[🚂maint-contact-img]: https://img.shields.io/badge/Contact-Maintainer-0093D0.svg?style=flat&logo=rubyonrails&logoColor=red

data/CONTRIBUTING.md

@@ -1,17 +1,24 @@
 # Contributing
 
-Bug reports and pull requests are welcome on GitLab at [https://gitlab.com/appraisal-rb/appraisal2][🚎src-main]
-. This project is intended to be a safe, welcoming space for collaboration, and contributors are expected to adhere to
+Bug reports and pull requests are welcome on [CodeBerg][📜src-cb], [GitLab][📜src-gl], or [GitHub][📜src-gh].
+This project should be a safe, welcoming space for collaboration, so contributors agree to adhere to
 the [code of conduct][🤝conduct].
 
-To submit a patch, please fork the project and create a patch with tests.
-Once you're happy with it send a pull request.
+To submit a patch, please fork the project, create a patch with tests, and send a pull request.
 
 Remember to [![Keep A Changelog][📗keep-changelog-img]][📗keep-changelog] if you make changes.
 
-## You can help!
+## Developer Certificate of Origin
 
-Simply follow these instructions:
+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 open issues and pull requests, or use the gem and find something to improve.
+
+Follow these instructions:
 
 1. Join the Discord: [![Live Chat on Discord][✉️discord-invite-img]][✉️discord-invite]
 2. Fork the repository
@@ -20,22 +27,107 @@ Simply follow these instructions:
 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. Run the at least one workflow of tests via `act`, e.g.,:
-    ```console
-    act -W '.github/workflows/ruby-3-3.yml'
-    ```
-    NOTE: Because there are so many workflows, running `act` naked might grind your machine to a halt.
-9. Create new Pull Request.
-10. Announce it in the channel for this org in the [Discord][✉️discord-invite]!
-
-NOTE: Run tests with `act` to have confidence they will pass in CI.
-      Also, because the spec run makes many changes to local bundle config,
-      many specs will fail locally in subsequent runs unless run via `act`.
-      The spec suite is not idempotent.  This is a goal for the future, if you'd like to work on it.
+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
+
+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.
+
+General/runtime
+- DEBUG: Enable extra internal logging for this library (default: false)
+- REQUIRE_BENCH: Enable `require_bench` to profile requires (default: false)
+- 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 `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)
+- K_SOUP_COV_MIN_HARD: Fail the run if thresholds are not met (true/false)
+- K_SOUP_COV_MULTI_FORMATTERS: Enable multiple formatters at once (true/false)
+- K_SOUP_COV_OPEN_BIN: Path to browser opener for HTML (empty disables auto-open)
+- MAX_ROWS: Limit console output rows for simplecov-console (e.g., 1)
+  Tip: When running a single spec file locally, you may want `K_SOUP_COV_MIN_HARD=false` to avoid failing thresholds for a partial run.
+
+GitHub API and CI helpers
+- GITHUB_TOKEN or GH_TOKEN: Token used by `ci:act` and release workflow checks to query GitHub Actions status at higher rate limits
+
+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.
+  - 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
+- GIT_HOOK_FOOTER_APPEND: Append a footer to commit messages when goalie allows (true/false)
+- 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)
+
+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
@@ -50,30 +142,26 @@ 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 against the current Ruby release:
+For targeted runs, disable the hard coverage threshold to avoid false failures:
 
 ```console
-bundle exec rake act
+K_SOUP_COV_MIN_HARD=false bundle exec kettle-test spec/path/to/spec.rb
 ```
 
-Or the equivalent:
+### Spec organization (required)
 
-```console
-act -W '.github/workflows/current.yml'
-```
-NOTE: Because there are so many workflows, running `act` naked might grind your machine to a halt.
+- 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/appraisal2/my_class.rb` -> `spec/appraisal2/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.
 
 ## Lint It
 
@@ -89,6 +177,19 @@ Or just run the linter.
 bundle exec rake rubocop_gradual:autocorrect
 ```
 
+For more detailed information about using RuboCop in this project, please see the [RUBOCOP.md](RUBOCOP.md) guide. This project uses `rubocop_gradual` instead of vanilla RuboCop, which requires specific commands for checking violations.
+
+### Important: Do not add inline RuboCop disables
+
+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:
+  - `bundle exec rake rubocop_gradual:autocorrect` (preferred)
+  - `bundle exec rake rubocop_gradual:force_update` (only when you cannot fix the violations immediately)
+
+As a general rule, fix style issues rather than ignoring them. For example, our specs should follow RSpec conventions like using `described_class` for the class under test.
+
 ## Contributors
 
 Your picture could be here!
@@ -97,7 +198,7 @@ Your picture could be here!
 
 Made with [contributors-img][🖐contrib-rocks].
 
-Also see GitLab Contributors: [https://gitlab.com/appraisal-rb/appraisal2/-/graphs/main][🚎contributors-gl]
+Also see GitLab Contributors: [https://gitlab.com/pboling/appraisal2/-/graphs/main][🚎contributors-gl]
 
 ## For Maintainers
 
@@ -109,7 +210,7 @@ a public key for signing gems will need to be picked up by the line in the
 All releases are signed releases.
 See: [RubyGems Security Guide][🔒️rubygems-security-guide]
 
-NOTE: To build without signing the gem you must set `SKIP_GEM_SIGNING` to some value in your environment.
+NOTE: To build without signing the gem set `SKIP_GEM_SIGNING` to any value in the environment.
 
 ### To release a new version:
 
@@ -125,43 +226,47 @@ NOTE: To build without signing the gem you must set `SKIP_GEM_SIGNING` to some v
 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-main]: https://gitlab.com/appraisal-rb/appraisal2
-[🧪build]: https://github.com/appraisal-rb/appraisal2/actions
-[🤝conduct]: https://gitlab.com/appraisal-rb/appraisal2/-/blob/main/CODE_OF_CONDUCT.md
+[📜src-gl]: https://gitlab.com/pboling/appraisal2
+[📜src-cb]: https://codeberg.org/pboling/appraisal2
+[📜src-gh]: https://github.com/pboling/appraisal2
+[🧪build]: https://github.com/pboling/appraisal2/actions
+[🤝conduct]: https://github.com/pboling/appraisal2/blob/main/CODE_OF_CONDUCT.md
 [🖐contrib-rocks]: https://contrib.rocks
-[🖐contributors]: https://github.com/appraisal-rb/appraisal2/graphs/contributors
-[🚎contributors-gl]: https://gitlab.com/appraisal-rb/appraisal2/-/graphs/main
-[🖐contributors-img]: https://contrib.rocks/image?repo=appraisal-rb/appraisal2
+[🖐contributors]: https://github.com/pboling/appraisal2/graphs/contributors
+[🚎contributors-gl]: https://gitlab.com/pboling/appraisal2/-/graphs/main
+[🖐contributors-img]: https://contrib.rocks/image?repo=pboling/appraisal2
 [💎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
-[💎stone_checksums]: https://github.com/pboling/stone_checksums
+[💎stone_checksums]: https://github.com/galtzo-floss/stone_checksums
 [📗keep-changelog]: https://keepachangelog.com/en/1.0.0/
 [📗keep-changelog-img]: https://img.shields.io/badge/keep--a--changelog-1.0.0-FFDD67.svg?style=flat
-[✉️discord-invite]: https://discord.gg/3qme4XHNKN
-[✉️discord-invite-img]: https://img.shields.io/discord/1373797679469170758?style=for-the-badge
+[📌semver-breaking]: https://github.com/semver/semver/issues/716#issuecomment-869336139
+[📌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

@@ -0,0 +1,74 @@
+<!-- RELEASE-NOTES-FOOTER-START -->
+
+Official Discord 👉️ [![Live Chat on Discord][✉️discord-invite-img]][✉️discord-invite]
+
+Many paths lead to being a sponsor or a backer of this project. Are you on such a path?
+
+[![OpenCollective Backers][🖇osc-backers-i]][🖇osc-backers] [![OpenCollective Sponsors][🖇osc-sponsors-i]][🖇osc-sponsors] [![Sponsor Me on Github][🖇sponsor-img]][🖇sponsor] [![Liberapay Goal Progress][⛳liberapay-img]][⛳liberapay] [![Donate on PayPal][🖇paypal-img]][🖇paypal]
+
+[![Buy me a coffee][🖇buyme-small-img]][🖇buyme] [![Donate on Polar][🖇polar-img]][🖇polar] [![Donate to my FLOSS efforts at ko-fi.com][🖇kofi-img]][🖇kofi] [![Donate to my FLOSS efforts using Patreon][🖇patreon-img]][🖇patreon]
+
+[⛳liberapay-img]: https://img.shields.io/liberapay/goal/pboling.svg?logo=liberapay&color=a51611&style=flat
+[⛳liberapay]: https://liberapay.com/pboling/donate
+[🖇osc-backers]: https://opencollective.com/#backer
+[🖇osc-backers-i]: https://opencollective.com//backers/badge.svg?style=flat
+[🖇osc-sponsors]: https://opencollective.com/#sponsor
+[🖇osc-sponsors-i]: https://opencollective.com//sponsors/badge.svg?style=flat
+[🖇sponsor-img]: https://img.shields.io/badge/Sponsor_Me!-pboling.svg?style=social&logo=github
+[🖇sponsor]: https://github.com/sponsors/pboling
+[🖇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/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
+[🖇buyme]: https://www.buymeacoffee.com/pboling
+[🖇paypal-img]: https://img.shields.io/badge/donate-paypal-a51611.svg?style=flat&logo=paypal
+[🖇paypal]: https://www.paypal.com/paypalme/peterboling
+[✉️discord-invite]: https://discord.gg/3qme4XHNKN
+[✉️discord-invite-img]: https://img.shields.io/discord/1373797679469170758?style=flat
+
+<!-- RELEASE-NOTES-FOOTER-END -->
+
+# 🤑 A request for help
+
+Maintainers have teeth and need to pay their dentists.
+After getting laid off in an RIF in March, and encountering difficulty finding a new one,
+I began spending most of my time building open source tools.
+I'm hoping to be able to pay for my kids' health insurance this month,
+so if you value the work I am doing, I need your support.
+Please consider sponsoring me or the project.
+
+To join the community or get help 👇️ Join the Discord.
+
+[![Live Chat on Discord][✉️discord-invite-img-ftb]][✉️discord-invite]
+
+To say "thanks!" ☝️ Join the Discord or 👇️ send money.
+
+[![Sponsor pboling/appraisal2 on Open Source Collective][🖇osc-all-bottom-img]][🖇osc] 💌 [![Sponsor me on GitHub Sponsors][🖇sponsor-bottom-img]][🖇sponsor] 💌 [![Sponsor me on Liberapay][⛳liberapay-bottom-img]][⛳liberapay] 💌 [![Donate on PayPal][🖇paypal-bottom-img]][🖇paypal]
+
+# Another Way to Support Open Source Software
+
+I’m driven by a passion to foster a thriving open-source community – a space where people can tackle complex problems, no matter how small.  Revitalizing libraries that have fallen into disrepair, and building new libraries focused on solving real-world challenges, are my passions.  I was recently affected by layoffs, and the tech jobs market is unwelcoming. I’m reaching out here because your support would significantly aid my efforts to provide for my family, and my farm (11 🐔 chickens, 2 🐶 dogs, 3 🐰 rabbits, 8 🐈‍ cats).
+
+If you work at a company that uses my work, please encourage them to support me as a corporate sponsor. My work on gems you use might show up in `bundle fund`.
+
+I’m developing a new library, [floss_funding][🖇floss-funding-gem], designed to empower open-source developers like myself to get paid for the work we do, in a sustainable way. Please give it a look.
+
+**[Floss-Funding.dev][🖇floss-funding.dev]: 👉️ No network calls. 👉️ No tracking. 👉️ No oversight. 👉️ Minimal crypto hashing. 💡 Easily disabled nags**
+
+[⛳liberapay-bottom-img]: https://img.shields.io/liberapay/goal/pboling.svg?style=for-the-badge&logo=liberapay&color=a51611
+[🖇osc-all-img]: https://img.shields.io/opencollective/all/
+[🖇osc-sponsors-img]: https://img.shields.io/opencollective/sponsors/
+[🖇osc-backers-img]: https://img.shields.io/opencollective/backers/
+[🖇osc-all-bottom-img]: https://img.shields.io/opencollective/all/?style=for-the-badge
+[🖇osc-sponsors-bottom-img]: https://img.shields.io/opencollective/sponsors/?style=for-the-badge
+[🖇osc-backers-bottom-img]: https://img.shields.io/opencollective/backers/?style=for-the-badge
+[🖇osc]: https://opencollective.com/
+[🖇sponsor-bottom-img]: https://img.shields.io/badge/Sponsor_Me!-pboling-blue?style=for-the-badge&logo=github
+[🖇buyme-img]: https://img.buymeacoffee.com/button-api/?text=Buy%20me%20a%20latte&emoji=&slug=pboling&button_colour=FFDD00&font_colour=000000&font_family=Cookie&outline_colour=000000&coffee_colour=ffffff
+[🖇paypal-bottom-img]: https://img.shields.io/badge/donate-paypal-a51611.svg?style=for-the-badge&logo=paypal&color=0A0A0A
+[🖇floss-funding.dev]: https://floss-funding.dev
+[🖇floss-funding-gem]: https://github.com/galtzo-floss/floss_funding
+[✉️discord-invite-img-ftb]: https://img.shields.io/discord/1373797679469170758?style=for-the-badge

data/LICENSE.md

@@ -0,0 +1,49 @@
+# License
+
+This project is made available under the following license.
+Choose the option that best fits your use case:
+
+- [MIT](MIT.md)
+
+## Copyright Notice
+
+- Copyright (c) 2010 Joe Ferris
+- Copyright (c) 2011 Dan Croak
+- Copyright (c) 2011-2012 Gabe Berke-Williams
+- Copyright (c) 2011 Joe Ferris
+- Copyright (c) 2011 Joseph Anthony Pasquale Holsten
+- Copyright (c) 2011 Nick Quaranto
+- Copyright (c) 2011 Prem Sichanugrist
+- Copyright (c) 2012 Gregory Ostermayr
+- Copyright (c) 2012 osheroff
+- Copyright (c) 2013 Jason Waldrip
+- Copyright (c) 2013 Marc Ignacio
+- Copyright (c) 2013 Phill Baker
+- Copyright (c) 2013-2016 Prem Sichanugrist
+- Copyright (c) 2013 sanemat
+- Copyright (c) 2014 Juan González
+- Copyright (c) 2014-2015 Prem Sichanugrist
+- Copyright (c) 2015 akihiro17
+- Copyright (c) 2015 Elliot Winkler
+- Copyright (c) 2015 M.Shibuya
+- Copyright (c) 2015 Vlad Bokov
+- Copyright (c) 2016 Geoff Massanek
+- Copyright (c) 2016 Ian Fosbery
+- Copyright (c) 2016 Teo Ljungberg
+- Copyright (c) 2017 Brad Gessler
+- Copyright (c) 2017 Oli Peate
+- Copyright (c) 2017, 2025-2026 Peter H. Boling
+- Copyright (c) 2018 Antonis Berkakis
+- Copyright (c) 2018 Jared Beck
+- Copyright (c) 2018, 2020, 2023-2024 Nick Charlton
+- Copyright (c) 2020 Brian Hawley
+- Copyright (c) 2020 David Rodríguez
+- Copyright (c) 2020 James Ebentier
+- Copyright (c) 2021, 2024 Nicolas Rodriguez
+- Copyright (c) 2022 André Arko
+- Copyright (c) 2022 Joe Sharp
+- Copyright (c) 2023 aymeric-ledorze
+- Copyright (c) 2023 Kyle Fazzari
+- Copyright (c) 2024 Joe Sharp
+- Copyright (c) 2024 Sebastian Cohnen
+- Copyright (c) 2024 Yevhenii Ponomarenko