colitur.git - deterministic OCaml engine to compute and validate liturgical calendars for multiple rites, template-driven output to year 9999

	Commit message (Collapse)	Author	Age	Files	Lines
*	docs: CHANGELOG entry for 1.0.0	Lukasz Kasprzak	2026-08-24	1	-0/+6
\|
*	docs: CHANGELOG entry for 0.10.1	Lukasz Kasprzak	2026-08-21	1	-0/+3
\|
*	feat(config): flavour is settable, and an INI overlay is diagnosed	Lukasz Kasprzak	2026-08-21	1	-0/+9
\| \| \| \| \| \| \| \| \| \| \|	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.0	Lukasz Kasprzak	2026-08-18	1	-0/+3
\|
*	docs: CHANGELOG entry for 0.6.0	Lukasz Kasprzak	2026-08-18	1	-0/+3
\|
*	docs: CHANGELOG entry for 0.5.0	Lukasz Kasprzak	2026-08-18	1	-0/+3
\|
*	docs: CHANGELOG entry for 0.4.0	Lukasz Kasprzak	2026-08-18	1	-0/+3
\|
*	docs: CHANGELOG entry for 0.3.1	Lukasz Kasprzak	2026-08-18	1	-0/+3
\|
*	docs: CHANGELOG entry for 0.3.0	Lukasz Kasprzak	2026-08-17	1	-0/+3
\|
*	docs: CHANGELOG entry for 0.2.0	Lukasz Kasprzak	2026-08-17	1	-0/+3
\|
*	feat(cli): --version, a CHANGELOG, and a release target	Lukasz Kasprzak	2026-08-17	1	-0/+6
	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.