Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The composer.lock file should really be tracked, as it helps ensure consistency of package versions and reduces the amount of variance, for instance helping for any issues arising from diff dependency versions to be more easily tracked and resolved... Even for sites with different packages, standardizing tracking it across the board helps ensure their local and live environments are using the same versions of packages, etc.
I've run
composer update
prior to committing, so should be appropriately representative of the current state of develop's dependencies