All software has dependencies: programming language, framework, and libraries. New versions for these dependencies with security fixes, bug fixes, or new features are regularly released. A new version is not always fully compatible with its predecessor. Teams that can rely on their test automation to answer the question of whether the new version of a dependency is problematic or not are in a good position.
This presentation shows best practices for upgrading dependencies without fear in projects that have high test coverage as well as approaches for projects without test automation.
More information and tickets: https://phpconference.com/