hegeltest 0.2.0-x86_64-linux → 0.3.0-x86_64-linux

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 002b96ea526d4a771046a0cde5d984554bf945d45d2e1f403d99b1662ea4809e
-  data.tar.gz: 7f58cf4828c9cab85010f4e2e3df1ade6ff7c6092e213007a34421687d2135ac
+  metadata.gz: a6d0f9ced2d7fcce11d764297e9e916389c5eb006835598e36ccadd72569c9e9
+  data.tar.gz: f9114f0b6e477796823feecd83633604ff1a1709e1f05805152e6baa191c58d7
 SHA512:
-  metadata.gz: b4e9384ac83849a11f404908f046cac1ec6144445e36bd6546900fb7d90763194cd600906f07d944ce5d3cf1d1aa3f30942a8b834fea2f1d1daf741b64f56070
-  data.tar.gz: 6137838f7bfb75a2d5d183aaf02306b99093c37e160c6726823402534123523434f02c658c02a4ea72e102a86eaa198a38868b6caacb2a0e85a7e0e8ff537ece
+  metadata.gz: c04ed219d8587f3e0fbccc0d50c45fc2c920258b6f1a5f5672aa13e3af96b3eef2ef35e7ad6a8a2ff6518eaf3803a126957c1af3c69cacaed29d68d83b27a3a9
+  data.tar.gz: 8cbbf7d6e04a6c30fbec40df324b8a63ad1e31c3bbb85cc6cc51d8e1bdd1acd97956d423e164278c073cb5a9a58c86528327e8169d8533a6e727607caca88f0f

data/CHANGELOG.md

@@ -2,15 +2,69 @@
 
 ## [Unreleased]
 
