Pomm Bundle Laravel Package

Product Decisions This Supports

• Upgrade planning and platform roadmap: The 3.0.0 release is a hard modernization gate. It adds support for Symfony 5 while dropping PHP 5 and Symfony 2, so any team on legacy PHP or Symfony 2 must either stay pinned to the 2.x line or fund a runtime upgrade. This directly informs whether the next platform-refresh milestone is a nice-to-have or a blocker for staying on a supported dependency.
• Build vs. buy / maintain vs. adopt: A package actively tracking Symfony 5 and dropping EOL runtimes is signaling that it is maintained and aligned with the current ecosystem. That lowers the "will this be abandoned under us?" risk that typically pushes a team toward building in-house.
• Feature scope and integration work: If your product depends on the functionality this package provides (framework-version compatibility, shared abstractions, or runtime utilities), 3.0.0 is the version that unblocks a Symfony 5 / modern-PHP migration. Roadmap the upgrade work as part of that migration, not as a standalone line item.
• Support matrix and customer commitments: Dropping PHP 5 and Symfony 2 narrows the environments you can credibly support. Use this to update stated minimum requirements, deprecation notices, and any SLA language tied to legacy platforms.
• Dependency hygiene / security posture: Removing EOL PHP 5 support reduces exposure to unpatched-runtime vulnerabilities and lets you stop arguing about unsupported versions in security reviews.

When to Consider This Package

Consider adopting (or upgrading to 3.0.0) when:

• You are on, or committed to, PHP 7+ and a currently-supported Symfony line (5.x, or 4.x where still supported). The package's support window now matches a modern stack.
• You are planning a platform modernization and want dependencies that migrate with you rather than block you.
• Your product or a key internal service depends on the functionality the package provides, and you value upstream maintenance over bespoke code you'd have to own.
• You are already on 2.x and can absorb a breaking-change upgrade in the same cycle as your PHP/Symfony bump.

Look elsewhere (or defer) when:

• You are still on PHP 5 or Symfony 2. 3.0.0 is not for you; you are on a frozen 2.x branch with no forward path unless you upgrade the runtime. Treat that as a strategic decision, not a dependency bump.
• You need a vendor to support legacy environments for contractual reasons — this release makes clear that's not a supported position.
• Your Laravel-only stack has no Symfony-coupled dependency surface and the package's functionality is already covered natively or by a first-party module.
• The upgrade cost for 3.0.0 exceeds what you'd save versus the in-house or alternative implementation, especially if you use only a small slice of the package.

How to Pitch It (Stakeholders)

For executives: We depend on a package that just released a major version. The short version is that it is modernizing — it now supports current Symfony and has dropped PHP 5 and Symfony 2, both of which are long past end-of-life. That is a good signal about the maintainer's direction, but it is a breaking change: teams on older runtimes cannot simply upgrade and will need to either fund a platform upgrade or accept staying on the older 2.x line. The decision to make is whether the runtime modernization is already on our roadmap — if it is, this upgrade rides along with it; if it is not, we should schedule it, because staying on EOL PHP is a growing security and supportability risk.

For engineering: 3.0.0 adds Symfony 5 support and removes PHP 5 and Symfony 2. Plan the upgrade as part of the same workstream as the PHP/Symfony bump, not separately — the constraints are the same. Audit our dependency tree for anything else still pinning PHP 5 or Symfony 2; this package may be the first of several. Verify our test matrix and CI images cover the new minimums before merging. Where we are on 2.x and cannot move yet, pin explicitly and document the date we intend to exit, so we do not drift onto an unsupported branch by accident.