Laravel 12.47, weekly updates, and weekly tip

Laravel 12.47

Several patch releases last week and two minor releases brings us to Laravel 12.47 this week. Here are the highlights:

• More enum support in #58310, #58343, and #58350
• Add Arr::onlyValues() and Arr::exceptValues() in #58317
• Add Collection::containsManyItems() in #58312
• Add MySQL DDL locking options in #58293
• Add @includeIsolated for isolating data to includes in #58311
• Add Cache::withoutOverlapping() in #58303
• "Vector things" (Postgres support) in #58337

You may review the full branch diff on GitHub for a complete list of changes.

Weekly Journal

Last week I got crazy and broke ground on three new Shifts.

The first was actually during my Wednesday livestream. I started a new Laravel Cloud PreCheck (maybe not the final name). This is in partnership with Laravel. They wanted a tool where potential users could check Laravel Cloud compatible. While most modern Laravel applications likely meet the requirements, being able to point to your repo and perform an automated check was ideal. So they thought of Shift, and I'm glad to help.

Next, I started implementing the strategies I cover in the Fast Laravel video course for my other Laravel projects. I got tired of configuring the application, copying over the custom middleware, and installing our package. So, I created a free "Fast Laravel" Shift. Again, just a nice bit of automation so you're not doing it yourself for every project.

And, Monday I broke ground on a Livewire 4.x Shift. This was a bit of last minute decision. But there seemed to be strong interest for me to build one.

In fairness, people have asked for Livewire Shifts over the years. I planned on building one for Livewire 3. But they released their own internal tool. It works pretty well, so I didn't feel a need to overlap. But, they won't have an internal tool for Livewire 4. So the Livewire 4.x Shift will launch tomorrow with the official release of Livewire 4.

Weekly Tip

Keep calm and carry on.

I've been repeating this famous British World War II motivational slogan. I posted a long form tweet, but the short version is with the recent news from fellow Laravel community founders and coming off my own flat year, I'm a bit nervous.

Shift is dealing with a sort of a 1-2 punch. It's not only impact from AI, but impact from Laravel's "optional" releases. I honestly don't know if they'll be a Laravel 13.

I still believe Shift has a place. I believe it still does a better job upgrading Laravel (or Livewire) than AI. However, this may not always be the case. Or there may not be a Laravel release to upgrade.

This is on my mind for 2026. I'm trying to "keep calm". If Shift is going to "carry on", it needs to adapt. So I'm working to figure out the next move.