Laravel 12.33, weekly updates, and weekly tip

Laravel 12.33

There was a release last week follow by a crapload of patch releases. Then another release today brings us all the way to Laravel 12.33.0.

Here are the highlights from both Laravel 12.32 and 12.33:

  • Extend SQS FIFO and fair queue support in #57187
  • Introduce Http::batch() in #56946
  • Introduce "after" rate limiting in #57125
  • Add enums support for ThrottleRequests::using() in #57190
  • Fix nested can and inherit models on route groups in #57172
  • Batch job failure callback support in #55916
  • Add Stringable::doesntContain() for symmetry in #57279
  • Fix using @pushIf Blade Directive with complex conditions in #57274

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

My daughters woke up with a fever last Tuesday. So, needless to say, I missed the newsletter last week. Fortunately they were feeling better by Thursday as my wife and I had planned an overnight trip for our anniversary.

Last week, I continued on my quest to cache as much of laravelshift.com with Cloudflare as possible. I'm getting into some pretty crazy numbers. Way past my expectations. Of course, I'm leaving some tweets along the way and will share tips here soon.

On the flight, I continued working on the "smarter migrations" feature for my Laravel Additions package. This adds some better guessing based on the name passed to artisan make:migrate. Using that, it generates a fuller migration. I just merged it, and will officially tag something tomorrow.

With the rest of this week, I'll keep caching with Cloudflare and probably do some maintenance on Blueprint. Oh, and there is some outstanding Human Shift work. Just waiting on the client to finish review.

Weekly Tip

Even without my Laravel Additions package, Laravel does some guessing when running make:migration.

If your name is prefixed with create_, Laravel will generate a Schema::create() migration for you. Otherwise, it will generate a Schema::table() migration.

If your name ends with _to_xxx, from_xxx, or in_xxx, Laravel will also guess the table name.

A few real-world examples:

# generates a `Schema::create()`
php artisan make:migration create_products_table
php artisan make:migration create_products
 
# generates a `Schema::table()`
php artisan make:migration add_stripe_id_to_products_table
php artisan make:migration add_stripe_id_to_products