Nav Bundle Laravel Package

Product Decisions This Supports

• Upgrade sequencing / roadmap pacing. v2.0.0 raises the platform floor to PHP 8+ and Symfony ^6.0. That is a roadmap decision, not a library decision: you either budget the PHP/Symfony modernization now (and gain a supported dependency tree with security backports) or pin to ^1.0 and accept that you are on a maintenance-only branch.
• Integration surface reduction (feature scope). Dropping easycorp/easyadmin-bundle and sensio/framework-extra-bundle removes two batteries-included integrations. Product question to answer: does your back-office rely on EasyAdmin, and does your routing rely on annotation/@Route conventions? If yes, you now own that glue or you migrate to EasyAdmin 4 + native attributes.
• Build vs. buy. The package got narrower and more focused in v2 — smaller dependency graph, fewer version-coupling hazards, but also less out-of-the-box value. Worth re-scoring against an in-house implementation if your usage was mostly the EasyAdmin integration.
• Use cases in scope. PHP 8 typed codebases on Symfony 6; admin/CRUD back-offices; teams standardizing on attributes over annotations.
• Maintenance/risk signal. The non-BC items (phpunit → symfony/phpunit-bridge, CS and PHPStan fixes, deprecation cleanup) read as an actively maintained project, which is usually the strongest single input into a "keep vs. replace" decision.

When to Consider This Package

Adopt when:

• You are already on, or are committed to, PHP 8 + Symfony 6.
• You do not depend on EasyAdmin (any version) or on sensio/framework-extra-bundle features such as annotation-based routing/config.
• You want a small, focused dependency rather than a framework-within-a-framework.
• Ongoing maintenance matters (this release is a reasonable proxy that it does).

Look elsewhere / stay on v1.x when:

• You are still on Symfony 4/5 or PHP 7.x — v2.0.0 is simply not installable.
• Your admin UI is built on EasyAdmin 2/3 and migration is not funded this cycle — pin ^1.0 and put an EasyAdmin migration on the roadmap, because v1 will stop receiving fixes.
• You rely on framework-extra-bundle annotations pervasively; the migration is mechanical but touches every controller.
• You need first-class Laravel integration — this is a Symfony-ecosystem package; confirm the Laravel fit explicitly before adopting, since nothing in this release addresses that.

How to Pitch It (Stakeholders)

To executives: v2.0.0 is a maintenance-driven major release, not a feature release. The cost is a platform upgrade (PHP 8 + Symfony 6) plus some rework of admin/routing integrations; the benefit is staying on a supported, security-patched foundation with a smaller dependency footprint. The alternative — staying on v1 — is cheap this quarter and expensive within two, because v1 no longer advances.

To engineering: expect real migration work, gated on the platform upgrade. Specifically: replace annotation-based routing/config with attributes, decouple from EasyAdmin or upgrade it separately, and drop any framework-extra-bundle reliance. The test harness moves to symfony/phpunit-bridge, so CI configuration and any custom PHPUnit bootstrapping will need updating. Sequence it as: platform upgrade → dependency bump → integration rework, with a ^1.0 pin as the rollback position.