henitai 0.5.1 → 0.5.3

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 321426b14e3d03dae68885665b6abee8e11ea48d7a00036664dd0b6a10af2659
-  data.tar.gz: 262e708c7393a11e57f8fe25b9588b8b6aa04c026bebef1dec0aa77fedd782ba
+  metadata.gz: 0530ecd98105a394b4466cbe23704f848565c55e318c35a31e096eedc2cba299
+  data.tar.gz: 56c64c5b679b0bc7c66691a4a7b20c274ac90d1d812d7abb65e778190cd6bb39
 SHA512:
-  metadata.gz: 4ef8ed1d823903bceca334c81a895a1734745480e0966ab55e100ea95b8479201824ebbd048ea86f0465c0a98fd39dd561a62876614e20bed7b1f64460d10e20
-  data.tar.gz: b152279d4854b7aeb55afb5696a77054184947f0ea16570dd9e3f90a62388295b6f4f6499f101d323a8fa0071c9d83d8847e3348c878061c980587ab6ddfd53f
+  metadata.gz: e8725233ea8c806ca65fc488560daafbfc2300f723a054039b29dd45625a935217ebdbe609fde3e2df693299ee5ca069d35ce00b63a4e9a4d90dcfa9e77e2920
+  data.tar.gz: d8052c091f3967d1cc873cb34b02f04ad339714f08950841f65e7ef1ff064573bb0f54226eb3725d29dd3e7a42727d535b469396c76aa0a0ae2ffb5ae1075336

data/CHANGELOG.md

@@ -7,9 +7,42 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 ## [Unreleased]
 
+## [0.5.3] - 2026-08-26
+
+### Fixed
+
+- A timed-out Minitest baseline suite is now actually killed. Its child was
+  spawned without `pgroup: true`, so the parent's group-wide `SIGTERM` named a
+  process group that never existed, raised `ESRCH`, and left the suite running;
+  the parent then blocked in `Process.wait` until the suite finished on its own
+  — minutes past the timeout it had already reported, and long after the log
+  tail quoted in the error had stopped describing reality. The suite child now
+  leads its own group, as the RSpec baseline child already did, and post-run
+  cleanup signals that group instead of the single pid, so a Rails test server
+  or browser driver started by the suite is torn down with it.
+
+## [0.5.2] - 2026-08-26
+
+### Changed
+
+- `test_excludes` now also applies to the coverage-bootstrap suite, not only to
+  per-mutant test selection. Slow end-to-end or integration suites could be kept
+  away from mutant children but still had to run in full during the baseline,
+  where the fixed suite timeout aborts the run with
+  `Henitai::CoverageError: Configured test suite failed while generating
+  coverage` even though the suite itself was green. Excluded files are also
+  dropped from the coverage freshness watch list, so a test that no longer
+  contributes to the baseline no longer invalidates it. Lines covered only by
+  excluded tests now count as uncovered and are not mutated — matching what
+  already happened at execution time, where such mutants could never be killed.
+  A `test_excludes` set that leaves no test file now aborts with
+  `Henitai::ConfigurationError` instead of running an empty suite and then
+  reporting missing coverage.
+
 ## [0.5.1] - 2026-08-25
 
 ### Changed
+
 - `minitest` runtime dependency widened from `~> 5.25` to `>= 5.25, < 7`.
   The floor is unchanged; only the ceiling moved. `~> 5.25` capped the
   range below 6.0, so bundles resolving minitest 6.x could not install
@@ -20,6 +53,7 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 ## [0.5.0] - 2026-08-21
 
 ### Security
+
 - `sqlite3` requirement raised from `~> 1.7` to `>= 2.9.5, < 3`, excluding the
   vulnerable releases up to and including 2.9.4. This is a runtime major bump:
   applications pinned to `sqlite3` 1.x will need to upgrade before installing
@@ -28,6 +62,7 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
   floors so a regression fails the suite rather than shipping quietly
 
 ### Changed
+
 - `coverage_criteria` now actually affects scoring. The block was documented,
   defaulted and validated since it was introduced, but nothing ever read it —
   `Result` hardcoded the `MS` numerator as `killed + timeout + runtime_error`,
@@ -50,6 +85,7 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
   4.0-only form), and CI runs the floor alongside 4.0.2
 
 ### Fixed
+
 - Forked mutant children no longer outlive a parent that dies without warning.
   Children run in their own process group, and all parent-side cleanup —
   timeout kills, graceful drain, signal traps — only runs while the parent's
