colitur.git/CHANGELOG.md, branch v0.8.0 deterministic OCaml engine to compute and validate liturgical calendars for multiple rites, template-driven output to year 9999 https://git.labunix.xyz/colitur.git/atom?h=v0.8.0 2026-08-18T12:27:13Z docs: CHANGELOG entry for 0.7.0 2026-08-18T12:27:13Z Lukasz Kasprzak lukas@labunix.xyz 2026-08-18T12:27:13Z urn:sha1:94d95fd9b26e6bdd39fd08b7555948df56eee1ed docs: CHANGELOG entry for 0.6.0 2026-08-18T11:23:36Z Lukasz Kasprzak lukas@labunix.xyz 2026-08-18T11:23:36Z urn:sha1:5d3e201c21427ec54ff3d58bade04e40cb621ae9 docs: CHANGELOG entry for 0.5.0 2026-08-18T10:36:25Z Lukasz Kasprzak lukas@labunix.xyz 2026-08-18T10:36:25Z urn:sha1:c61ddde803e1e5a2df76fcacdf1f01c8dc3e0718 docs: CHANGELOG entry for 0.4.0 2026-08-18T09:43:34Z Lukasz Kasprzak lukas@labunix.xyz 2026-08-18T09:43:34Z urn:sha1:590429b68105013e4dc0963d57d0eaca584427cc docs: CHANGELOG entry for 0.3.1 2026-08-18T07:10:46Z Lukasz Kasprzak lukas@labunix.xyz 2026-08-18T07:10:46Z urn:sha1:0158449f7060570bf3de17a8869b4ca668bd837f docs: CHANGELOG entry for 0.3.0 2026-08-17T20:24:33Z Lukasz Kasprzak lukas@labunix.xyz 2026-08-17T20:24:33Z urn:sha1:921a17583067f49ed5c9f900b649d049c2b876ec docs: CHANGELOG entry for 0.2.0 2026-08-17T18:57:22Z Lukasz Kasprzak lukas@labunix.xyz 2026-08-17T18:57:22Z urn:sha1:301b9abd8e47e487dc5159d49d8e2432bc62488c feat(cli): --version, a CHANGELOG, and a release target 2026-08-17T14:19:02Z Lukasz Kasprzak lukas@labunix.xyz 2026-08-17T14:19:02Z urn: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.