Laravel Flowfield Laravel Package

Product Decisions This Supports

• Platform-support and upgrade planning: v1.0.1 removes a Laravel 10 blocker by replacing the unsupported Builder::afterQuery() call with a fallback using the model’s retrieved event. A PM can keep Laravel 10 in the supported matrix instead of forcing a framework upgrade solely because of this package.
• Adoption and maintenance prioritization: This is a patch release with no new product surface, breaking changes, or deprecations. It should be treated as a low-risk maintenance upgrade for teams already using the package or evaluating it for Laravel 10.
• Build-vs-buy / integration risk: The release lowers integration risk for Laravel 10 applications that need the package’s flow-field scoping behavior. It does not add capabilities that would change a build-vs-buy decision.
• Roadmap communication: Do not position this as a feature milestone. It is compatibility and release-infrastructure work: Laravel 10 support, GitHub Actions Node 24 updates, and CI dependency-resolution improvements.
• Engineering investment: The CI changes improve the package’s ability to test across supported framework versions, but they are internal quality improvements rather than customer-facing roadmap items.

When to Consider This Package

• Consider it when a Laravel application—especially Laravel 10.x—needs the package’s flow-field scoping/model behavior and you want an Eloquent-integrated implementation rather than a custom build.
• Strongly consider upgrading to v1.0.1 if you are on v1.0.0 with Laravel 10 and have encountered BadMethodCallException: Call to undefined method Builder::afterQuery().
• Validate the fallback path in your application if models rely heavily on retrieved events, since the compatibility fix uses that event when afterQuery() is unavailable.
• Look elsewhere if you need a broad feature roadmap, capabilities beyond this package’s flow-field scope, or support for framework versions not covered by its CI matrix. This release is maintenance-focused and does not signal new product investment.

How to Pitch It (Stakeholders)

Executive summary: v1.0.1 is a low-risk patch release that fixes Laravel 10 compatibility and improves CI reliability. There are no breaking changes or new features, so it does not change the product roadmap—but it reduces adoption risk for Laravel 10 teams and supports keeping the package in the supported platform matrix.

Engineering summary: Upgrade to v1.0.1 to resolve the Laravel 10 afterQuery() failure. The fallback uses the model retrieved event when needed, so regression-test models with existing retrieved listeners. CI updates for Node 24 and Composer matrix testing are internal improvements.

Product summary: Treat this as a maintenance release. It is worth including in dependency-upgrade and compatibility communications, but it is not a customer-facing feature launch or a reason to re-prioritize roadmap work.