eiriksm / cosy-composer / 36814233479

90%

main: 90%

push

github

Do not report "not updated" when the lock file did not match the update data

Before running the composer update, compare the lock file on disk with the
lock data the update check was based on, for the packages we expect to be
updated. If they differ, the lock file has been changed by something else
than this update, for example the default branch already having it. If
composer then reports that nothing was updated, we log that the lock file did
not match and skip the package, instead of reporting a failed update.

The comparison is made before the update runs, so an update that actually
changes the lock file (for example to a lower version) is still reported as
not updated.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01KLebHMTMFmGiBtY5RKVTqh

28 of 36 new or added lines in 1 file covered. (77.78%)

2431 of 2694 relevant lines covered (90.24%)

60.63 hits per line