Versioning or not the composer.lock file?
Many developers ignore the composer.lock into their .gitignore, because it's an auto-generated file. By analyzing the .gitignore file's purpose this theory is correct, however, is a good practice to manage the version control of this file, and using the composer install command to prepare an environment, not composer update, let's check the basis that sustains that idea in order to apply this change on your projects.
Tags: git, composer, strategy, architecture