v2.5.0

What's Changed

• fix: fail a haystack whose next bale can no longer be unserialized by @viicslen in #2
• Laravel 13 upgrade by @viicslen in #3

New Contributors

• @viicslen made their first contribution in #2

Full Changelog: v2.3.0...v2.5.0

v2.4.0

Laravel 13 support.

• allow illuminate/* ^13.0
• allow laravel/serializable-closure ^2.0 alongside ^1.2

laravel/framework v13 requires laravel/serializable-closure ^2.0.10, while this package pinned ^1.2. That single conflict made Haystack uninstallable alongside Laravel 13.

SerializableClosure's public API is unchanged between v1 and v2, so no source changes were needed. Verified by running the suite against both: 128 passed / 12 failed on each, an identical result. The 12 pre-existing failures are assertions comparing Closure object identity plus a testbench PostgresBuilder::setConnection incompatibility, neither related to this change.

Also widens the orchestra/testbench and pestphp/pest dev constraints so the suite is installable on current Laravel versions.

v2.3.0

Full Changelog: https://github.com/FmTod/laravel-haystack/commits/v2.3.0