Framework applications depend on a graph of packages, plugins and PHP extensions. Updating everything without review can introduce breaking changes; never updating leaves known defects and security issues in place.
Establish package ownership
Keep Composer manifests and lock files under version control. Know which packages are runtime dependencies and which are development-only. Record why unusual packages or plugins are required.
Review before updating
Inspect outdated packages, security advisories, supported PHP versions and framework compatibility. Prefer targeted updates for routine maintenance and planned upgrade branches for major changes.
Test the dependency graph
Run unit and integration tests, static analysis and application smoke tests. Exercise framework integrations such as queues, cache, sessions, storage and mail.
Deploy with rollback options
Back up data where migrations are involved, deploy during a controlled window and monitor logs. Keep the previous release available when the deployment model supports rollback.
Further reading
- Composer: https://getcomposer.org/doc/
- Packagist: https://packagist.org/