colitur.git/CHANGELOG.md, branch v0.10.0deterministic OCaml engine to compute and validate liturgical calendars for multiple rites, template-driven output to year 9999https://git.labunix.xyz/colitur.git/atom?h=v0.10.02026-08-21T10:19:43Zfeat(config): flavour is settable, and an INI overlay is diagnosed2026-08-21T10:19:43ZLukasz Kasprzaklukas@labunix.xyz2026-08-21T10:19:43Zurn:sha1:055deaedd6bc1acb770bd96b7da8f985ab0f4f0b
The escaping flavour was the one rendering setting with no config key,
so a template whose extension says nothing needed the flag every run.
Unset still means infer, which config --show reports as (infer) rather
than (none).
Backfills the 0.8.0 and 0.9.0 changelog entries. Both were tagged by
hand rather than through 'make release', which is precisely the guard
that would have refused a release with no changelog line.
docs: CHANGELOG entry for 0.7.02026-08-18T12:27:13ZLukasz Kasprzaklukas@labunix.xyz2026-08-18T12:27:13Zurn:sha1:94d95fd9b26e6bdd39fd08b7555948df56eee1eddocs: CHANGELOG entry for 0.6.02026-08-18T11:23:36ZLukasz Kasprzaklukas@labunix.xyz2026-08-18T11:23:36Zurn:sha1:5d3e201c21427ec54ff3d58bade04e40cb621ae9docs: CHANGELOG entry for 0.5.02026-08-18T10:36:25ZLukasz Kasprzaklukas@labunix.xyz2026-08-18T10:36:25Zurn:sha1:c61ddde803e1e5a2df76fcacdf1f01c8dc3e0718docs: CHANGELOG entry for 0.4.02026-08-18T09:43:34ZLukasz Kasprzaklukas@labunix.xyz2026-08-18T09:43:34Zurn:sha1:590429b68105013e4dc0963d57d0eaca584427ccdocs: CHANGELOG entry for 0.3.12026-08-18T07:10:46ZLukasz Kasprzaklukas@labunix.xyz2026-08-18T07:10:46Zurn:sha1:0158449f7060570bf3de17a8869b4ca668bd837fdocs: CHANGELOG entry for 0.3.02026-08-17T20:24:33ZLukasz Kasprzaklukas@labunix.xyz2026-08-17T20:24:33Zurn:sha1:921a17583067f49ed5c9f900b649d049c2b876ecdocs: CHANGELOG entry for 0.2.02026-08-17T18:57:22ZLukasz Kasprzaklukas@labunix.xyz2026-08-17T18:57:22Zurn:sha1:301b9abd8e47e487dc5159d49d8e2432bc62488cfeat(cli): --version, a CHANGELOG, and a release target2026-08-17T14:19:02ZLukasz Kasprzaklukas@labunix.xyz2026-08-17T14:19:02Zurn:sha1:cc6655134e155dd0879ecb8eb009271e17488834
Groundwork for tagging. The project had no version anywhere: not in
dune-project, not in the binary, no CHANGELOG, no tags.
The version lives in two places -- dune-project, which generates
colitur.opam, and a constant in bin/main.ml, which is what --version
prints. Two rather than one because dune's watermarking only substitutes
in a release tarball, so a binary built the ordinary way from a checkout
would report a placeholder. The release target rewrites both and then
re-checks both, and finally requires the freshly built binary to report
the version it just wrote: a release that bumped one and not the other
would ship a binary disagreeing with its own package metadata.
--version is deliberately not embedded in the help text. cli.t pins
help's first line, and a version there would mean editing a test
expectation every release for no gain.
The release target mirrors lectio's, refusals included: no release from a
dirty tree, none without a CHANGELOG entry for that version, none whose
version bump silently failed to apply, and `make check` -- the full
1583-9999 sweep, not the sampling suite -- must pass before the tag is
created.