Who contributed to Laravel on July 19, 2026?

3 developers shipped this update, including pushpak1300, amjosuesanchez, and Wilsen Hernández.

What were the notable Laravel updates?

Store conversation participants polymorphically, Add human-in-the-loop, and Add summarize macro for text summarization.

@laravel

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

github ↗

Pick a date

Topics: PHP Full archive →

The Wire · Showcase

LARAVEL AI PLUGS CONVERSATION LEAK, ADDS HUMAN APPROVAL GATES

By RepoJournal · Filed 06:55 UTC on July 19, 2026 · About Laravel

3 people shipped this

pushpak1300 @pushpak1300 4 cited

amjosuesanchez @amjosuesanchez 1 cited

Wilsen Hernández @wilsenhc 1 cited

A critical polymorphic participant fix stops conversation history from bleeding between models that share IDs, while new human-in-the-loop tooling lets agents pause before side effects hit production.

In brief

Laravel AI now stores conversation participants polymorphically. stops the accidental data bleed when the same chat model runs in multiple contexts. took long enough.
Human-in-the-loop approval gates landed in Laravel AI. meaning you can gate AI decisions behind actual humans before they ship. regulatory teams will sleep better.
Laravel AI adds a summarize macro for text summarization. one-liner instead of rolling your own prompt engineering. saves tokens and reads cleaner.
Bedrock support now handles cross-account AssumeRole. multi-account AWS setups just got easier to wire into Laravel AI. fewer credential headaches.

Laravel AI shipped a security fix [1] that rescopes conversations by both participant type and ID, following Sanctum's tokenable pattern. The vulnerability: if your app runs multiple auth providers (User #1 and Admin #1), they'd collide on the same conversation history. This is now gated behind an opt-in discriminator for backward compatibility. In the same release cycle, the framework added human-in-the-loop approval gates [2] that pause agents before executing tools with external side effects, exposing pending calls for human review across prompt, stream, and queue modes. Roster merged its 1.x branch into main [5], consolidating development tracks. The AI team also shipped a text summarization macro [3] that cuts boilerplate (just call `str($article)->summarize()` instead of spinning up an agent each time), plus Bedrock cross-account AssumeRole support [4] for teams invoking models from different AWS accounts. Package skeleton picked up CLI compatibility flags [6] to play nicer with automated tooling.

Action items

→ If you handle multi-provider auth with AI conversations, enable the participant_type discriminator immediately to prevent history leaks laravel/ai [immediate]
→ Review human-in-the-loop approval pattern for any agent tooling touching external systems or databases laravel/ai [plan]
→ Audit active Bedrock integrations and evaluate cross-account AssumeRole for multi-account setups laravel/ai [monitor]

References

[1] Store conversation participants polymorphically ↗ laravel/ai
[2] Add human-in-the-loop ↗ laravel/ai
[3] Add summarize macro for text summarization ↗ laravel/ai
[4] Bedrock: support cross-account AssumeRole credential provider ↗ laravel/ai
[5] Sync 1.x into main ↗ laravel/roster
[6] Adds --no-ansi and --quiet options for compatibility ↗ laravel/package-skeleton

Quick answers

What shipped in Laravel on July 19, 2026?: A critical polymorphic participant fix stops conversation history from bleeding between models that share IDs, while new human-in-the-loop tooling lets agents pause before side effects hit production. In total, 6 commits and 6 pull requests landed.
Who contributed to Laravel on July 19, 2026?: 3 developers shipped this update, including pushpak1300, amjosuesanchez, and Wilsen Hernández.
What were the notable Laravel updates?: Store conversation participants polymorphically, Add human-in-the-loop, and Add summarize macro for text summarization.

LARAVEL AI BREAKS OPEN EMBEDDINGS FOR IMAGES, VIDEO, AND DOCUMENTS

The SDK you've been reaching around just got multimodal: Gemini and Voyage embeddings now accept file attachments alongside text, closing the gap between what providers support and what Laravel lets you build.

php 14 shipped 1-min read

@laravel 2 days ago

LARAVEL 13 TIGHTENS VALIDATION AND IMAGE EXPORTS WHILE PACKAGE SKELETON GETS HARDENED FOR CI

Laravel's core shipped four validation and image format additions overnight while fixing the configure script that was crashing on non-interactive runs.

php 35 shipped 1-min read

@laravel 3 days ago

Laravel AI Ships Rector Cleanup, Framework Tightens Test Infrastructure

Laravel AI 0.9.1 landed with Rector automation to modernize syntax across the stack, while the framework continues stripping redundant timezone handling from its test suite.

php 17 shipped 1-min read

@laravel 4 days ago

LARAVEL AI FIXES STREAMING CORRUPTION AS BOOST ADDS AGENT FLEXIBILITY

Multi-step AI streams were mangling persisted messages mid-sentence, but Laravel AI just plugged the leak with two critical fixes that restore conversation integrity.

php 11 shipped 1-min read

— or follow the whole beat:

Elsewhere on the wire

@cachyos about 10 hours ago

CACHYOS LINUX 7.1.4 SHIPS WITH SCHEDULER REVERT AND AMD AUDIO FIXES

The kernel bumped to 7.1.4 overnight with a critical scheduler revert and targeted audio driver fixes for AMD systems.

infra 57 shipped 1-min read

Elixir & Phoenix about 10 hours ago

ECTO FIXES SILENT DATA CORRUPTION IN MAP UPDATES AND BELONGS_TO LOOKUPS

Two critical Ecto bugs that silently corrupt changeset data are now fixed, and you should merge these immediately if you're using map or association updates.

elixir 10 shipped 1-min read

Mobile platforms about 10 hours ago

SWIFT COMPILER DROPS DECADE-OLD INTEROP WORKAROUND, REIMPLEMENTS CORE OPTIMIZER IN PURE SWIFT

Swift's ClangImporter finally stopped stripping type aliases that have been unnecessary since 2014, while the compiler's foundational SSAUpdater moved entirely off C++ dependencies.

mobile 28 shipped 1-min read

@dotnet about 10 hours ago

SOURCE.DOT.NET PROXY LAYER BROKEN, SOURCEBROWSER GETS MAJOR OVERHAUL

source.dot.net is serving HTTP 500s and stale assets because the proxy layer exposes bugs that local-disk deployments never catch, and SourceBrowser just got a significant upgrade that's likely its last.

dotnet 12 shipped 1-min read