Primer Core Laravel Package

Product Decisions This Supports

• Framework upgrade roadmap (Laravel 10 → 11): v5.2.0 adds illuminate/collections v11 support, which removes the last compatibility blocker for teams standardising on Laravel 11. This is the primary decision this release informs — whether the Laravel 11 migration can proceed without forking or replacing the package.
• Build vs. buy for foundational scaffolding: Primer Core supplies shared base classes/primitives (providers, view models/components and similar glue) that would otherwise be hand-rolled per project. The decision is whether to standardise on it across a portfolio of apps or absorb ~a few hundred lines of glue into an internal package.
• Dependency hygiene / upgrade budget: A release whose only change is raising a framework constraint signals a thin, low-maintenance dependency. Budget accordingly — little ongoing cost, but also little differentiation, and no guarantee of feature investment.
• Convention standardisation: If your team already uses Rareloop-style conventions, adopting the package reduces divergence between projects and shortens onboarding; if not, it adds a vocabulary your engineers must learn for modest gain.
• Vendor risk register: Single new contributor, version-numbered against Laravel majors, no feature work in this release — a candidate for "acceptable but have an exit plan" classification rather than a strategic dependency.
• Not supported by this release: no new end-user features, no deprecations, no breaking changes. It should not be used to justify roadmap commitments or marketing claims about capability.

When to Consider This Package

Consider it when:

• You are on (or moving to) Laravel 11 and need illuminate/collections v11 compatibility — v5.2.0 is the minimum version that clears this.
• You want a small, unobtrusive set of base classes to standardise service providers, view models/components and similar boilerplate across multiple Laravel applications.
• Your team is comfortable reading and, if necessary, vendoring a compact package — the surface area is small enough that forking is a realistic fallback.
• The package's conventions already match or closely resemble your house style.

Look elsewhere (or build in-house) when:

• You need substantial functionality — this is glue, not a framework or feature library.
• You require a vendor with published support SLAs, predictable release cadence, or multiple maintainers; the changelog shows a small contributor base and long gaps between releases.
• You are pinned to an older Laravel major and cannot take v5.x, or you need backwards compatibility guarantees across majors.
• Your architecture already has an established internal base-class layer; introducing a second one creates duplication for no functional return.
• You are evaluating it for a greenfield product where framework-native primitives (service providers, Blade components, view models via community packages) already cover the need.

Adoption gate for this release specifically: pin ^5.2 in composer.json, confirm no transitive constraint conflicts on illuminate/collections, and verify your Laravel 11 test suite passes before treating the upgrade as complete.

How to Pitch It (Stakeholders)

For executives: This is a maintenance release for a small internal-style dependency. It adds Laravel 11 compatibility and nothing else — no new features, no breaking changes, no licensing or cost impact. The practical outcome is that it unblocks (or de-risks) our Laravel 11 upgrade path for any services using it. It is not a strategic investment; treat it as plumbing that is now current.

For engineering: Bump to v5.2.0 to gain illuminate/collections v11 support. There are no API changes to absorb, so the upgrade is a version constraint change plus a regression run. Keep in mind the package is lightly maintained and versioned against Laravel majors — if it stalls on a future major, the sensible play is to vendor the code rather than wait. Worth a short note in the dependency log: acceptable to depend on, but not something to build architecture around.