Extensions Laravel Package

Product Decisions This Supports

• Framework upgrade planning. 2.0.3 adds Laravel v13 compatibility. This is the release that unblocks a Laravel 13 upgrade for any product depending on laravel-doctrine/extensions — treat it as a prerequisite dependency bump on the platform-upgrade roadmap, not as a feature.
• Build vs. buy on persistence plumbing. The package supplies the Laravel service-provider/config wiring plus a curated set of Doctrine behavioral extensions (timestamps, blameable/audit, soft deletes, sluggable, tree/nested-set, translatable). Buying this off the shelf avoids maintaining in-house event subscribers and listeners that reimplement the same behavior.
• Architecture decision: Eloquent vs. Doctrine. Its presence in the stack implies a deliberate choice to run Doctrine ORM inside Laravel alongside (or instead of) Eloquent. Roadmap items that depend on rich domain modeling, unit-of-work semantics, or mapping to a legacy schema should be scoped with this in mind.
• Feature use cases it directly enables. Audit trails and "who changed what" (timestampable/blameable), reversible deletes on Doctrine entities (softdeleteable), CMS/marketing content localization (translatable), category and org-hierarchy navigation (tree), and SEO-stable URLs (sluggable) — all without bespoke per-entity code.
• Dependency-risk tracking. A patch release that only widens a framework constraint is a positive maintenance signal: the package is being kept current with Laravel majors. Re-assess if a future Laravel major ships without a corresponding release here.

When to Consider This Package

Adopt when:

• You already use laravel-doctrine/orm (or are committed to Doctrine) and need the standard behavioral extensions plus their Laravel wiring; this package is the natural companion rather than a standalone choice.
• The domain model is complex enough to justify the Data Mapper pattern — many related entities, non-trivial invariants, or an existing relational schema you cannot reshape into Eloquent conventions.
• You need two or more of the bundled behaviors. Pulling the package for a single behavior is hard to justify versus a small custom subscriber.
• You are on, or planning, Laravel 13 and need a version that declares support for it — 2.0.3 is the minimum viable pin for that upgrade.

Look elsewhere when:

• The product is a conventional CRUD application. Eloquent plus a couple of model observers delivers most of this with a smaller conceptual footprint and a much larger hiring pool.
• The team has no Doctrine experience. The onboarding cost of entity mapping, the unit of work, and DQL is real and rarely appears in an initial estimate.
• You need one narrow behavior (e.g. soft deletes only). A focused, in-repo implementation is cheaper to own than a transitive dependency chain.
• You require vendor-backed SLAs or commercial support — this is community-maintained OSS, and version support tracks volunteer effort.
• You depend on extension behaviors this package does not ship, or on Doctrine features gated behind a different major line; check the pinned Doctrine ORM version before committing.

How to Pitch It (Stakeholders)

For executives (one paragraph): This is a routine maintenance release of an open-source library our Laravel applications use for database persistence and audit/history behavior. Version 2.0.3 adds support for Laravel 13. There are no new features, no licensing or cost impact, and no action required unless and until we schedule the Laravel 13 upgrade — at which point this release is what makes that upgrade possible. Risk is low, and the release is a positive signal that the library is actively maintained.

For engineering leads (detail): 2.0.3 is a patch-level change whose only content is the Laravel v13 compatibility update (PR #89). No public API changes, no deprecations, no configuration or migration steps to perform for teams staying on Laravel 12 and below. Practical implications: (1) bump the constraint in the same PR as the framework upgrade, not ahead of it; (2) confirm the whole dependency graph — laravel-doctrine/orm, auth, migrations, softdeletes — also supports Laravel 13, since this package alone will not get you there; (3) run the full suite plus a smoke test of extension configuration, as behavioral extensions often fail at runtime rather than at install; (4) pin the exact patch version in composer.lock and let routine dependency automation handle future patches.

Recommendation: Keep and upgrade. Adopt 2.0.3 as the standard pin for the Laravel 13 upgrade ticket; no change to current architecture or vendor strategy.