Laravel 12 support

[jonnott]

Just putting this out there to get ahead of the curve on supporting Laravel 12 when it's released on 24th Feb 2025.

[mfn]

We also need to adapt the CI workflows, otherwise we don't know if it works.

[jonnott]

We also need to adapt the CI workflows, otherwise we don't know if it works.

I think I've done that know .. to the best I know how, anyway. Feel free to propose further changes!

[mfn]

Not there yet, but getting closer.

orchestra/testbench needs to allow ^10 I guess (or the dev version, whichever works)

pro tip: try it locally, but for all illuminate/* packages temporarily just use ^12, then you'll see the dep conflicts quicker.

[barryvdh]

Windows seems to be a bit icky about not escaping ^ in the requirements, but should be good now :)

[jonnott]

Windows seems to be a bit icky about not escaping ^ in the requirements, but should be good now :)

There's a note about that issue for Windows here: https://getcomposer.org/doc/articles/versions.md#writing-version-constraints (under the 'Caret Version Range' section) 🤯

[barryvdh]

Yeah I saw that but not sure how to cleanly do that in the yaml for windows only.

[jonnott]

Yeah I saw that but not sure how to cleanly do that in the yaml for windows only.

Indeed, you wouldn't want that escaping in the yaml and it'd probably break for non-Windows contexts. I assume it's something that needs to be configured differently somehow by GitHub on their CI setup for Windows in terms of how it translates the version constraints to the CLI..

[mfn]

Heroes, thanks!