> * Use full version numbers for your dependencies. The tradeoff for this approach is to have to resolve version conflicts manually anytime there is more than

> * Use full version numbers for your dependencies. The tradeoff for this approach is to have to resolve version conflicts manually anytime there is more than minor dependency changes. In particular, adding a package that is newer than most of your dependencies can be a nightmare when you locked down all the working revisions of your libraries. On one hand there is less drama about packages changing under one's feet, on the other hand part of composer's job is shifted back to the dev who does the package updates. Personally I would advise a more balanced approach of allowing minor version changes and only block major ones.