We're currently on Laravel 5.5, which is an LTS release. But I think we should still try to keep on the latest? It shouldn't be a huge amount of work to upgrade by the looks of it.
https://laravel.com/docs/5.6/upgrade
https://laravel.com/docs/5.7/upgrade
tobyzerner
All 7 comments
Fine with me. We can try to catch up during the next beta releases, and then try to upgrade regularly.
franzliedke
on 13 Nov 2018
I personally think it best to push out an upgrade as soon as a new Laravel version is released. Taylor isn't really going to release a huge backward breaking version soon anyway, the framework stabilised and is mature so it all should be pretty manageable to do.
luceos
on 13 Nov 2018
We need this in order to fix our problem with foreign key constraints when using table prefixes and having multiple flarum installs inside the same database.
luceos
on 26 Nov 2018
@luceos We still need to revert #1656.
franzliedke
on 20 Dec 2018
1656 reverted, in all core extensions as well.
luceos
on 15 Jan 2019
馃 odd, maybe forgot to commit them, thanks 馃憤
luceos
on 3 Feb 2019
Related issues
clrh
路
4Comments
jordanjay29
路
3Comments
jordanjay29
路
3Comments
tobyzerner
路
4Comments
datitisev
路
4Comments
Most helpful comment
I personally think it best to push out an upgrade as soon as a new Laravel version is released. Taylor isn't really going to release a huge backward breaking version soon anyway, the framework stabilised and is mature so it all should be pretty manageable to do.