hl run --keep-completed-on-failure keeps successful lockfile entries when another key in the same target fails, so a later run retries only leftover keys. Default hl run still rolls those successes back. A failed target-file write still rolls back this run’s entries for every target that was not written.
View the GitHub release · Full changelog
Breaking changes
None.Features
- Add
hl run --keep-completed-on-failure. Successful keys stay in.hyperlocalise.lock.jsonwhen a sibling key fails. The nexthl runretries only leftover keys instead of retranslating the whole target. A failed target-file write still rolls back this run’s entries for every target that was not written. See run and Lockfile contract.
Fixes
None.Performance
None.Tests
- Mixed-success lock persistence with
--keep-completed-on-failure. - Resume of only the failed key on the next
hl run. - Lock rollback when the target file cannot be written, including later unwritten targets and prior lock entries that must stay.