Laravel 10.31, weekly updates, and 🔥 tip

Laravel 10.31

Quick patch release last week and a minor today brings us to Laravel 10.31. Here are the highlights:

  • Allow Sleep::until() to be passed a timestamp as a string in #48883
  • Fix whereHasMorph() with nullable morphs in #48903
  • Allow chaining a job batch in #48633
  • Add support for Sec-Purpose header in #48925
  • Escape forward slashes when exploding wildcard rules in #48936

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 handed off the Human Shifts. Then I focused on deploying some changes to the Can I Upgrade Laravel online tool. There was more work to do here than I expected. So I paused on that and switched gears to updating the Shifty Plans.

There were two changes. First a price increase that has been long overdue. Particularly for the LTS Plan. It now includes a number of Shifts and will include the Laravel 11.x Shift in February. However, its price from 2 years ago was too low to being with, and as such not pushing users to swap to the Latest Plan.

Second is the renaming of the LTS Plan. LTS versions are now a thing of the past. Yay! I was never a fan. So, this is now called the Legacy Plan to simply indicate it's for an older app.

This week I hope to do the tailwindification of the screens that we're designed last week. I'm really hoping to regain some momentum on the side-project.

🔥 Tip

There was a coding tip I came across, but after being sick at the end of last week I forgot. So I'll have another soft tip this week which is something I actually tweeted out in response to Marcel.

I think one of the greatest qualities a developer can have is the ability to stay focused on a task through completion. I find this more important than being up on the latest technology or practices. Said another way, shipping simple code that works is better than half writing an elegant solution with new technology.