Laravel 12.19, weekly updates, and weekly tip

Laravel 12.19

Couple fixes this week and a few new feature brings us to Laravel 12.19.0. Here are the highlights.

  • Introduce ComputesOnceableHashInterface in #56009
  • Add assertRedirectBackWithErrors() to TestResponse in #55987
  • Add fromUploadedFile() to Mailable in #56027
  • Introduce UseEloquentBuilder PHP attribute to register custom Eloquent Builder in #56025
  • Add asFluent model cast in #56046
  • Introduce FailOnException job middleware in #56037
  • Add isSoftDeletable(), isPrunable(), and isMassPrunable() to model class in #56060

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 livestream series building a site for a local cleaning service with AI, Laravel, and Tailwind. I TDD'd the cost estimator. This week, I'll go back to building the web form and displaying results with Tailwind.

Today is the first day I've felt better. So I didn't do much else last week. Basically continued to market WP Static by sharing on Reddit and writing its origin story post.

This week I'm catching up on support emails and recordings for my course.

Weekly Tip

I was skipping around Nuno's interview with Jeffrey Way and caught something. It was actually something Jeffrey was saying about Taylor. He said Taylor prioritizes how the code feels above all else.

As I noted in a recent newsletter, sometimes it's hard to articulate my exact point. But this is an underlying priority for me as well. I care most about how the code feels. Specifically, I care that the code is approachable.

I encounter so much code using design patterns for no reason, forcing a custom structure, or lacking code fundamentals. This makes me more skeptic to adopt the new shiny. But in the end, it's not that I don't like the new shiny, or would use it. I just prioritize having the code be approachable. So I tend to be a laggard, instead of an early adopter.

View Archives →