Timeline for Should composer.lock be committed to version control?
Current License: CC BY-SA 3.0
8 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jan 19, 2023 at 15:02 | comment | added | dvdpzzt | @CarlosMora why would you work with different php version in dev and prod? This can only lead to unknown/undetected bugs since any test you can perform in the dev environment could fail in prod. As an example, you could write code using specific syntax of php 8 that can not be understand by php 7 and even if all your dev tests pass the prod environment fail. | |
| Feb 23, 2022 at 8:23 | comment | added | Carlos Mora | That only works in case prod and dev are EXACTLY the same environment. If you have PHP 7.4 in prod and 8.0 in dev, it may result in different dependencies sets. If you include your .lock file, then you should also include your vendor directory. | |
| Mar 17, 2020 at 13:40 | comment | added | José Lozano Hernández | Thanks, I think this answer explains why you should version composer.lock, and if not, what the consequences are and if you can live with them. | |
| Jun 19, 2017 at 8:03 | history | edited | Paulo Freitas | CC BY-SA 3.0 |
fixed typos and improved formatting
|
| S Jan 10, 2016 at 21:59 | history | suggested | rugk | CC BY-SA 3.0 |
Fixed typos, improved spelling
|
| Jan 10, 2016 at 21:18 | review | Suggested edits | |||
| S Jan 10, 2016 at 21:59 | |||||
| Oct 2, 2015 at 21:50 | review | Late answers | |||
| Oct 2, 2015 at 21:51 | |||||
| Oct 2, 2015 at 21:32 | history | answered | lebobbi | CC BY-SA 3.0 |