Support the ongoing development of Laravel.io →
Installation Configuration Architecture
Last updated 2 years ago.
0

Do what I do, composer update to update the framework, then create a new branch in your git repo called laravel-dev, add a remote to laravel/laravel, pull, then merge the changes from that branch into your master branch...

Handle the conflicts, and you're good to go. Try to do this every few days so it doesn't pile up on you.

Here is a good walk-through.

Last updated 2 years ago.
0

Thanks - ive been doing something similar. Im just getting hit with issue after issue.

Im currently on the issue: TokenMismatchException in VerifyCsrfToken.php line 25:

Last updated 2 years ago.
0

There will be a lot of breaking changes until the release, just gotta work through them. That's one of the downsides of working with the development branch of any project.

Last updated 2 years ago.
0

I know you are right. Thanks for the advice.

Last updated 2 years ago.
0

You could stick to a specific commit so that composer doesn't pull down any changes after that commit:

"require": {
        "laravel/framework": "dev-master#3c9d67ad657290c889969c85867677f35e6ae8f1"

Just use the hash of the latest commit and it will be frozen.

Last updated 2 years ago.
0

Thanks site sense. Funny enough - thats what I have just got working.

Last updated 2 years ago.
0

Sign in to participate in this thread!

Eventy

Your banner here too?

qazjayp99 qazjayp99 Joined 27 Jun 2014

Moderators

We'd like to thank these amazing companies for supporting us

Your logo here?

Laravel.io

The Laravel portal for problem solving, knowledge sharing and community building.

© 2024 Laravel.io - All rights reserved.