v0.11.2

Headline

A file the host already brought to the new release is unchanged, not a conflict, so claim followed by an update no longer blocks.

Fixed

• An owned file whose bytes already equal the new target is unchanged, not a conflict, even when it differs from its recorded original (the host applied the change itself, or took the release's bytes after claiming the file). Nothing is written, the update isn't blocked, and the installed record takes the target, so the original advances. A file that differs from both the original and the target is still a conflict (#216).

Maintenance release on the 0.11 line: the same fix as 0.12.1, for hosts on tey/mod ^0.11 (tey/kit). Fresh-install check: a new Laravel 13.39 app on PHP 8.5 requiring this branch passes mod:install and mod:list, and the install-A, host-writes-B, upgrade script plans unchanged with nothing written (it plans conflict on 0.11.1).

---

What's Changed

• Plan an owned file already at the target as unchanged (0.11.x) by @jaspertey in #219

Full Changelog: v0.11.1...v0.11.2