Connections For Laravel Laravel Package

Product Decisions This Supports

• Supports build-vs-buy decisions for Laravel packages that expose configurable/swappable models: the 1.1.2 patch confirms factory support follows host-configured models, reducing the need for custom test scaffolding in downstream apps.
• Informs roadmap and extensibility bets: if product requirements include host apps replacing package models, this release lowers integration risk and improves confidence in package-level factories as a supported workflow.
• Helps prioritize upgrade work: 1.1.2 is a patch-level correctness fix, not a breaking or feature release, so adoption can be scoped as a low-risk maintenance upgrade for teams already relying on model swaps.
• Guides QA/test strategy: teams can rely on package factories to build the configured model in tests, rather than maintaining app-specific factory overrides for swapped models.

When to Consider This Package

• Consider it when building or adopting a Laravel/PHP package where domain models are intentionally swappable by the host application and factories are expected to work against the configured model.
• Adopt or upgrade to 1.1.2 if your application swaps the package’s model and uses package factories in tests; this release directly addresses a correctness gap in that workflow.
• Look elsewhere if the product does not need model swapping, if factories are not part of the integration contract, or if the package’s extension model is too opinionated for your architecture.
• Treat this as a maintenance-grade release: it strengthens test reliability and host-app compatibility, but it is not a reason alone to adopt the package if broader feature, maturity, or support criteria are unmet.

How to Pitch It (Stakeholders)

This patch release improves reliability for Laravel applications that customize the package by swapping its underlying model. Factories now build the configured model, which means downstream teams can trust package-provided test factories instead of writing custom workarounds. For executives, it signals active maintenance and lower integration risk in extensible deployments. For engineering, it is a low-risk patch upgrade with direct value for test suites and host-app compatibility, especially where model swapping is part of the product contract.