@@ -84,6 +120,7 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
   0.3.1; this restores it
 
 ### Internal
+
 - Test-suite coupling to private implementation details is now guarded by
   `spec/infra/private_method_reach_spec.rb`, a ratchet: every spec that reaches
   a private method through `send` or an instance-variable poke carries a
@@ -104,6 +141,7 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 ## [0.4.0] - 2026-07-14
 
 ### Added
+
 - `hard` operator set (`mutation.operators: hard` / `--operators hard`), a
   strict superset of `full` for usually-unkillable mutations (ADR-12):
   currently `EqualityIdentityOperator` and the new `HashKeyType`
@@ -113,6 +151,7 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
   single-pair hashes and double-splat entries are skipped
 
 ### Changed
+
 - `full` now means "usually killable": the symbol-key -> string-key mutation
   moved from `HashLiteral` into the new hard-set `HashKeyType`, and
   `EqualityIdentityOperator` moved from `full` to `hard` — `full` runs emit
@@ -121,6 +160,7 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 ## [0.3.1] - 2026-07-13
 
 ### Fixed
+
 - Per-mutant log capture no longer crashes with
   `Encoding::UndefinedConversionError` when the host app sets
   `Encoding.default_internal` (as Rails test environments do) and a child
@@ -130,6 +170,7 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
   from corrupting the file.
 
 ### Changed
+
 - `--since REF` now includes the working tree: tracked files with
   uncommitted changes and untracked files count as changed, matching what
   actually gets tested. Previously only committed changes in `REF..HEAD`
@@ -146,6 +187,7 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 ## [0.3.0] - 2026-07-13
 
 ### Added
+
 - `henitai run --incremental`: verdict reuse from the history store. Killed
   verdicts are reused when the subject's source and every covering test file
   are byte-identical to what was recorded; Survived verdicts are additionally
@@ -181,6 +223,7 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
   moved out of the default light set into its own operator (ADR-10)
 
 ### Fixed
+
 - Mutants in `module_function` modules were unkillable: `module_function`
   copies the method onto the module's singleton and activation only replaced
   the instance side, so callers kept running original code and every such
@@ -200,6 +243,7 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 - Flaky-retry counter no longer inflates when a respawned child fails again
 
 ### Changed
+
 - Terminal reporter renders original nodes from their source slice and reuses
   a memoized unparse of the mutated node shared with the JSON reporter
   (a dogfood profile spent 27% of wall time re-unparsing survivors)
@@ -213,6 +257,7 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
   redefinition warnings into their logs
 
 ### Internal
+
 - Architecture documentation gained §8.11 (incremental verdict reuse) and
   ADR-11 (content-fingerprint verdict reuse, not git scoping); new backlog
   tickets for CI warm verdict cache, child null formatter, and auto-`--since`
@@ -224,12 +269,14 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 ## [0.2.1] - 2026-06-25
 
 ### Fixed
+
 - `henitai run` now exits 0 when a run evaluates no valid mutants, instead of
   failing a CI gate on a vacuous result
 - Flaky-retry counts are now recorded on the parallel execution path (they were
   always reported as 0 regardless of actual retries)
 
 ### Changed
+
 - `Result` and `Reporter::Json` take their IO as an injected dependency,
   restoring the domain/infrastructure boundary (no public API change)
 - Decomposed the monolithic `integration.rb` into single-responsibility files
@@ -238,6 +285,7 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 - Narrowed broad rescues in `safe_unparse` and per-test coverage snapshotting
 
 ### Internal
+
 - De-mocked runner specs, added `process_wakeup` and helper coverage, and
   removed sleep- and chdir-based flakiness from the suite
 - Enabled full-operator dogfooding configuration and isolated the
@@ -247,6 +295,7 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 ## [0.2.0] - 2026-04-30
 
 ### Added
+
 - `--survivors-from <path>` flag on `henitai run` for survivor-only reruns:
   re-execute only the mutants that survived a prior full run without re-running
   the whole suite
@@ -281,6 +330,7 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 - x86_64 platform added to gem platform list
 
 ### Changed
+
 - JSON mutation report vendor extension now always includes `sessionId`
   (and `gitSha` when available) to support survivor-only reruns
 - Terminal reporter labels partial reruns as "Partial survivor rerun" and
@@ -295,6 +345,7 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
   `max_flaky_retries: 3` added
 
 ### Fixed
+
 - Minitest autorun hook suppressed in mutation child processes to prevent
   spurious re-runs of the full suite inside each fork
 - Coverage bootstrap RSpec subprocess ARGV leakage resolved — child processes
