Warn the user when patches.lock is not up to date

[cweagans]

Verification

• I have updated Composer to the most recent stable release (composer self-update)
• I have updated Composer Patches to the most recent stable release (composer update cweagans/composer-patches)
• I am using one of the supported PHP versions (8.0+)
• I have searched existing issues and discussions for my problem.
• My problem is not addressed in the troubleshooting guide.

What were you trying to do (and why)?

#472 (comment)

Trying to change a patch/setting.

What happened? What did you expect to happen?

The plugin did nothing and ignored all changes. It should have warned when the resolved patches/settings were different from the ones that generated the lock file.

Contents of composer.json

-

Contents of patches.lock

-

Full output of composer patches-doctor

-

Full output of relevant Composer command with the -vvv flag added

-

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[rajeshreeputra]

In patchPackage if we check hash for the current patches.lock.json file and if there is any change then execute command to relock the patches.lock.json, then I guess this problem will be fixed.

[cweagans]

No, relock should always be an explicit operation. We should never automatically do this.

[cweagans]

You can call isFresh() on the Locker class to check this. If there's a hash mismatch, emit a warning to the console. Def shouldn't relock automatically though.