Turbo Toast Bundle Laravel Package

Product Decisions This Supports

• Framework upgrade sequencing (PHP 8.4 / Symfony UX 3). v0.4.0 removes a hard install blocker for teams already on Symfony UX 3. If your roadmap includes a PHP 8.4 + UX 3 upgrade, this package no longer has to be swapped out or forked to get there — the constraint is widened, nothing else changed.
• Build vs. buy for notification UX. A Turbo-native toast layer is a small but non-trivial piece of frontend plumbing (Stimulus controller, Turbo Stream wiring, flash integration). Adopting a maintained bundle keeps that out of your own backlog and off your on-call surface.
• Dependency-risk scoring for the release. This is a compatibility-only release: no public API, config key, template, or Stimulus identifier changed. That makes it a low-risk bump you can schedule inside a normal maintenance window rather than a dedicated migration epic.
• Timing the upgrade against your PHP baseline. UX 3 requires PHP >= 8.4. On PHP 8.3, Composer will keep resolving UX 2, so this release is a no-op for you until the PHP upgrade lands. Use it as a signal that the package is tracking the ecosystem, not as a trigger to move PHP early.
• Vendor-confidence check. The release adds explicit dual-major CI coverage (both UX majors pinned and verified per cell, UX 3 tested from 3.0.0 to latest). That is evidence of maintained compatibility rather than an untested constraint bump — useful input if you maintain an approved-dependencies list.

When to Consider This Package

Consider it when:

• You are on Symfony with Turbo/Hotwire (symfony/ux-turbo) and want toast-style notifications without hand-rolling the Stimulus/Turbo Stream glue.
• Your application is already on, or planning, Symfony UX 3 and PHP 8.4 — v0.4.0 is specifically what unblocks installation there.
• You are on PHP 8.3 / UX 2 and want a low-commitment option that will not force an early PHP upgrade; the bundle resolves to UX 2 and does not pull UX 3 in on its own.
• You value a stable public surface — this release changes none, so adoption cost stays predictable.

Look elsewhere when:

• You are on Laravel or a non-Turbo frontend — this is a Symfony UX bundle and the toast layer assumes Turbo/Stimulus. A Laravel app would need a Livewire/Inertia-native equivalent, and that is a separate build-vs-buy call.
• You need a rich notification platform (email/SMS/push channels, templating, delivery tracking). This is a UI-level toast integration, not a notification service.
• You are not yet on PHP 8.4 but must be on UX 3 immediately — that combination is not resolvable here; the PHP upgrade is the prerequisite, not the package.
• You require guaranteed long-term support commitments or a formal deprecation policy; nothing in this release speaks to that.

How to Pitch It (Stakeholders)

For executives: This is a maintenance release for a small frontend notification component. It adds compatibility with the newest Symfony UX major (UX 3) and changes no application-facing behavior. Net effect: one fewer blocker on our PHP 8.4 / Symfony upgrade path, at effectively zero migration cost. Nothing needs to be done now if we are still on PHP 8.3.

For engineering: v0.4.0 widens symfony/ux-turbo and symfony/stimulus-bundle to ^2.13 || ^3.0. No public API, configuration key, template, or Stimulus identifier changed, and the bundle does not pull UX 3 in by itself — your application's own constraints decide the major. The test matrix now pins and verifies both UX majors per cell (UX 3 from 3.0.0 to latest); note that symfony/flex does not constrain UX, so pinning has to be explicit. UX 3 requires PHP >= 8.4, so treat the PHP upgrade as the gate and this bump as the follow-on. Upgrade action: routine composer update, no code changes.