Laravel 11.42, weekly updates, and deals
Laravel 11.42
With over 2 weeks of PRs, there's a lot in this week's release of Laravel 11.42. Here are the highlights:
- Add
Macroable
andfill()
toFluent
in #54404 - Allow passing
precision
toNumber::currency()
in #54456 - Fluent numeric validation in #54425
- Add relative date shorthands to Query Builder in #54408
- Where doesnt have nullable morph in #54363
- Add Builder On Clone callback support in #54477
- Add the ability to skip migrations within tests in #54441
- Add
missing
toContext
in #54499 - Add
setAssetRoot
toUrlGenerator
in #54530 - Add middleware and failed handlers for broadcastable events in #54562
- Allow JSON assertions on streamed content in #54565
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.
Weekly Journal
Last week I continued my Wednesday livestreams with a Part 2 of hacking on ideas for Laravel 12. One of them actually got merged. The other two were closed. I'll revisit one of them after chatting with Taylor in a final stream tomorrow.
There were a lot of readers who tried WP Static last week. Thank you! JT and I have been smoothing out a few rough edges. I'm also recording a proper demo video. As right now it's just a placeholder of the northern lights. With all of that, I will delay sharing it publicly until after the Laravel 12 release. But the service should be fully functional if any more of you want to try it out.
With the rest of the week, I got most of the Laravel 12.x Shift written. There will be changes all the way into (and after) the official release of Laravel 12 on February 24th. But I like to have a pre-release version available for early adopters to run (at a discount) to test both the Laravel 12.x Shift and Laravel 12 itself.
Weekly Tip
Despite most of my PRs being merged, I've found my PR experience has become rather noisy. In fact, my PR in today's release had more "thumbs down" than it did "thumbs up". So, a few tips.
First, you never know what's going to get merged. It depends mostly on if Taylor sees its immediate value. You can sell that with a good PR description. But it's really about that moment in time. I've had PRs get closed, just to get merged a year later. So, you never know. If you like the feature, keep trying. If it never gets in, make it a package.
Second, keep the good vibes going. Commenting on every PR or leaving a "thumbs downer" creates noise. If you see a bug or disagree with something, by all means, say what you must. But do so sparingly and keep it encouraging. Politely point out your concern and offer alternatives. Again, keep the good vibes going.