Symfony Password Exposed Bundle Laravel Package

Product Decisions This Supports

• Upgrade and support-window planning: v1.1.0 supports Symfony 8 while retaining PHP 7.4 and Symfony 4.4 compatibility, so a PM can keep one dependency across legacy and modern services instead of forking or delaying upgrades.
• Build vs. buy: Active maintenance, cross-version dependency resolution, and lowest/current regression tests reduce the case for custom integration glue around translation contracts or bundle/compiler-pass behavior.
• Roadmap sequencing: Treat this as a compatibility and maintenance release, not a feature milestone. Use it to unblock Symfony 8 readiness and dependency cleanup.
• Risk reduction: The parent bundle build-hook ordering fix and direct translation-contract dependency reduce integration failures and version-conflict risk; clarified YAML defaults reduce onboarding and support load.
• Use cases: Mixed PHP/Symfony estates, Laravel/PHP applications relying on Symfony components, packages needing translation-contract interop, and teams standardizing documented config defaults.

When to Consider This Package

• Consider it when you need Symfony bundle integration, compiler-pass behavior, or translation-contract support while maintaining broad PHP/Symfony compatibility.
• Consider it if you are preparing for Symfony 8 but cannot yet drop PHP 7.4 or Symfony 4.4 across all services.
• Consider it when you value regression coverage at both lowest and current dependency configurations.
• Look elsewhere if you need a purely Laravel-native package with no Symfony bundle semantics, require modern-PHP-only dependencies, need new product features in this release, or cannot accept the maintenance burden of broad legacy compatibility.
• Verify that the clarified YAML configuration defaults match your intended behavior before rollout.

How to Pitch It (Stakeholders)

• Executives: v1.1.0 is a low-risk maintenance release that keeps the package usable across old and new Symfony/PHP versions, reducing upgrade blockers and custom maintenance. No breaking changes or deprecations are called out.
• Engineering: It adds Symfony 8 support while retaining PHP 7.4/Symfony 4.4, fixes bundle build-hook ordering, depends directly on the translation contract for cross-version resolution, clarifies YAML defaults, adds lowest/current regression tests, and removes a stale lockfile. Adopt it as dependency hygiene and upgrade enablement, not as a feature release.