+## [0.3.0] - 2026-10-14
+
+### Engine: libhegel 0.45.4 (was 0.45.1)
+
+The [libhegel 0.45.4 release notes](https://github.com/hegeldev/hegel-rust/releases/tag/libhegel-v0.45.4)
+describe 0.45.4 alone. The
+[engine changelog](https://github.com/hegeldev/hegel-rust/blob/libhegel-v0.45.4/hegel-c/CHANGELOG.md)
+describes each engine release after 0.45.1, up to 0.45.4.
+
+Each platform gem carries `libhegel` 0.45.4. The engine only adds to its C
+interface, and these bindings do not use the additions. The engine
+changes these results for a caller:
+
+- A run that generates no valid test case now raises `Hegel::Error` with a
+  message that starts with `Unsatisfiable`, also when
+  `suppress_health_check:` holds `:filter_too_much` or
+  `:test_cases_too_large`. Before, such a run passed. A test that rejects
+  every case and expects to pass must now draw at least one valid case.
+- `from_regex` records each drawn string as one choice that the pattern
+  constrains. A failure shrinks inside the pattern, so
+  `from_regex("(?:bbbb|a)", fullmatch: true)` now shrinks to `"a"`, where
+  it stopped at `"bbbb"` before. The example database drops a failure that
+  an earlier engine saved for a `from_regex` draw, so the first run after
+  the update does not replay it.
+- `from_regex` rejects a look-behind of variable width, such as
+  `(?<=a*)b`, with `Hegel::Error`, as Python's `re` does.
+- `\w`, `\d`, `\s`, and case-insensitive matching in `from_regex` follow
+  Unicode 17.0. Before, they followed Unicode 15.1.
+- A run stops when its test-case budget or its budget of invalid cases is
+  spent. Before, it could also stop after ten rejected cases in a row that
+  it had seen before.
+
+## [0.2.1] - 2026-10-08
+
+### Engine: libhegel 0.45.1 (was 0.45.0)
+
+The [libhegel 0.45.1 release notes](https://github.com/hegeldev/hegel-rust/releases/tag/libhegel-v0.45.1)
+describe the engine changes.
+
+Each platform gem carries `libhegel` 0.45.1. A caller has nothing to
+change. The engine now reads a NULL string buffer with length zero as the
+empty string, and it rejects a NULL buffer with a nonzero length. These
+bindings send neither case, so a drawn value does not change:
+`from_regex("", fullmatch: true)` draws `""` on both engines.
+
 ## [0.2.0] - 2026-10-07
 
+### Engine: libhegel 0.45.0 (was 0.32.5)
+
+The [libhegel 0.45.0 release notes](https://github.com/hegeldev/hegel-rust/releases/tag/libhegel-v0.45.0)
+describe 0.45.0 alone. The
+[engine changelog](https://github.com/hegeldev/hegel-rust/blob/libhegel-v0.45.0/hegel-c/CHANGELOG.md)
+describes each engine release after 0.32.5, up to 0.45.0.
+
+Each platform gem carries `libhegel` 0.45.0. The engine changed its C
+interface in several places between the two, and these bindings follow
+each change. The sections below list what that changes for a caller.
+
+### Ruby
+
 The floor is Ruby 3.4. A project on Ruby 3.3 stays on 0.1.1. See
 [ADR 0017](docs/adr/0017-raise-the-ruby-floor-to-3-4.md).
 
-Each platform gem carries `libhegel` 0.45.0, up from 0.32.5. The engine
-changed its C interface in several places between the two, and these
-bindings follow each change.
-
 ### Changes a caller has to make
 
 `Hegel.test` no longer takes `stateful_step_count:`. Pass `step_count:` to
@@ -120,6 +174,8 @@ The engine is called through the `ffi` gem. Each platform gem carries the
 matching `libhegel` 0.32.5 build. The platform-independent gem carries none,
 so a run on it needs `HEGEL_LIBHEGEL_PATH` pointing at a local build.
 
+[0.3.0]: https://github.com/meganemura/hegel-ruby/releases/tag/v0.3.0
+[0.2.1]: https://github.com/meganemura/hegel-ruby/releases/tag/v0.2.1
 [0.2.0]: https://github.com/meganemura/hegel-ruby/releases/tag/v0.2.0
 [0.1.1]: https://github.com/meganemura/hegel-ruby/releases/tag/v0.1.1
 [0.1.0]: https://github.com/meganemura/hegel-ruby/releases/tag/v0.1.0

data/docs/README.md

@@ -30,6 +30,7 @@ An index of the design records for `hegel-ruby`.
 - [0021: Run a state machine in rounds, with its own step count](adr/0021-run-a-state-machine-in-rounds-with-its-own-step-count.md)
 - [0022: Keep microsecond times over a nanosecond engine](adr/0022-keep-microsecond-times-over-a-nanosecond-engine.md)
 - [0023: Leave unset settings to the engine's profile](adr/0023-leave-unset-settings-to-the-engines-profile.md)
+- [0024: Release when a merge changes the gem version](adr/0024-release-when-a-merge-changes-the-gem-version.md)
 
 A new decision gets a new record. A changed decision supersedes the old
 record instead of editing it, so the history stays readable.

data/docs/adr/0024-release-when-a-merge-changes-the-gem-version.md

@@ -0,0 +1,49 @@
+# 0024: Release when a merge changes the gem version
+
+## Status
+
+Accepted. Replaces the tag push that started the Release workflow.
+
+## Context
+
+A release took three steps from the maintainer: merge the pull request that
+prepares the version, push the tag `v<version>` on the merged commit, and
+approve the `release` environment. The tag carried no decision of its own.
+The version in `lib/hegel/version.rb` already said what to release, and the
+approval was the real gate.
+
+A daily routine now opens a pull request for each new libhegel release, with
+a "Prepare <version>" commit. The maintainer's part should be the decision,
+not the steps around it.
+
+GitHub does not start a workflow from a push that a workflow makes with its
+own `GITHUB_TOKEN`. A workflow that pushed the tag after a merge would
+therefore not start a tag-triggered Release workflow.
+
+## Decision
+
+The Release workflow starts on a push to `main` that changes
+`lib/hegel/version.rb`. Its first job reads the version and looks for the tag
+`v<version>`. When the tag exists, as after a revert to a released version,
+the run stops there. Otherwise the publish job waits for the `release`
+environment approval, then builds and pushes the gems from the merged
+commit. The last job creates the tag on that commit and the GitHub release
+together, with `gh release create --target`.
+
+The tag is created last, after the gems are out. A rejected approval then
+leaves no tag behind, and rerunning the workflow run releases the same
+commit later.
+
+Two alternatives were refused. A workflow that only pushed the tag needs a
+personal access token or a GitHub App token to start the tag-triggered
+workflow, which is a long-lived secret for one step. Creating the tag before
+the approval leaves a tag for a version that may never ship, and the check
+job would then skip that version for good.
+
+## Consequences
+
+A release is one merge and one approval. Merge a pull request that changes
+the gem version only when that version should ship.
+
+A tag pushed by hand no longer starts a release. The workflow's own run on
+`main` is the place to retry one.

data/lib/hegel/libhegel_version.rb

@@ -5,5 +5,5 @@ module Hegel
   # Hegel::VERSION (the gem's own release): hegel-go and hegel-typescript keep
   # the two separate too, so bumping the pinned engine can land as its own
   # commit without also releasing a new gem version.
-  LIBHEGEL_VERSION = "0.45.0"
+  LIBHEGEL_VERSION = "0.45.4"
 end

data/lib/hegel/runner.rb

@@ -178,9 +178,9 @@ module Hegel
     # Pulls test cases from +run+ until hegel_next_test_case reports none
     # left (a nil out-parameter, not an error). Never counts iterations
     # itself: test_cases bounds generation, not how many times shrinking
-    # and rejected cases call the body. Measured against libhegel 0.45.0, a
+    # and rejected cases call the body. Measured against libhegel 0.45.4, a
     # run configured for 20 test cases whose body rejected nearly every case
-    # took 1040 to 1537 iterations. +stats+ does its own, different counting
+    # took 475 to 1607 iterations. +stats+ does its own, different counting
     # -- see GenerationStats above.
     def drive(impl, ctx, run, stats, captures, &block)
       loop do

data/lib/hegel/version.rb

@@ -1,5 +1,5 @@
 # frozen_string_literal: true
 
 module Hegel
-  VERSION = "0.2.0"
+  VERSION = "0.3.0"
 end

data/skills/hegel-ruby/references/ruby/reference.md

@@ -494,12 +494,12 @@ expose) are not available in this binding; `codec:`, `min_codepoint:`, and
 `max_codepoint:` are the alphabet controls it exposes today.
 
 Other generators cover most character-set jobs. These results were measured
-with libhegel 0.45.0:
+with libhegel 0.45.4:
 
 | Job | Generator | Measured output |
 |---|---|---|
-| Characters to include | `from_regex("[ぁ-んA-Z0-9]{1,5}", fullmatch: true)` | `"ぁ"`, `"Hわ9ごう"`; 30 draws all matched the pattern |
-| Characters to exclude | `from_regex("[^,\\t\\n]{0,6}", fullmatch: true)` | `""`, `"\u008FBՔ\u0014੐C"`; 30 draws contained no comma, tab, or newline |
+| Characters to include | `from_regex("[ぁ-んA-Z0-9]{1,5}", fullmatch: true)` | `"0"`, `"ぢ3"`, `"るJこ"`; 30 draws all matched the pattern |
+| Characters to exclude | `from_regex("[^,\\t\\n]{0,6}", fullmatch: true)` | `""`, `"\u0010ùóR'<"`; 30 draws contained no comma, tab, or newline |
 | A contiguous block | `text(min_codepoint: 0x300, max_codepoint: 0x36F)` | Every character of 100 draws was in U+0300 through U+036F |
 | An arbitrary alphabet | `arrays(sampled_from(%w[ß a İ]), max_size: 4).map(&:join)` | 30 draws, each built only from `ß`, `a`, and `İ` |
 
@@ -1219,11 +1219,18 @@ value already in the shape you need):
 
 ```ruby
 result = Hegel.test(test_cases: 20, suppress_health_check: [:filter_too_much], verbosity: :quiet) do |tc|
-  tc.draw(integers.filter { |_n| false })
+  tc.draw(integers(min_value: 0, max_value: 1_000_000).filter(&:zero?))
 end
 result # => nil
 ```
 
+The suppressed check does not let a run pass with no valid input. A
+predicate that never holds, such as `integers.filter { |_n| false }`,
+still raises `Hegel::Error`, with a message that starts with
+`"Unsatisfiable: unable to satisfy the test's assumptions."` Since libhegel
+0.45.2, the engine ends every run that generates no valid test case this
+way.
+
 ## Gotchas
 
 1. **Float defaults include NaN and infinity when unbounded.** `floats` with

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: hegeltest
 version: !ruby/object:Gem::Version
-  version: 0.2.0
+  version: 0.3.0
 platform: x86_64-linux
 authors:
 - meganemura
@@ -69,6 +69,7 @@ files:
 - docs/adr/0021-run-a-state-machine-in-rounds-with-its-own-step-count.md
 - docs/adr/0022-keep-microsecond-times-over-a-nanosecond-engine.md
 - docs/adr/0023-leave-unset-settings-to-the-engines-profile.md
+- docs/adr/0024-release-when-a-merge-changes-the-gem-version.md
 - docs/architecture.md
 - lib/hegel.rb
 - lib/hegel/draw_name.rb