Laravel 9.37, weekly updates, and 🔥 tip
Couple patch releases last week and some new features this week brings us to Laravel 9.37. Here are the highlights:
rawValueto Query Builder in #44631
isset()throwing when strict mode is enabled in #44642
- Add event for committing transaction in #44608
- Support checksums for filesystem disks in #44660
- Add handlers for silently discarded and missing attribute violations in #44664
- Allow passing
- Support preloading assets with Vite in #44096
- Add raw content property for mailables in #44703
You may review the full branch diff on GitHub for a complete list of changes.
This version bump and update is automated for subscribers to a Shifty Plan. If you don't have one of those, be sure to bump your constraint and run
composer update to get the latest features.
I feeling wasn't 100% last week. I powered through another live stream working on Blueprint for Hacktober last Wednesday. But I didn't have the energy to work on new features. So I focused on some of the other low hanging issues. I'll continue working on the
meta feature in my final Hacktober live stream tomorrow.
When I was working, my main focus was the Human Shift which came in the week before. I got it upgraded from Laravel 4.2 to 9.x. I ended up forking an old package to create a bridge between the old and new codebases. Normally I don't do this. But to give the launch a better chance at being seamless, it was my only option.
I also recorded another episode of The BaseCode Podcast. This is a continuation of my solo season talking about Shift. I have a few more episodes planned to finish out the story. However, for the last episode I may do a Q&A episode. So if you have anything you want to know about Shift, reply with your question and I'll talk about it in the final episode.
There's been a lot of buzz the last few weeks about some of the "strict mode" additions in Laravel. Taylor demoed some of these during Laracon. But even more have been added since.
Aaron Francis wrote up an awesome blog post on these safety mechanisms. I consider it a must read.
I plan to try enabling "strict mode" for laravelshift.com next week. If everything goes well, I'll likely make this the default for my new Laravel apps.