@@ -307,6 +358,7 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
   preventing stale cache hits after edits
 
 ### Performance
+
 - File discovery cached in the integration layer; repeated calls within one
   run no longer re-scan the filesystem
 - Polling sleep removed from the scheduler hot loop; slots are refilled
@@ -315,6 +367,7 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 ## [0.1.10] - 2026-04-16
 
 ### Fixed
+
 - RuboCop `RSpec/MultipleExpectations` offenses in `coverage_formatter_spec` and
   `per_test_coverage_collector_spec` resolved by splitting each two-assertion
   example into focused single-expectation examples
@@ -322,6 +375,7 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 ## [0.1.9] - 2026-04-16
 
 ### Fixed
+
 - SimpleCov is now suppressed during Minitest mutant child runs: `SimpleCov.start`
   is turned into a no-op before test files are required, eliminating the
   "Stopped processing SimpleCov as a previous error has been detected" warning
@@ -330,12 +384,14 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 ## [0.1.8] - 2026-04-16
 
 ### Added
+
 - Minitest integration now supports per-test coverage: a `MinitestCoverageReporter`
   snapshots `Coverage.peek_result` after each test and writes `henitai_per_test.json`,
   enabling targeted mutation runs that only execute the tests covering the mutated lines —
   the same efficiency that was previously available only to RSpec projects
 
 ### Fixed
+
 - RSpec integration now respects `--exclude-pattern` entries in `.rspec` so excluded
   spec files are not passed to the runner during mutation runs
 - Per-test source file filter corrected to check only the project-relative path prefix
@@ -345,11 +401,13 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 ## [0.1.7] - 2026-04-14
 
 ### Added
+
 - Committed integration smoke projects for RSpec and Minitest, runnable via
   `bundle exec rake smoke:integration:all`, to exercise `henitai` against
   small real projects that depend on the local source checkout
 
 ### Fixed
+
 - Child-process stdout/stderr restoration after captured test runs now keeps
   the standard streams usable, preventing passing mutant executions from being
   misclassified because the child exited with a closed stdio handle
@@ -360,6 +418,7 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 ## [0.1.6] - 2026-04-14
 
 ### Fixed
+
 - Minitest is no longer required eagerly when `henitai/integration` loads, so
   projects that do not include Minitest in their bundle can still boot and use
   non-Minitest integrations without a parent-process `LoadError`
@@ -367,6 +426,7 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 ## [0.1.5] - 2026-04-14
 
 ### Fixed
+
 - Steep type errors in `Runner` after removing targeted-run bootstrap scoping:
   updated `bootstrap_mutants` RBS signature to match the new single-argument
   form and removed stale signatures for `refresh_coverage_for_targeted_run`,
@@ -375,6 +435,7 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
   workspace setup and report writing into helper methods
 
 ### Changed
+
 - Targeted-run coverage bootstrap no longer scopes the initial run to the
   subject's test files; the full suite is always used for the baseline,
   trading a minor performance optimisation for reliability
@@ -382,6 +443,7 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 ## [0.1.4] - 2026-04-14
 
 ### Fixed
+
 - `StringLiteral` operator no longer generates no-op mutations where the
   replacement equals the original value (e.g. the spurious `"" → ""` mutant
   that was emitted for methods already returning an empty string literal)
@@ -397,6 +459,7 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
   runner's configured reports directory
 
 ### Changed
+
 - `ScenarioExecutionResult.build` factory method consolidates status and
   exit-status derivation that was previously spread across `Integration`,
   reducing the mutation surface of the value object
@@ -404,6 +467,7 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 ## [0.1.3] - 2026-04-13
 
 ### Added
