-
Notifications
You must be signed in to change notification settings - Fork 2.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Laravel upgrade checklist #5473
Comments
Keep refining this until you get to L9 LTS and you will make friends! 😄 |
Yeah we have time to be prepared now, will try tomorrow to update to development branch of 9.0 to see what further changes we need to do. We should be fast this time to upgrade, not like last time haha. Being on the latest version fast would gain traction. |
Nice work @filipac - great job. Re:
and
We've been discussing in #5271 about running a pre-processor for Yaml files to gain compatibility with the later versions of Otherwise, everything looks relatively graceful. Did you happen to run the unit tests and confirm that everything still passed? |
@bennothommo i've run them now. Here's what I found so far
After changing the above, the remaning 2 failures and some errors from phpunit are:
|
@filipac Are you able to produce a PR with your changes so far? Might be worth it so that we can see it when run against the unit tests in our CI config, and I can try and reproduce these test results locally. |
I made the upgrade changes today, there is a little more to it than what is described. It's good to know these things early so we can prepare for what's coming. Everything is ready to go in a branch for when the time comes but we won't release with it just yet because it will be too disruptive in addition to the wider release that is coming shortly Thanks @filipac ! 💪 |
Sorry for comment in closed issue. Do we have plan to upgrade to laravel 8 ?. I want to use batch job but laravel 6 doesn't support |
It's already mapped on the roadmap for Laravel 9. It's v2 only. |
I've successfully upgraded a fresh OctoberCMS to use Laravel ^8.0 ( 8.25.0 as of speaking) from Laravel 6 we currently use.
I am sure there is no desire from core team to upgrade to non-lts version for now, but I just want to document what changes should we make to have it working:
symfony/yaml
in october/rain to ^5.1October\Rain\Database\Query\Grammars
give an exception because the implementation is not as in parent class. Changed thecompileUpsert
functions to useIlluminate\Database\Query\Builder
instead ofOctober\Rain\Database\QueryBuilder
and it worked.October\Rain\Events\Dispatcher
needed an update especially inlisten
method cause the signature changedFoundation/Bootstrap/LoadEnvironmentVariables
we need to change the way Dotenv::create is called (first parameter now should be\Illuminate\Support\Env::getRepository()
, the other 2 parameters remain the same.backend/models/brandsetting/fields.yaml
needs an update inavailableColors
keys because the new Symfony Yaml parser sees colors as a comment and we get an exception of invalid Yaml. Did not check other yaml files if they include#
but we should do that.Otherwise, everything seems to work so far on Laravel 8.0. Not sure what the changes will be in 9.0 which is scheduled for September this year, this will be the next LTS. But from what I've seen on Github, nothing too breaking, just upgrading some components.
I think we should be prepared to upgrade anytime and maybe sometime in the future try to mirror the latest supported version of Laravel (not only LTS) since we will now have only one per year. If we keep piling up versions to upgrade, it becomes a nightmare job. Since October is evergreen and we now have some kind of versioning, I do not see a problem mirroring latest Laravel, especially since we have a wrapper around the framework and not much of our/plugin's code needs to be updated.
Is this repo the best place to have this checklist registered, or is https://github.com/octoberrain/meta more suited?
Just want to help and stay on track with the great Laravel releases, this would be a strong point for us (see Statamic which always supports latest versions of Laravel).
The text was updated successfully, but these errors were encountered: