RepoJournal
Laravel

@laravel

PHP's most popular framework — Forge, Vapor, and a massive paying audience

Pick a date

  1. Sun 3 may
  2. Mon 4 may
  3. Tue 5 may
  4. Wed 6 may
  5. Thu 7 may
  6. Fri 8 may
  7. Sat 9 may
  8. Sun 10 may
  9. Mon 11 may
  10. Tue 12 may
  11. Wed 13 may
  12. Thu 14 may
  13. Fri 15 may
  14. Sat 16 may
  15. Sun 17 may
  16. Tue 19 may
  17. Thu 21 may
  18. Sat 23 may
  19. Sun 24 may
  20. Mon 25 may
  21. Tue 26 may
  22. Wed 27 may
  23. Thu 28 may
  24. Fri 29 may
  25. Sat 30 may
  26. Sun 31 may
  27. Mon 1 jun
  28. Mon 8 jun
  29. Tue 9 jun
  30. Today 10 jun

The Wire · Showcase

LARAVEL AI FIXES PROVIDER KEY RESOLUTION WHILE SAIL BACKPORTS 8.5 DOCKERFILE ACROSS LEGACY VERSIONS

By RepoJournal · Filed · About Laravel

Laravel's AI package just patched a consistency bug in provider option resolution that was forcing boilerplate code into every provider implementation [ref:1], while Sail v1.59.0 rolled out unified Dockerfile improvements across five PHP versions in one shot [ref:10].

The AI package fixed a root cause issue [1] where provider key resolution wasn't centralized, forcing redundant code across implementations — this merge pulls that logic into TextGenerationOptions once and for all. Separately, Laravel's adding validation teeth to embeddings input [8], rejecting blank strings and non-strings before they hit providers, cutting useless API calls. There's also a fix pending for database connection respect in Conversation and ConversationMessage models [9], which were ignoring configured secondary databases and hitting the default instead. Across five repositories — AI, Sail, Boost, Agent Skills, and Agent Detector — the team pinned all GitHub Actions to commit SHAs and added Dependabot automation [4] [5] [6] [7], a security hardening move that drops GITHUB_TOKEN exposure after checkout. Sail's backport [3] brought 8.5 Dockerfile improvements down to 8.4, 8.3, 8.2, 8.1, and 8.0, including playwright setup and MYSQL_CLIENT args for older versions.

Action items

References

  1. [1] Consistent provider key resolution in provider options ↗ laravel/ai
  2. [2] v1.59.0 ↗ laravel/sail
  3. [3] Backport 8.5 Dockerfile to 8.4, 8.3, 8.2, 8.1 and 8.0 ↗ laravel/sail
  4. [4] Pin GitHub Actions to commit SHAs and add Dependabot config ↗ laravel/ai
  5. [5] Pin GitHub Actions to commit SHAs and add Dependabot config ↗ laravel/agent-skills
  6. [6] Pin GitHub Actions to commit SHAs and add Dependabot config ↗ laravel/boost
  7. [7] Pin GitHub Actions to commit SHAs and add Dependabot config ↗ laravel/agent-detector
  8. [8] Reject blank or non-string embeddings inputs ↗ laravel/ai
  9. [9] Respect configured database connection in Conversation and ConversationMessage models ↗ laravel/ai

FAQ

What changed in Laravel on May 14, 2026?
Laravel's AI package just patched a consistency bug in provider option resolution that was forcing boilerplate code into every provider implementation , while Sail v1.59.0 rolled out unified Dockerfile improvements across five PHP versions in one shot .
What should Laravel teams do about it?
Upgrade Laravel Sail to v1.59.0 if you're running PHP 8.0–8.4 to sync Dockerfile improvements • Update Laravel AI and check if you're using custom embeddings to validate against blank/non-string inputs • If using ai.conversations.connection config, update to the pending database connection fix when merged
Which Laravel repositories shipped on May 14, 2026?
laravel/ai, laravel/sail, laravel/agent-skills, laravel/boost, laravel/agent-detector

For your repos

The showcase is a teaser.
Your wire is the product.

Same engine. Different stack. Below: what changes when the wire is yours.

Showcase wire

  • •14 famous open source orgs
  • •One wire per day
  • •Public, generic
  • •Read on the web, when you remember

Your wire

  • →Up to 1,500 of your repos - orgs, deps, vendors
  • →Morning and evening briefs
  • →Action items routed to your team
  • →Slack delivery, email, breaking-news CVE alerts

Want a hands-on demo first? Ask a current user for an invite link.