search

alexeymezenin / laravel-best-practices

Laravel best practices
11.43k stars 2.38k forks source link

Keep your Laravel up to date #111

Closed michael-rubel closed 3 years ago

michael-rubel commented 3 years ago

This PR contains the main tip in 4 languages to keep the framework up to date. The common problem with development applications is outdated dependencies, which lead to limited functionality (and creating "bloated" solutions instead of KISS) and security risks.

alexeymezenin commented 3 years ago

Thanks for the tip. I think it's not always true. Constantly updating a bigger project takes too many resources, sometimes breaks things, etc.

If a team has resources to do this and in this specific project a newer version of Laravel won't break much, then yes, it's a good idea to do that.

michael-rubel commented 3 years ago

It may take resources, but it is the best practice to keep your dependencies fresh. Your app will not break due to an update anyway if you have tests. Laravel itself doesn't have many breaking changes between versions and we have Laravel Shift for the updates too.