title: Should composer.lock be committed to version control?
body: <p>I'm a little confused with <code>composer.lock</code> used in an application with a repository.</p>
  
  <p>I saw many people saying that we should not <code>.gitignore</code> <code>composer.lock</code> from the repository.</p>
  
  <p>If I update my libraries in my dev environment, I will have a new <code>composer.lock</code> but I will not be able to update them into production, will I ?</p>
  
  <p>Won't it generate conflicts on this file ?</p>