+
 - Four new mutation operators: `UnaryOperator` (negates boolean and numeric
   unary expressions), `UpdateOperator` (swaps `+=`/`-=`/`*=` and targets
   compound-assignment nodes), `RegexMutator` (replaces regex literals with
@@ -422,6 +486,7 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
   `x || false`, `true && x`, `x && true` are suppressed as equivalent mutants
 
 ### Changed
+
 - Per-line mutation cap (`max_mutants_per_line`) removed from the generator,
   configuration schema, and validator — see ADR-08. All syntactically valid
   mutations on a line are now generated unconditionally
@@ -436,6 +501,7 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
   without reflection
 
 ### Performance
+
 - Coverage bootstrap freshness check: the baseline RSpec run is skipped when
   `.resultset.json` is newer than every watched source and test file,
   eliminating ~83 % of bootstrap wall time on repeated runs within a session
@@ -457,6 +523,7 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
   AST node
 
 ### Fixed
+
 - Mutant child processes now run in isolated process groups (`setpgid`);
   `cleanup_process_group` sends `SIGTERM` to the entire group on timeout or
   error, preventing orphaned subprocesses
@@ -472,10 +539,12 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 ## [0.1.2] - 2026-04-07
 
 ### Added
+
 - Method coverage is now enabled in both RSpec and Minitest bootstraps, and
   the static filter merges method-level coverage into the line map
 
 ### Fixed
+
 - Coverage baseline regeneration now happens on every `henitai run`, so stale
   coverage state does not leak between runs
 - Coverage handling now accepts symbol-keyed `Coverage.peek_result` output and
@@ -492,6 +561,7 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 ## [0.1.1] - 2026-04-03
 
 ### Added
+
 - Minitest integration for Rails projects: injects SimpleCov for coverage
   collection, sets `RAILS_ENV=test` and `PARALLEL_WORKERS=1` in the baseline
   subprocess, preloads `config/environment.rb` before mutant activation, adds
@@ -499,6 +569,7 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 - `simplecov` runtime dependency (required by the Minitest integration)
 
 ### Fixed
+
 - `rspec/core` was unconditionally required at load time, causing a `LoadError`
   in projects that do not have RSpec installed — now loaded lazily only when the
   RSpec integration is used
@@ -508,6 +579,7 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 ## [0.1.0] - 2026-03-01
 
 ### Added
+
 - Initial gem scaffold with Ruby 4.0.2 support
 - Dev Container configuration (official `ruby:4.0.2-alpine` base image, Codex CLI preinstalled)
 - CI pipeline (RuboCop + RSpec + incremental mutation testing on PRs)
@@ -516,7 +588,9 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 - CLI critical path: `henitai run` now executes the full pipeline, supports `--since`, returns CI-friendly exit codes, and `henitai version` prints `Henitai::VERSION`
 - RSpec per-test coverage output: `henitai/coverage_formatter` now writes `coverage/henitai_per_test.json`
 
-[Unreleased]: https://github.com/martinotten/henitai/compare/v0.5.1...HEAD
+[Unreleased]: https://github.com/martinotten/henitai/compare/v0.5.3...HEAD
+[0.5.3]: https://github.com/martinotten/henitai/compare/v0.5.2...v0.5.3
+[0.5.2]: https://github.com/martinotten/henitai/compare/v0.5.1...v0.5.2
 [0.5.1]: https://github.com/martinotten/henitai/compare/v0.5.0...v0.5.1
 [0.5.0]: https://github.com/martinotten/henitai/compare/v0.4.0...v0.5.0
 [0.4.0]: https://github.com/martinotten/henitai/compare/v0.3.1...v0.4.0

data/README.md

@@ -77,7 +77,7 @@ excludes:
   - lib/henitai/eager_load.rb   # standalone entry points with no in-process coverage
 
 test_excludes:
-  - spec/end_to_end/*_spec.rb   # never select these files for individual mutants
+  - spec/end_to_end/*_spec.rb   # never run these files, mutants or coverage baseline
 
 mutation:
   operators: light   # light | full
@@ -109,8 +109,14 @@ when a value is invalid.
 
 CLI flags override the corresponding values from `.henitai.yml`.
 
-`test_excludes` removes matching test files from per-mutant selection. A mutant
-with no tests left is reported as `NoCoverage` and is not executed.
+`test_excludes` removes matching test files from per-mutant selection *and* from
+the coverage-bootstrap suite. A mutant with no tests left is reported as
+`NoCoverage` and is not executed. Excluding slow end-to-end or integration
+suites therefore also keeps them out of the baseline run — which matters,
+because a test that never runs against a mutant can never kill one, and the
+baseline suite has a fixed timeout. Lines covered only by excluded tests count
+as uncovered and are not mutated. Excluding every test file aborts with
+`Henitai::ConfigurationError`.
 `mutation.max_log_bytes` is a positive per-stream byte cap for captured child
 output. `mutation.max_timeout` caps auto-calibrated timeouts; an explicit
 `mutation.timeout` still takes precedence. When JSON or HTML reporting is

data/lib/henitai/coverage_bootstrapper.rb

@@ -32,11 +32,13 @@ module Henitai
     # @param config       [Configuration]
     # @param integration  [Integration::Base]
     # @param test_files   [Array<String>, nil] test files to run; defaults to
-    #                     all files reported by the integration when nil
+    #                     all files reported by the integration when nil.
+    #                     Either way, `config.test_excludes` matches are dropped.
+    # @raise [ConfigurationError] when the excludes leave no test file to run
     def ensure!(source_files:, config:, integration:, test_files: nil)
       return if source_files.empty?
 
-      resolved_test_files = resolve_test_files(integration, test_files)
+      resolved_test_files = resolve_test_files(integration, test_files, config)
 
       # Skip the bootstrap only when the coverage artifacts are both newer than
       # all watched files and actually cover the configured sources. A fresh
@@ -225,10 +227,24 @@ module Henitai
       Array(source_files) + Array(test_files) + VerdictFingerprint.dependency_files
     end
 
-    def resolve_test_files(integration, test_files)
-      return test_files unless test_files.nil?
+    # Excluded tests are dropped here rather than in `bootstrap_coverage`, so
+    # the same filtered list feeds both the suite run and the freshness watch
+    # list: a test that no longer contributes to the baseline must not
+    # invalidate it either.
+    def resolve_test_files(integration, test_files, config)
+      candidates = test_files.nil? ? integration.test_files : test_files
+      patterns = configured_test_excludes(config)
+      retained = ExcludedTestFilter.new(patterns:).reject(candidates)
+      return retained unless retained.empty? && candidates.any?
+
+      raise ConfigurationError,
+            "test_excludes #{Array(patterns).inspect} excludes every test file; " \
+            "coverage cannot be generated"
+    end
 
-      integration.test_files
+    # Specs pass bare config doubles exposing only what the example needs.
+    def configured_test_excludes(config)
+      config.respond_to?(:test_excludes) ? config.test_excludes : nil
     end
 
     def reports_dir(config)

data/lib/henitai/integration/minitest.rb

@@ -71,6 +71,11 @@ module Henitai
         env
       end
 
+      # `pgroup: true` makes the suite child a group leader, so the whole tree
+      # it spawns -- a Rails test server, browser drivers -- is signalable as
+      # one group. Without it the parent's `kill(:SIGTERM, -pid)` addresses a
+      # group that does not exist, raises ESRCH, and leaves a timed-out suite
+      # running to completion while the parent has already given up on it.
       def spawn_suite_process(test_files, log_paths)
         FileUtils.mkdir_p(File.dirname(log_paths[:stdout_path]))
         File.open(log_paths[:stdout_path], "w") do |stdout_file|
@@ -79,16 +84,19 @@ module Henitai
               subprocess_env,
               *suite_command(test_files),
               out: stdout_file,
-              err: stderr_file
+              err: stderr_file,
+              pgroup: true
             )
           end
         end
       end
 
+      # A timeout has already torn the group down and reaped the child in
+      # `handle_timeout`; signalling again would only race a recycled pid.
       def cleanup_suite_process(pid, wait_result)
         return unless pid
 
-        cleanup_child_process(pid)
+        cleanup_process_group(pid) unless wait_result == :timeout
         reap_child(pid) if wait_result.nil?
       end
 

data/lib/henitai/version.rb

@@ -1,5 +1,5 @@
 # frozen_string_literal: true
 
 module Henitai
-  VERSION = "0.5.1"
+  VERSION = "0.5.3"
 end

data/sig/henitai.rbs

@@ -1211,6 +1211,8 @@ module Henitai
     def coverage_fresh?: (Array[String], Configuration, Integration::Base, Array[String]?) -> bool
     def coverage_report_path: (Configuration) -> String
     def bootstrap_coverage: (Integration::Base, Configuration, ?Array[String]?) -> void
+    def resolve_test_files: (Integration::Base, Array[String]?, Configuration) -> Array[String]
+    def configured_test_excludes: (Configuration) -> Array[String]?
     def source_file_paths: (Array[String]) -> Array[String]
   end
 

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: henitai
 version: !ruby/object:Gem::Version
-  version: 0.5.1
+  version: 0.5.3
 platform: ruby
 authors:
 - Martin Otten
@@ -252,7 +252,7 @@ metadata:
   changelog_uri: https://github.com/martinotten/henitai/blob/main/CHANGELOG.md
   documentation_uri: https://github.com/martinotten/henitai/blob/main/README.md
   homepage_uri: https://github.com/martinotten/henitai
-  source_code_uri: https://github.com/martinotten/henitai/tree/v0.5.1
+  source_code_uri: https://github.com/martinotten/henitai/tree/v0.5.3
   rubygems_mfa_required: 'true'
 rdoc_options: []
 require_paths: