Routing Auto Bundle Laravel Package

Product Decisions This Supports

• Platform currency / upgrade planning: 2.1.0 is a compatibility release, not a feature release. Its only substantive content is (a) Symfony 4 support and (b) a raised floor — PHP 5.6 and 7.0 dropped, Symfony 3.0–3.2 dropped. That makes it a direct input to the "when do we move the app to Symfony 4 / PHP 7.1+" decision, and to the sequencing of that work against other roadmap items.
• Dependency policy (build vs. buy): A dependency that tracks upstream framework majors on a current cadence is cheaper to keep than a fork or an in-house reimplementation. This release is evidence for retain, provided we are willing to move our own runtime forward.
• Support-matrix and SLA commitments: The release narrows the supported environment. If we publish a support matrix (PHP versions, framework versions) to internal teams or customers, it needs updating in the same window as the upgrade.
• Version-pinning and release-window decisions: The PM-relevant action is not "adopt the feature" — there is no feature — it is "choose the upgrade window and the constraint bump." Decisions: pin to 2.0.x and defer, or bump the floor and align the whole stack now.
• Not supported by this release: any user-facing capability, performance, or UX decision. Treat 2.1.0 as infrastructure hygiene and keep it out of feature-level roadmap discussions.

When to Consider This Package

Consider adopting/upgrading when:

• The application is already on PHP 7.1+ and either on Symfony 4 or scheduled to move there — 2.1.0 is the version that supports that target.
• You want the package to stay on a maintained upstream branch so security and bug fixes keep flowing without patching.
• You are starting greenfield on a current Laravel/Symfony stack; there is no reason to start on the pre-2.1 line.

Look elsewhere or defer when:

• You are still running PHP 5.6 or 7.0, or Symfony 3.0–3.2. This is a breaking change at the constraint level — 2.1.0 will not install, and there is no compatibility shim. Stay on 2.0.x until the runtime moves, and treat that date as a tracked risk (end-of-life PHP is a security exposure, not just an inconvenience).
• You need a supported path for legacy environments for an extended period; this package has explicitly chosen not to provide one.
• You require LTS-style guarantees on older framework majors — the release history here shows a fast-follow cadence behind Symfony majors, which is good for currency and bad for long tails.

Caveat for the reviewer: the 2.1.0 notes are terse and give no feature or bugfix content. The exact new Symfony floor (presumably 3.3+) is not stated and should be confirmed from composer.json before committing to a support matrix.

How to Pitch It (Stakeholders)

For executives (one paragraph): This is a maintenance release with no new customer-facing features. Its value is defensive: it keeps the package on a currently supported PHP and Symfony base, which reduces security and unpatched-dependency exposure and avoids a fork later. The cost is a bounded engineering task — bumping our minimum PHP and framework versions — not a product initiative. The only real risk is that the upgrade is a hard break for any environment still on PHP 5.6/7.0 or Symfony 3.0–3.2, so it must be scheduled with the platform upgrade rather than dropped in.

For engineering (the actionable framing): 2.1.0 removes PHP 5.6 and 7.0 support and Symfony 3.0–3.2 support, and adds Symfony 4. Treat it as breaking: check composer.json constraints, confirm the actual new floor, add PHP 7.1+ and Symfony 4 to the CI matrix, and coordinate the constraint bump with the framework upgrade so we do not strand environments mid-flight. Recommend a single coordinated upgrade ticket rather than an opportunistic composer update.