Laravel Modules Forum Laravel Package

Product Decisions This Supports

• Platform modernization timing: v2.0.0 is a compatibility/maintenance release, not a feature release. It forces a clear decision: adopt Laravel 13 + PHP 8.4 now, defer the package upgrade, or fork/pin to the prior line if the product is still on Laravel 12/PHP 8.3.
• Build vs. buy for community/discussion features: The package covers boards, threads, post counters, search ranking, soft-delete/restore drift handling, read caching, and ACL/policy reads. That supports buying/maintaining forum primitives rather than building them in-house where the product needs standard discussion surfaces.
• Admin/UI roadmap: Filament 3, 4, and 5 remain supported, reducing risk around Filament upgrades and avoiding a forced admin-panel migration just to take this package version.
• Upgrade sequencing: Because Laravel 12 and PHP 8.3 are dropped, this release is a gating dependency for any roadmap item that requires Laravel 13 or PHP 8.4. PM should sequence this with broader platform upgrades rather than treat it as an isolated package bump.
• Performance/security tradeoff acceptance: Board and thread read caching are unchanged; ACL/policy reads remain deliberately uncached. That is a product-relevant stance: favor authorization freshness over cache hit rate for permission checks. Confirm this matches the product’s risk tolerance for high-traffic forums.
• Regression confidence: The release reports 145 passing tests / 461 assertions, PHPStan level 8 clean, and explicit coverage for post-count semantics across soft delete and restore. That supports accepting the upgrade with normal QA rather than a deep behavioral re-review.

When to Consider This Package

Consider adoption when:

• The product needs Laravel-native boards/threads/discussion primitives with moderation, soft deletes, search, and read caching.
• The platform is already on, or is actively planning to move to, PHP 8.4 and Laravel 13.
• The team uses Filament 3, 4, or 5 for admin surfaces and wants a package that explicitly supports all three.
• You value a maintained dependency with a CI matrix, static analysis, and regression tests over a bespoke forum implementation.
• You can accept the package’s authorization-read stance: ACL/policy reads are uncached by design, which is safer but may require capacity planning for very high-read community workloads.

Look elsewhere or defer when:

• The product is committed to Laravel 12 or PHP 8.3 in the near term. v2.0.0 is a hard break; staying on v1.x or selecting another package is the practical path.
• You need deep, product-specific forum behavior that the package does not expose, or you require fine-grained caching of authorization decisions at scale.
• The product does not use Filament and you want to avoid pulling in admin-panel compatibility surface area.
• You need new feature velocity from this dependency. v2.0.0 is primarily baseline modernization and SQL-safety hardening, not a feature expansion.

How to Pitch It (Stakeholders)

Executive summary: v2.0.0 is a maintenance and platform-compatibility release for the Laravel forum/modules package. It adds support for Laravel 13 and PHP 8.4, keeps Filament 3/4/5 compatibility, and hardens three SQL construction points by removing runtime string splicing. The tradeoff is explicit: it drops Laravel 12 and PHP 8.3. If we are on the older baseline, this is not a drop-in upgrade; it is a platform-upgrade dependency.

For engineering: The release rewrites ThreadObserver::deleted()/restored() and created() to use decrement()/increment()/incrementEach() instead of SQL string concatenation, and removes a getTable() qualifier from Thread::scopeSearch()’s ranking CASE. Counter semantics are unchanged and covered by ThreadDeletionDriftTest. Board/thread read caching is untouched; ACL/policy reads remain intentionally uncached. CI covers PHP 8.4 × Laravel 13 × Filament 3/4/5, with 145 tests / 461 assertions passing and PHPStan level 8 clean. Validate dependency constraints (ozankurt/laravel-modules-core ^2.0, ozankurt/laravel-modules-interactions ^2.0, spatie/laravel-package-tools ^1.93, cviebrock/eloquent-sluggable ^12.0 || ^13.0) against our lockfile before scheduling the bump.

Recommendation: Treat v2.0.0 as a go only if the Laravel 13/PHP 8.4 upgrade is already on the near-term roadmap. Otherwise, pin to the prior supported line and revisit when the platform baseline moves.