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
1
The Beautiful Web
Jens Oliver Meiert
•
2 votes
2
Container queries are rad AF!
Chris Ferdinandi
•
2 votes
3
When your coding agent doesn’t understand your project, you’ll get junk
Benjamin Cane
•
1 votes
4
LLM Use in the Python Source Code
Miguel Grinberg
•
1 votes
5
Wagon’s algorithm in Python
John D. Cook
•
1 votes
6
An example conversation with Claude Code
Dumm Zeuch
•
1 votes