Lumen 5.1

Lumen has a big dependency on the Illuminate packages, so I think Lumen will be updated as well to use the new Illuminate packages. This doesn't mean there will be a 5.1 but I'm 97% sure there will be a 5.1 ;)

Yes, the versions will go hand in hand. When 5.1 Laravel is released 5.1 Lumen will be released. Taylor said this in the Laravel podcast an episode or two back.

Excellent, thanks guys!

This doesn't seem to have happened, two days after Laravel 5.1 release. Hoping Lumen update will follow soon.

https://twitter.com/laravelphp/status/608982072804392960

Lumen 5.1 released as of yesterday

There do not appear to be any upgrade instructions, do any files need to be changed or is it just a matter of updating the version in composer.json?

I didn't find any instructions either..

Find the lack of upgrade guide very unprofessional. Seems so halfassed.

@zandzpider kind of feel like the Laravel 5.1 upgrade guide was lacking, too. Keep finding out about new files (like config/broadcasting.php), changed lines (such as config/app.php using ::class on everything now), deprecated items without details on replacements (like Iron.io push queues), etc. Learning more about the full upgrade process by viewing the source on Github.

Kind of surprising and disappointing.

I submitted a PR with that stuff documented after doing a diff on a base 5.0 v. 5.1 install, it was summarily rejected. You can do a completed update to get all the new files and code structures buy doing just that. Create two new projects, one at 5.1 and the other 5.0 and diff the two. Update your current project per the upgrade guide, then update based on running the diffs on the vanilla projects. It really isn't a whole lot, took me less than an hour.

Seems like there are some attitude shifts going on.. tiny bit concerned, I'm in deep with Laravel and I'm paying for Forge and Envoyer. Taylor has sounded a bit disinterested in a few podcasts, not sure if that's just his personality or if something else is going on.

In some ways, I think it's cool that Taylor seems to handle all of the documentation and support on his products, in other ways I wish there were others involved. Not sure if there are when it comes to docs, but I know every time I contact support for Forge or Envoyer it's always Taylor.

I think it's difficult to provide direct support for products that you developed without some sort of bias, a few times I've felt a bit like it's my fault for not knowing how to do something or what appears to be a glitch isn't one. Honestly, I've received better support for free (free/paid plans) subscription services that I use, such as Mailgun.

Rolling out a major release without any upgrade guide is a bit weird. Laravel is growing larger and larger, support needs to scale with it. Just my opinion as a paying customer, for what it's worth.