Minor versions, breaking changes
Read OriginalThe article details a real-world incident where a `composer update` in a Laravel project caused a breaking change due to a minor version bump in a dependency (`spatie/laravel-view-components`). It explains how nested dependencies and version constraints (like `league/commonmark`) can create conflicts, and demonstrates using `composer why-not` to diagnose the issue. It serves as a cautionary tale about semantic versioning and dependency management in PHP/Composer projects.
Comments
No comments yet
Be the first to share your thoughts!
Browser Extension
Get instant access to AllDevBlogs from your browser
Top of the Week
No top articles yet