Closed Slamdunk closed 6 years ago
After changing composer.json file composer.lock should be updated as well.
Of course, but how?
I mean, we all know the command composer update --lock
but thisis not the case.
The lock file here is present to test a particular set of depencencies that are neither the lowest nor the latest. The fact is that I don't know how to rebuild it, or putin another way, I don't know the exact envirnoment on how the lock file should be updated into.
Of course, but how?
Basically build should work with any lock file - generated on any env but and builds should check set of different configuration - with different dependencies. I think you can use either
$ composer update --lock
or:
$ composer update nothing
and it will just update the hash in composer.lock
. And it's enough.
I repeat what I saidin the previous comment: of course composer update --lock
updates the lock file hash, but I think it's useless because it doesn't address the purpose of the lock file.
Btw, I've updated it.
@Slamdunk the only reason to do that is to keep composer.lock
in sync, even if dependencies are still older than the latest ones.
Any ETA to merge?
@Slamdunk thank you
After changing
composer.json
filecomposer.lock
should be updated as well.