Laravel makes semantic versioning look bad

Here I go again! I couldn't find it but I remember I did a rant about Laravel needing to pick date formatted versioning instead of semantic versioning when Laravel 12 was announced. The reason I'm writing this is because Livewire can announce a release compatible with an unreleased major version . Lets dive in. Semantic versioning The main goal of semantic versioning is to make the dependency management predictable. It uses three sets of numbers divided by a dot. The context of the numbers from left to right is major, minor and patch. A major number change must happen when there are backward incompatible changes. But it can also happen when multiple features and or changes are introduced. The Laravel situation From the commits on Github and a blog on Lavavel News The biggest change is the optional use of attributes. While they added quite a few attributes, does this really warrant a major update? You could argue raising the minimum required PHP version, 8.2 to 8.3, is cause for a major