Dry running Composer update without actually updating dependencies

1 · Amit Merchant · Oct. 5, 2021, 2:01 p.m.
It would always be a good idea to cross-verify/confirm a destructive action before you actually perform it. For instance, while giving users the ability to delete something important, let’s say the user account, it’s a good idea to present them a confirmation popup before he/she deletes the account permanently. Similarly, the composer update is one such action. While it’s not so destructive to update the dependencies, it’s always good to have the ability to check what would get updated when you ...