API Versioning in Laravel
– blog.treblle.com - submitted by Steve McDougall
Learn how to version your Laravel APIs properly in this walk through tutorial.
Read more [blog.treblle.com]
Posts tagged with versioning
Dropping support for a PHP version is not a breaking change
Seb explains why it's perfectly safe to drop a major version of PHP without tagging a new major version of a package.
Read more [sebastiandedeyne.com]
Join 9,500+ smart developers
Get my monthly newsletter with what I learn from running Spatie, building Oh Dear, and maintaining 300+ open source packages. Practical takes on Laravel, PHP, and AI that you can actually use.
No spam. Unsubscribe anytime. You can also follow me on X.
"Freek publishes a super resourceful and practical newsletter. A must for anyone in the Laravel space"
Laravel LTS is a Trap
A couple of months ago Jason McCreary, creator of Laravel Shift, wrote down his opinion on the Laravel's LTS release. I couldn't agree more with this piece.
The more developers that get trapped by LTS, the more of a drag it creates on the Laravel community. Potentially having adverse affects on its growth. Using LTS as a minimum compatibility line for a Laravel package or other third-party code is understandable. But freezing your apps to an LTS version is not. Your apps should run the latest stable version of Laravel.
https://medium.com/@jasonmccreary/laravel-lts-is-a-trap-97b1d1103961
The Road to Monolog 2.0
One of the main questions when doing a major release is which minimum PHP version to support going forward. Last summer I decided I wanted to do a big jump from 5.3 and directly target PHP 7. It provides a lot of nice features as well as performance improvements, and as Monolog is one of the most installed packages on Packagist I wanted to help nudge everyone towards PHP 7.http://seld.be/notes/the-road-to-monolog-2-0
