Anchors 0.1.374

What's new in 0.1.374

Fix: evidence kept by declaration survives the next change that proves nothing
anchors keep-evidence moved a file's evidence to its current content and moved the node's
revision with it, but left the node's evidence revisions — the content without what proves
nothing, such as the header's date — those of the previous content. The next rebuild compared
the new content's evidence revisions with those, found them changed, and dropped what the
declaration had kept. At MIF, keep-evidence --lines on 781 files whose imports alone had
changed, followed by anchors touch bumping their headers' dates, left 271 of them with no
mutation.
The node now takes the evidence revisions of the content kept. The same holds for the files
check --fix repairs and for the specs anchors migrate rewrites.
keep-evidence also brings back the mutation the map at HEAD holds for a file whose signal
holds none — a coverage run at the new content had started a new signal, and the command
found nothing to carry. A mutation measured again at the new content stays its own. To recover
files that lost their mutation this way, run keep-evidence --lines on them again before the
map is committed: the map at HEAD is where the mutation comes back from.
Everything in the v0.1.351 notes still applies: run anchors migrate once, crossing format 8.
Changelog
- a9c9092 fix(keep-evidence): the kept evidence survives a date; a mutation HEAD holds comes back

Full release notes »