kettle-dev 2.3.5 → 2.3.6

data/CONTRIBUTING.md

@@ -1,275 +0,0 @@
-# Contributing
-
-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, create a patch with tests, and send a pull request.
-
-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 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
-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
-
-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 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 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:generate
-```
-
-Use `bin/rake appraisal:update` when you intentionally need to resolve fresh
-appraisal locks.
-
-If you need to reset all gemfiles/*.gemfile.lock files:
-
-```console
-bin/rake appraisal:reset
-```
-
-When adding an appraisal to CI, check the [runner tool cache][🏃‍♂️runner-tool-cache] to see which runner to use.
-
-## Run Tests
-
-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 kettle-test
-```
-
-For targeted runs, disable the hard coverage threshold to avoid false failures:
-
-```console
-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/kettle/dev/my_class.rb` -> `spec/kettle/dev/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
-
-Run all the default tasks, which includes running the gradually autocorrecting linter, `rubocop-gradual`.
-
-```console
-bundle exec rake
-```
-
-Or just run the linter.
-
-```console
-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!
-
-[![Contributors][🖐contributors-img]][🖐contributors]
-
-Made with [contributors-img][🖐contrib-rocks].
-
-Also see GitLab Contributors: [https://gitlab.com/kettle-dev/kettle-dev/-/graphs/main][🚎contributors-gl]
-
-## For Maintainers
-
-### One-time, Per-maintainer, Setup
-
-**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 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.
-
-### To release a new version:
-
-#### Automated process
-
-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 `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].
-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`
-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
-13. Sanity check the SHA256, comparing with the output from the `bin/gem_checksums` command:
-    - `sha256sum pkg/<gem name>-<version>.gem`
-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-dev/kettle-dev
-[📜src-cb]: https://codeberg.org/kettle-dev/kettle-dev
-[📜src-gh]: https://github.com/kettle-dev/kettle-dev
-[🧪build]: https://github.com/kettle-dev/kettle-dev/actions
-[🤝conduct]: https://github.com/kettle-dev/kettle-dev/blob/main/CODE_OF_CONDUCT.md
-[🖐contrib-rocks]: https://contrib.rocks
-[🖐contributors]: https://github.com/kettle-dev/kettle-dev/graphs/contributors
-[🚎contributors-gl]: https://gitlab.com/kettle-dev/kettle-dev/-/graphs/main
-[🖐contributors-img]: https://contrib.rocks/image?repo=kettle-dev/kettle-dev
-[💎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/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
-[📌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

@@ -1,70 +0,0 @@
-<!-- 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 to my FLOSS efforts at ko-fi.com][🖇kofi-img]][🖇kofi]
-
-[⛳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/kettle-dev#backer
-[🖇osc-backers-i]: https://opencollective.com/kettle-dev/backers/badge.svg?style=flat
-[🖇osc-sponsors]: https://opencollective.com/kettle-dev#sponsor
-[🖇osc-sponsors-i]: https://opencollective.com/kettle-dev/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
-[🖇kofi-img]: https://img.shields.io/badge/ko--fi-%E2%9C%93-a51611.svg?style=flat
-[🖇kofi]: https://ko-fi.com/pboling
-[🖇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 kettle-dev/kettle-dev 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/kettle-dev
-[🖇osc-sponsors-img]: https://img.shields.io/opencollective/sponsors/kettle-dev
-[🖇osc-backers-img]: https://img.shields.io/opencollective/backers/kettle-dev
-[🖇osc-all-bottom-img]: https://img.shields.io/opencollective/all/kettle-dev?style=for-the-badge
-[🖇osc-sponsors-bottom-img]: https://img.shields.io/opencollective/sponsors/kettle-dev?style=for-the-badge
-[🖇osc-backers-bottom-img]: https://img.shields.io/opencollective/backers/kettle-dev?style=for-the-badge
-[🖇osc]: https://opencollective.com/kettle-dev
-[🖇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/RUBOCOP.md

@@ -1,71 +0,0 @@
-# RuboCop Usage Guide
-
-## Overview
-
-A tale of two RuboCop plugin gems.
-
-### RuboCop Gradual
-
-This project uses `rubocop_gradual` instead of vanilla RuboCop for code style checking. The `rubocop_gradual` tool allows for gradual adoption of RuboCop rules by tracking violations in a lock file.
-
-### RuboCop LTS
-
-This project uses `rubocop-lts` to ensure, on a best-effort basis, compatibility with Ruby >= 1.9.2.
-RuboCop rules are meticulously configured by the `rubocop-lts` family of gems to ensure that a project is compatible with a specific version of Ruby. See: https://rubocop-lts.gitlab.io for more.
-
-## Checking RuboCop Violations
-
-To check for RuboCop violations in this project, always use:
-
-```bash
-bundle exec rake rubocop_gradual:check
-```
-
-**Do not use** the standard RuboCop commands like:
-- `bundle exec rubocop`
-- `rubocop`
-
-## Understanding the Lock File
-
-The `.rubocop_gradual.lock` file tracks all current RuboCop violations in the project. This allows the team to:
-
-1. Prevent new violations while gradually fixing existing ones
-2. Track progress on code style improvements
-3. Ensure CI builds don't fail due to pre-existing violations
-
-## Common Commands
-
-- **Check violations**
-    - `bundle exec rake rubocop_gradual`
-    - `bundle exec rake rubocop_gradual:check`
-- **(Safe) Autocorrect violations, and update lockfile if no new violations**
-  - `bundle exec rake rubocop_gradual:autocorrect`
-- **Force update the lock file (w/o autocorrect) to match violations present in code**
-  - `bundle exec rake rubocop_gradual:force_update`
-
-## Workflow
-
-1. Before submitting a PR, run `bundle exec rake rubocop_gradual:autocorrect`
-   a. or just the default `bundle exec rake`, as autocorrection is a pre-requisite of the default task.
-2. If there are new violations, either:
-   - Fix them in your code
-   - Run `bundle exec rake rubocop_gradual:force_update` to update the lock file (only for violations you can't fix immediately)
-3. Commit the updated `.rubocop_gradual.lock` file along with your changes
-
-## Never add inline RuboCop disables
-
-Do not add inline `rubocop:disable` / `rubocop:enable` comments anywhere in the codebase (including specs, except when following the few existing `rubocop:disable` patterns for a rule already being disabled elsewhere in the code). We handle exceptions in two supported ways:
-
-- Permanent/structural exceptions: prefer adjusting the RuboCop configuration (e.g., in `.rubocop.yml`) to exclude a rule for a path or file pattern when it makes sense project-wide.
-- Temporary exceptions while improving code: record the current violations in `.rubocop_gradual.lock` via the gradual workflow:
-  - `bundle exec rake rubocop_gradual:autocorrect` (preferred; will autocorrect what it can and update the lock only if no new violations were introduced)
-  - If needed, `bundle exec rake rubocop_gradual:force_update` (as a last resort when you cannot fix the newly reported violations immediately)
-
-In general, treat the rules as guidance to follow; fix violations rather than ignore them. For example, RSpec conventions in this project expect `described_class` to be used in specs that target a specific class under test.
-
-## Benefits of rubocop_gradual
-
-- Allows incremental adoption of code style rules
-- Prevents CI failures due to pre-existing violations
-- Provides a clear record of code style debt
-- Enables focused efforts on improving code quality over time

data/SECURITY.md

@@ -1,21 +0,0 @@
-# Security Policy
-
-## Supported Versions
-
-| Version  | Supported |
-|----------|-----------|
-| 2.3.latest | ✅         |
-
-## Security contact information
-
-To report a security vulnerability, please use the
-[Tidelift security contact](https://tidelift.com/security).
-Tidelift will coordinate the fix and disclosure.
-
-## Additional Support
-
-If you are interested in support for versions older than the latest release,
-please consider sponsoring the project / maintainer @ https://liberapay.com/pboling/donate,
-or find other sponsorship links in the [README].
-
-[README]: README.md

data/certs/pboling.pem

@@ -1,27 +0,0 @@
------BEGIN CERTIFICATE-----
-MIIEgDCCAuigAwIBAgIBATANBgkqhkiG9w0BAQsFADBDMRUwEwYDVQQDDAxwZXRl
-ci5ib2xpbmcxFTATBgoJkiaJk/IsZAEZFgVnbWFpbDETMBEGCgmSJomT8ixkARkW
-A2NvbTAeFw0yNTA1MDQxNTMzMDlaFw00NTA0MjkxNTMzMDlaMEMxFTATBgNVBAMM
-DHBldGVyLmJvbGluZzEVMBMGCgmSJomT8ixkARkWBWdtYWlsMRMwEQYKCZImiZPy
-LGQBGRYDY29tMIIBojANBgkqhkiG9w0BAQEFAAOCAY8AMIIBigKCAYEAruUoo0WA
-uoNuq6puKWYeRYiZekz/nsDeK5x/0IEirzcCEvaHr3Bmz7rjo1I6On3gGKmiZs61
-LRmQ3oxy77ydmkGTXBjruJB+pQEn7UfLSgQ0xa1/X3kdBZt6RmabFlBxnHkoaGY5
-mZuZ5+Z7walmv6sFD9ajhzj+oIgwWfnEHkXYTR8I6VLN7MRRKGMPoZ/yvOmxb2DN
-coEEHWKO9CvgYpW7asIihl/9GMpKiRkcYPm9dGQzZc6uTwom1COfW0+ZOFrDVBuV
-FMQRPswZcY4Wlq0uEBLPU7hxnCL9nKK6Y9IhdDcz1mY6HZ91WImNslOSI0S8hRpj
-yGOWxQIhBT3fqCBlRIqFQBudrnD9jSNpSGsFvbEijd5ns7Z9ZMehXkXDycpGAUj1
-to/5cuTWWw1JqUWrKJYoifnVhtE1o1DZ+LkPtWxHtz5kjDG/zR3MG0Ula0UOavlD
-qbnbcXPBnwXtTFeZ3C+yrWpE4pGnl3yGkZj9SMTlo9qnTMiPmuWKQDatAgMBAAGj
-fzB9MAkGA1UdEwQCMAAwCwYDVR0PBAQDAgSwMB0GA1UdDgQWBBQE8uWvNbPVNRXZ
-HlgPbc2PCzC4bjAhBgNVHREEGjAYgRZwZXRlci5ib2xpbmdAZ21haWwuY29tMCEG
-A1UdEgQaMBiBFnBldGVyLmJvbGluZ0BnbWFpbC5jb20wDQYJKoZIhvcNAQELBQAD
-ggGBAJbnUwfJQFPkBgH9cL7hoBfRtmWiCvdqdjeTmi04u8zVNCUox0A4gT982DE9
-wmuN12LpdajxZONqbXuzZvc+nb0StFwmFYZG6iDwaf4BPywm2e/Vmq0YG45vZXGR
-L8yMDSK1cQXjmA+ZBKOHKWavxP6Vp7lWvjAhz8RFwqF9GuNIdhv9NpnCAWcMZtpm
-GUPyIWw/Cw/2wZp74QzZj6Npx+LdXoLTF1HMSJXZ7/pkxLCsB8m4EFVdb/IrW/0k
-kNSfjtAfBHO8nLGuqQZVH9IBD1i9K6aSs7pT6TW8itXUIlkIUI2tg5YzW6OFfPzq
-QekSkX3lZfY+HTSp/o+YvKkqWLUV7PQ7xh1ZYDtocpaHwgxe/j3bBqHE+CUPH2vA
-0V/FwdTRWcwsjVoOJTrYcff8pBZ8r2MvtAc54xfnnhGFzeRHfcltobgFxkAXdE6p
-DVjBtqT23eugOqQ73umLcYDZkc36vnqGxUBSsXrzY9pzV5gGr2I8YUxMqf6ATrZt
-L9nRqA==
------END CERTIFICATE-----

data/sig/kettle/dev/appraisals_ast_merger.rbs

@@ -1,72 +0,0 @@
-# TypeProf 0.21.11
-
-module Kettle
-  module Dev
-    # AST-driven merger for Appraisals files using Prism
-    module AppraisalsAstMerger
-      TRACKED_METHODS: Array[Symbol]
-
-      # Merge template and destination Appraisals files preserving comments
-      def self.merge: (String template_content, String dest_content) -> String
-
-      # Extract blocks and preamble from parse result
-      def self.extract_blocks: (
-        Prism::ParseResult parse_result,
-        String source_content
-      ) -> [Array[Prism::Comment], Array[Hash[Symbol, untyped]]]
-
-      # Check if node is an appraise call
-      def self.appraise_call?: (Prism::Node node) -> bool
-
-      # Extract appraise block name from node
-      def self.extract_appraise_name: (Prism::Node? node) -> String?
-
-      # Merge preamble comments from template and destination
-      def self.merge_preambles: (
-        Array[Prism::Comment] tmpl_comments,
-        Array[Prism::Comment] dest_comments
-      ) -> Array[String]
-
-      # Extract block header comments
-      def self.extract_block_header: (
-        Prism::Node node,
-        Array[String] source_lines,
-        Array[Hash[Symbol, untyped]] previous_blocks
-      ) -> String
-
-      # Merge blocks from template and destination
-      def self.merge_blocks: (
-        Array[Hash[Symbol, untyped]] tmpl_blocks,
-        Array[Hash[Symbol, untyped]] dest_blocks,
-        Prism::ParseResult tmpl_result,
-        Prism::ParseResult dest_result
-      ) -> Array[Hash[Symbol, untyped]]
-
-      # Merge statements within a block
-      def self.merge_block_statements: (
-        Prism::Node? tmpl_body,
-        Prism::Node? dest_body,
-        Prism::ParseResult dest_result
-      ) -> Array[Hash[Symbol, untyped]]
-
-      # Generate statement key for deduplication
-      def self.statement_key: (Prism::Node node) -> [Symbol, String?]?
-
-      # Build output from preamble and blocks
-      def self.build_output: (
-        Array[String] preamble_lines,
-        Array[Hash[Symbol, untyped]] blocks
-      ) -> String
-
-      # Normalize statement to use parentheses
-      def self.normalize_statement: (Prism::Node node) -> String
-
-      # Normalize argument to canonical format
-      def self.normalize_argument: (Prism::Node arg) -> String
-
-      # Extract original statements from node
-      def self.extract_original_statements: (Prism::Node node) -> Array[Hash[Symbol, untyped]]
-    end
-  end
-end
-

data/sig/kettle/dev/changelog_cli.rbs

@@ -1,69 +0,0 @@
-# TypeProf 0.21.11
-
-module Kettle
-  module Dev
-    # CLI for updating CHANGELOG.md with new version sections
-    class ChangelogCLI
-      UNRELEASED_SECTION_HEADING: String
-
-      @root: String
-      @changelog_path: String
-      @coverage_path: String
-
-      def initialize: (?strict: bool, ?enforce_coverage_thresholds: bool, ?update_prep: bool, ?root: String) -> void
-
-      # Main entry point that updates CHANGELOG.md
-      def run: () -> void
-
-      def pending_release_status: () -> Hash[Symbol, untyped]
-
-      def release_state: () -> Hash[Symbol, untyped]
-
-      def release_state_table: (?Hash[Symbol, untyped] state) -> String
-
-      private
-
-      # Abort with error message
-      def abort: (String msg) -> void
-
-      # Detect version from lib/**/version.rb
-      def detect_version: () -> String
-
-      # Extract unreleased section from changelog
-      def extract_unreleased: (String content) -> [String?, String?, String?]
-
-      # Detect previous version from after text
-      def detect_previous_version: (String after_text) -> String?
-
-      # Filter unreleased sections keeping only those with content
-      def filter_unreleased_sections: (String unreleased_block) -> String
-
-      # Get coverage lines from coverage.json
-      def coverage_lines: () -> [String?, String?]
-
-      # Get YARD documentation percentage
-      def yard_percent_documented: () -> String?
-
-      # Convert legacy heading tag suffix to list format
-      def convert_heading_tag_suffix_to_list: (String text) -> String
-
-      # Update link references in changelog
-      def update_link_refs: (
-        String content,
-        String? owner,
-        String? repo,
-        String? prev_version,
-        String new_version
-      ) -> String
-
-      # Normalize spacing around headings
-      def normalize_heading_spacing: (String text) -> String
-
-      # Ensure proper footer spacing
-      def ensure_footer_spacing: (String text) -> String
-
-      # Detect initial compare base from changelog
-      def detect_initial_compare_base: (Array[String] lines) -> String
-    end
-  end
-end

data/sig/kettle/dev/ci_helpers.rbs

@@ -1,42 +0,0 @@
-module Kettle
-  module Dev
-    module CIHelpers
-      # singleton (module) methods
-      def self.project_root: () -> String
-      def self.repo_info: () -> [String, String]?
-      def self.current_branch: () -> String?
-      def self.current_head_sha: () -> String?
-      def self.workflows_list: (?String root) -> Array[String]
-      def self.exclusions: () -> Array[String]
-
-      def self.latest_run: (
-        owner: String,
-        repo: String,
-        workflow_file: String,
-        ?branch: String?,
-        ?token: String?,
-        ?require_head: bool,
-        ?head_sha: String?
-      ) -> { "status" => String, "conclusion" => String?, "html_url" => String, "id" => Integer, "head_sha" => String? }?
-
-      def self.success?: ({ "status" => String, "conclusion" => String? }?) -> bool
-      def self.failed?: ({ "status" => String, "conclusion" => String? }?) -> bool
-
-      def self.default_token: () -> String?
-
-      # GitLab
-      def self.origin_url: () -> String?
-      def self.repo_info_gitlab: () -> [String, String]?
-      def self.default_gitlab_token: () -> String?
-      def self.gitlab_latest_pipeline: (
-        owner: String,
-        repo: String,
-        ?branch: String?,
-        ?host: String,
-        ?token: String?
-      ) -> { "status" => String, "web_url" => String, "id" => Integer, "failure_reason" => String? }?
-      def self.gitlab_success?: ({ "status" => String }?) -> bool
-      def self.gitlab_failed?: ({ "status" => String }?) -> bool
-    end
-  end
-end

data/sig/kettle/dev/ci_monitor.rbs

@@ -1,17 +0,0 @@
-module Kettle
-  module Dev
-    module CIMonitor
-      def self.status_emoji: (String? status, String? conclusion) -> String
-      def self.monitor_all!: (?restart_hint: String) -> void
-      def self.monitor_gitlab!: (?restart_hint: String) -> bool
-      def self.collect_all: () -> { github: Array[untyped], gitlab: untyped? }
-      def self.summarize_results: ({ github: Array[untyped], gitlab: untyped? }) -> bool
-      def self.monitor_and_prompt_for_release!: (?restart_hint: String) -> void
-      def self.collect_github: () -> Array[untyped]?
-      def self.collect_gitlab: () -> { status: String, url: String? }?
-      def self.monotonic_time: () -> Float
-      def self.github_start_timeout: () -> Integer
-      def self.github_poll_interval: () -> Float
-    end
-  end
-end