Migrations Laravel Package

Product Decisions This Supports

• Framework upgrade planning: The 3.4.4 release confirms Laravel 13 compatibility, which directly supports decisions about when (and whether) to schedule a Laravel upgrade without being blocked by Doctrine migration tooling. A PM can signal "green light" for L13 migration tracks where this package is a dependency.
• Build vs. buy: If your team is running Doctrine ORM inside a Laravel app (rather than Eloquent), this package replaces the need to hand-roll migration commands, a migrations config, and Doctrine's SchemaTool wiring. The decision is essentially "adopt this package" vs. "build a bespoke migration runner" — the latter is rarely worth it.
• Tech-debt / dependency-risk tracking: An actively maintained package with a track record of shipping framework-compatibility releases within the ecosystem's cadence is a lower-risk dependency to keep in the stack. This release is a data point for the risk column, not just a feature.
• Roadmap alignment with the Laravel ecosystem: Teams with a "stay within one major Laravel version" policy can rely on this release to keep the upgrade window open on schedule.

When to Consider This Package

Adopt it when:

• Your application uses Doctrine ORM entities (not only Eloquent) and you still want Laravel-style, versioned migration files managed via artisan.
• You need schema migrations expressed against Doctrine's metadata, keeping entity and schema definitions as the single source of truth.
• You are on or moving to Laravel 13 and the dependency must not become the long pole in the upgrade.
• Your team is comfortable with Doctrine's conventions and tooling; the learning curve is real but bounded.

Look elsewhere when:

• The app is Eloquent-only — Laravel's built-in migrations are the right tool, and adding Doctrine is unnecessary surface area.
• You require non-Laravel deployment targets or a framework-agnostic migration layer; Doctrine's own doctrine/migrations is the more direct choice.
• You need first-class support guarantees (SLA-backed vendor support) — this is a community package.
• Migrations are run by a separate ops/DBA pipeline outside the Laravel app; the artisan integration adds little.

How to Pitch It (Stakeholders)

For executives: This is a small, focused open-source component that lets our Laravel application manage database schema changes through Doctrine's proven migration engine. The 3.4.4 release adds support for Laravel 13, which keeps us current with the framework's release cadence and removes a potential blocker from our next upgrade cycle. It is low-cost, low-surface-area, and community-maintained, with no licensing or vendor commitment.

For engineering: The package bridges laravel-doctrine/orm and doctrine/migrations, exposing migrations as artisan commands backed by Doctrine's SchemaTool and version table. The 3.4.4 release is a compatibility release only — Laravel 13 support plus CI coverage — with no breaking changes, no deprecations, and no API or behavior changes. Engineers on L11/L12 can upgrade at their convenience; teams planning an L13 move should treat this release as the prerequisite that unblocks that work. Review the changelog link and confirm CI matrix coverage before adopting the bump in a production branch.

Decision ask: Approve the minor-version bump and record L13 readiness for the upcoming framework upgrade; no further evaluation needed for this release.