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.

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:

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.

I know you are right. Thanks for the advice.

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.

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