Brent • 3/26/2020

Minor versions, breaking changes

Read Original

The 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.

0 comments
#dependency management #php #semantic versioning
Minor versions, breaking changes

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
React vs Browser APIs (Mental Model)
Jivbcoop • 4 votes
2
React, useEffect, and Stale Closures: How to Avoid Them with Dependencies and useRef
Jivbcoop • 3 votes
3
Building Type-Safe Compound Components
TkDodo Dominik Dorfmeister • 2 votes
4
Dew Drop – January 15, 2026 (#4583)
Alvin Ashcraft • 1 votes
5
Using Browser Apis In React Practical Guide
Jivbcoop • 1 votes
6
Better react-hook-form Smart Form Components
Maarten Hus • 1 votes
7
Building a Complete FIRE Calculator App with GitHub Copilot in One Chat Session
James Montemagno • 1 votes