Repository navigation
Mifal 0.2.0
mifal update now follows release tags. Merging to main no longer reaches people who have updated to this version; only a pushed vX.Y.Z tag does.
- A tag counts only if it is
vX.Y.Z, sits on the branch the clone tracks, and itsVERSIONfile is the tag. Mistyped, off-branch, local or foreign tags are ignored. - Update is judged against the installed revision. A fork that keeps its own commits can follow its branch with
mifal update --branch. maint/rehearse-upgrade.shand areleaseworkflow: the full suite and an upgrade rehearsal from the previous release run wheneverVERSIONchanges, and a pushed tag is checked to equalVERSIONand sit onmain.
Upgrading from 0.1.x: your first mifal update runs the old code and lands on the tip of main; from then on updates follow release tags.
Setting Mifal up with a coding agent: give it this repository's link; AGENTS.md tells it to check the machine, install the newest release, show you a dry run and wait for your yes, then run mifal doctor.
Tested: full suite under Python 3.9 and 3.13 (186 + 348 + 9 + 18 + 369 tests); a clean-home upgrade from 0.1.2 through the real GitHub remote; a fresh agent following the install page in a disposable home folder.
Not signed. macOS only. Alpha.