Prism Laravel Package

Product Decisions This Supports

• Adopt/upgrade decision: v0.133.1 is a compatibility-repair release. It restores Prism\Prism\Streaming\StreamCollector, which v0.132.0 removed without notice, and reports no breaking changes. Teams already using Prism streaming should treat v0.133.1 as the safe target release rather than staying on or moving to v0.132.0.
• Build vs. buy for streaming orchestration: The package provides a maintained streaming collection abstraction, but the deprecation of StreamCollector in favour of StreamedMessages::fromEvents() means PMs should plan for a migration path rather than treating the current class as a permanent API.
• Roadmap and migration planning: New work should target StreamedMessages::fromEvents(). Existing consumers of StreamCollector can continue on v0.133.1 but should schedule migration work before a future removal.
• Dependency-risk management: The v0.132.0 incident shows that a routine composer update can break consumers when public classes are removed in minor releases. PMs should require version pinning, upgrade testing, and release-note review for products that depend on Prism streaming.
• Feature scope and use cases: This supports products that need LLM streaming with step-level events and replay metadata, including chat interfaces, agent harnesses, and applications that reconstruct streamed messages from events.
• Vendor/package evaluation: The quick restore and consumer testing are positive maintenance signals, but the silent removal is a release-process warning. PMs should weigh responsiveness against the need for stable public APIs.

When to Consider This Package

Consider this package when:

• You are building Laravel/PHP products that need streamed LLM responses and want an existing abstraction instead of maintaining your own stream collector.
• You already depend on Prism streaming and need v0.133.1 to restore compatibility after v0.132.0.
• You can tolerate a pre-1.0 dependency with evolving APIs and are willing to track deprecations and migration work.
• You can pin versions and test composer update changes before production rollout.
• You need step-aware streamed messages with replay metadata and can adopt StreamedMessages::fromEvents() for new code.

Look elsewhere or defer adoption when:

• You require strict semantic-versioning guarantees and cannot absorb minor-release API churn.
• You need long-term support commitments or vendor SLAs around public API stability.
• You do not need streaming LLM functionality and would otherwise add dependency surface for no product value.
• Your team cannot allocate migration work away from deprecated APIs such as StreamCollector.
• A silent removal in a prior minor release is unacceptable for your risk profile, even though v0.133.1 restores the class.

How to Pitch It (Stakeholders)

For executives: This release fixes a compatibility break in Prism’s streaming API. v0.132.0 removed a public class without notice; v0.133.1 restores it with the same signatures and no breaking changes. The package remains usable for streaming LLM features, but it carries pre-1.0 dependency risk, so we should pin versions and budget a small migration to the recommended replacement API.

For engineering: Upgrade to v0.133.1 to unblock streaming consumers affected by the missing StreamCollector. Existing code can keep using StreamCollector for now, but it is deprecated in favour of StreamedMessages::fromEvents(), which follows the current stream shape and preserves per-step replay metadata. New code should use StreamedMessages::fromEvents(). Add a regression test around streaming collection and pin the Prism version so future minor releases cannot silently break production.