diff options
| author | Lukasz Kasprzak <lukas@labunix.xyz> | 2026-08-17 21:00:17 +0200 |
|---|---|---|
| committer | Lukasz Kasprzak <lukas@labunix.xyz> | 2026-08-17 21:00:17 +0200 |
| commit | d8ce8c3806111e1d1ba54d2ef99a8ae550c7567b (patch) | |
| tree | 90ce70d45eb104d642c3a1375f8c97b8853eb21f /bin | |
| parent | 301b9abd8e47e487dc5159d49d8e2432bc62488c (diff) | |
| download | colitur-0.2.0.tar.gz colitur-0.2.0.zip | |
test(cli): pin the version's shape, not its literalv0.2.0
The release target bumps bin/main.ml and dune-project, but cli.t pinned
the literal too, so cutting 0.2.0 failed `make check` on a cram diff that
was purely the bump working correctly. Every release would have had to
edit a test for no gain.
The shape is asserted here instead. The value is already checked where it
can actually drift: the release target requires the freshly built binary
to report the version it just wrote.
Diffstat (limited to 'bin')
| -rw-r--r-- | bin/main.ml | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/bin/main.ml b/bin/main.ml index 06732b3..fc50fae 100644 --- a/bin/main.ml +++ b/bin/main.ml @@ -368,7 +368,7 @@ let readings_report ~overlays y = resolved_year_report ~line:readings_line ~over same reason. Deliberately NOT embedded in [help_text]: the cram test pins help's first line, and a version in it would make every release edit a test expectation for no gain. *) -let version = "0.1.0" +let version = "0.2.0" let help_text = {|colitur -- deterministic liturgical calendar engine (Roman rite, 1962) |
