Laravel 10.3, weekly updates, and 🔥 tip
Had a minor release last week as well as a patch release this morning bringing us to Laravel 10.3.1. There's a lot in these, but here are the highlights:
- Accept time when generating ULID in #46201
- Simplify collection customization in #46217
- Allow expressions in query builder in #46160
Conditionableto Logger in #46259
channel:listcommand in #46248
JobPoppedevents in #46220
- Allow array dereferencing for
PipelineFacade in #46271
- Support for
upsertwith UUID/ULID primary keys in #46161
- Add processors to logging placeholders in #46344
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.
A day late getting this one out. We had a few doctor appointments for the girls yesterday to get everyone checked up. Fortunately w're doing better and I really hope all this illness is behind us.
Last week I continued to make tweaks to the Laravel 10.x Shift, as well as updating the additional Laravel Shifts to include changes in Laravel 10. I also added an Adopt Laravel type hints to the Workbench. I'll deploy a new build of the Workbench desktop app later this week.
To that point, and as I've mentioned before, I plan to sunset the desktop application. Last week my LaraCasts CreatorSeries was launched. In it I build a command line tool for running automated tasks. I think with relatively low effort, I could rewrite most of the pieces that rely on the UNIX subsystem to PHP. There may be a few tasks that don't port over. But I'm willing to drop them if it means I can get rid of maintaining the Electron app.
That's for the months ahead. This week I will focus on updating the Tests Generator for Laravel 10 and some overall improvements. This is actually my last free week. Emma starts "Daddy Daycare" next week when Ashley's maternity leave ends.
I've mentioned it before, but I think having CI is critical. I love seeing that automation run green for a Pull Request, particularly those opened by Shift. It gives me confidence everything is working as expected.
I have been giving a talk on this recently at conferences. One I pre-recorded for ProcessCon was released last week. So if you're interested in setting up CI with GitHub Actions, this provides a good foundation. Of course you may also run the CI Generator to do most of what I demo in the talk automatically. I'm thinking about doing a series of live streams on these in the future.