Support the ongoing development of Laravel.io →
johnnycho
posted 11 years ago
Installation

Has anyone else run into this? I had a site on 4.1.28 and I ran a simple "composer update" on it. I was expecting it to update the site to 4.2, but instead it updated it to 4.1.30. And I don't see any official Laravel documentation about 4.1.30 anywhere.

Last updated 3 years ago.
0
matthewburrow
replied 11 years ago
Solution

Make sure within your composer.json file, that you have not got 4.1.* within your dependancies. Put 4.2.* instead. Then run a composer update.

Last updated 3 years ago.
0
johnnycho
replied 11 years ago

That did it. Thank you!

Last updated 3 years ago.
0

Sign in to participate in this thread!

Eventy

Your banner here too?

johnnycho johnnycho Joined 16 Mar 2014

Moderators

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

Eventy NativePHP
Fathom
Forge
Envoyer
Beyond Code
BairesDev
N-iX
Litslink

Your logo here?

Laravel.io

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

Laravel.io

Forum Articles Pastebin

Socials

X (Twitter) Bluesky Bluesky GitHub

The community

Laravel Laravel Laravel News Laravel News
Laracasts Laracasts Laravel Podcast Laravel Podcast
© 2025 Laravel.io - All rights reserved.
Terms of service Privacy policy Advertise