branchproof 0.11.0 → 0.12.0

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 3667120528803b1ceeb8c17313f66391b38633ed452757cb6e532f938d8cfd2a
-  data.tar.gz: ebdab6b41dde4697eff2634fe022c18e7c86e7abf4a317235fc94f24ec6070ad
+  metadata.gz: ac60ef7d1ba183067cb1290e2ca5a50a455733e38cd1d8eb8e31892a74b2b029
+  data.tar.gz: 03ff3d45dd008156103ca81a5834f7d2479ccee7ae37655b5b7a6a71dc3423e6
 SHA512:
-  metadata.gz: 226da6639e0f9aedc3345073e76b8bd78c23921ea0c5664d4230cf1712d25984a8b97168b2d721658e50c552dab54e6ad5cac71ae8bfccf5222c4eb89cf8471e
-  data.tar.gz: 7ff352e0d1ec9aca08a67d0ed9c6246a37f1560f16777a0c89b01ad04ad94fff7af99a2abb3b09135990f1d67b33e58cff3ce4209e0e0a5a808f72ff59a52c07
+  metadata.gz: 0e3bcc13ff1030451abf7fdc30d16eb36eb77a57d8b74fa13929365551c2749ee66b6bde3c84588c43404b1f665fd23067a93110e6bfc33bec8879b7401786c8
+  data.tar.gz: 60eb5d087463069447453422459e03d02eb2b7c332cb649d77159227b8f359375dd3bac4c74fa8f508f0a896fb8fd82415ffbd13d29a20c40fa43ce575511463

data/CHANGELOG.md

@@ -1,5 +1,94 @@
 ## [Unreleased]
 
+## [0.12.0] - 2026-10-05
+
+- Fix compilation of instrumented rescue bodies with early returns when Ruby
+  branch coverage is enabled, preserving return values, exception handling,
+  and `ensure` behavior.
+- Combine compatible serial reports with `branchproof collate`, recomputing
+  coverage and gates from merged observations. An optional expected-shard
+  manifest distinguishes complete collections from missing or unknown inputs;
+  incomplete collections cannot pass. Schema `1.7` retains shard provenance,
+  while existing analyze schemas remain unchanged. Terminal, GitHub, and HTML
+  output disclose collection status. No application boot or test run is needed.
+- Support serial plain Ruby applications using Minitest 6 while retaining
+  Minitest 5.25.5 and later. Doctor accepts the same `>= 5.25.5, < 7` range.
+  Recognize Minitest 6 parallel scheduling and reject bisect/server execution
+  before test bodies run. Frameworks remain application-supplied dependencies.
+- Add independent changed-decision gates with `--minimum-changed`, paired with
+  `analyze --changed-since` or a saved report's captured scope. Terminal, GitHub,
+  and HTML show changed-policy results; JSON schema `1.6` records and validates
+  them. Valid empty scopes are explicitly not applicable, and incomplete or
+  unavailable evidence cannot pass a changed gate.
+- Explain missing MC/DC evidence using captured expressions, an observed vector,
+  and a suggested counterpart. Shared report wording distinguishes hypothetical
+  candidates from observations and preserves short-circuit information.
+- Add `branchproof doctor` for static setup checks of the Ruby runtime, selected
+  test framework metadata, project configuration, and source/test file selection.
+  The command reports terminal or JSON results without loading project code or
+  running tests; it exits 2 when setup is blocked. See the README for its
+  readiness limits and JSON shape.
+- Make Minitest and RSpec application-supplied optional dependencies. Branchproof
+  now needs only Prism at runtime; saved reports can be rendered and compared
+  without either test framework installed.
+- Render saved reports as self-contained offline HTML with `branchproof report
+  snapshot.json --format html`. HTML preserves whole-run policy and exit status,
+  supports display filters, and can be uploaded as a CI artifact without rerunning
+  tests; HTML is unavailable for live analysis and comparison.
+- Add `analyze --changed-since REF` for informational coverage of current
+  decisions affected by tracked staged and unstaged worktree changes. Tests,
+  whole-run coverage, and minimum gates retain their existing scope; captured
+  changed-scope reports use JSON schema `1.5` and remain available offline.
+- Speed up level-3 supporting-set minimization by avoiding repeated Set
+  differences in greedy selection. Large synthetic RSpec and Minitest runs
+  take 70–77% less end-to-end time on Ruby 4.0.1; selected sets, search
+  budgets, report fields, and exit statuses are preserved. See the
+  [performance record](https://github.com/lucianghinda/branchproof/blob/main/docs/benchmarks/supporting-set-performance-2026-10-02.md)
+  for measurements and allocation/memory limits.
+
+- Require Ruby 4.0 or newer and run core, RSpec, and Rails CI on Ruby 4.0.
+- `branchproof mutate` now exits with status 2 and says that mutation testing
+  is not supported yet, instead of the generic unknown-command error.
+- Add RBS signatures for `Branchproof::Worker`.
+- Add `--view summary` for `analyze` and `report`. It ranks source files and
+  decisions with gaps: unexecuted decisions first, then the most missing
+  decision-table rules, unproven MC/DC conditions, and missing alternatives.
+  Each row shows its location, counts with denominators, the cases to test
+  (level 2+), and the tests that already reach the decision (level 3).
+  `--top`, `--focus`, and `--missing-only` apply; global summaries, gates,
+  and exit status are unchanged.
+- Add `--format github` for `analyze` and `report`. It prints GitHub Actions
+  annotations in summary-view order, errors for failed or incomplete runs
+  and unmet policy gates, and a final coverage notice. Annotation paths are
+  made repository-relative with `GITHUB_WORKSPACE`. When `GITHUB_STEP_SUMMARY` is set, it
+  also appends a Markdown job summary with the ladder, gates, and ranked gaps.
+- Add `Branchproof::RakeTask`. `require "branchproof/rake_task"` defines a
+  Rake task that runs `branchproof analyze` in a subprocess with the options
+  set in the Rakefile. Unset options keep the CLI and `.branchproof.json`
+  defaults, and a non-zero CLI exit status fails the Rake process with the
+  same status.
+
+- Report value-context `||` chains that end in a string, symbol, or numeric
+  literal (including interpolated strings and symbols), such as
+  `name.presence || entry&.title || "Item #{id}"`, as `fallback` alternatives:
+  each operand is an alternative, covered when a test makes it the one that
+  supplies the value. These chains are no longer Boolean `short_circuit`
+  decisions, so they leave the MC/DC and decision-table denominators. Chains
+  used as conditions (`if`, `unless`, `while`, `until`, ternary, and
+  `case`/`when`), chains that end in `true`, `false`, or `nil`, keyword `or`,
+  and chains whose operands contain `&&`, `||`, `!`, or a jump (`return`,
+  `break`, `next`, `redo`, `retry`) keep Boolean treatment.
+- Decision IDs for these expressions change because their context changes.
+  Comparisons against reports made with earlier versions show them as removed
+  `short_circuit` decisions and new `fallback` decisions.
+
+## [0.11.1] - 2026-09-28
+
+- Treat string, interpolated string, symbol, and numeric literal conditions as
+  always truthy. Rules that need such a literal to be falsey, as in
+  `name || "Item #{id}"`, are now excluded as statically impossible instead of
+  being reported as missing with unknown reachability.
+
 ## [0.11.0] - 2026-09-25
 
 - Add validated coverage policies for Decision, Condition, Condition/Decision,