Steem Laravel Package

Product Decisions This Supports

• Runtime upgrade planning: v4.1.0 adds PHP 8 support, which unblocks teams standardizing on PHP 8.x. This directly informs the "can we upgrade the platform this quarter?" decision — the package is no longer a blocker.
• Build vs. buy: With a stable 4.x line now spanning modern PHP runtimes, the maintenance burden of an in-house equivalent is harder to justify. Leaning toward buy/adopt keeps engineering focused on differentiated work.
• Feature/roadmap scope: A compatibility-only release signals the maintainers are investing in longevity rather than surface area. Plan roadmap work assuming the package's feature set is stable, not expanding.
• Use cases: Safe to include in new Laravel services targeting PHP 8, including greenfield work and services scheduled for runtime upgrades. Also reasonable to standardize on a single major version (4.x) across the fleet rather than maintaining mixed versions.

When to Consider This Package

Adopt when:

• Your target runtime is PHP 8.x and you want a maintained package rather than a pinned legacy version.
• You need a dependency that is actively tracking upstream PHP/Laravel support rather than one frozen at an older major.
• You are consolidating multiple Laravel services onto a common package version and want a release that spans both older and current PHP runtimes during the transition.

Look elsewhere or pause when:

• You are still on PHP 7.x and cannot upgrade — confirm the 4.x line's minimum PHP version before adopting, since 4.1.0's PHP 8 support does not by itself guarantee 7.x remains supported.
• You require documented behavioral or feature changes to justify the upgrade; this release is compatibility-oriented, so there is no functional incentive to migrate mid-cycle.
• You depend on transitive packages that have not yet declared PHP 8 compatibility — the constraint must be satisfied across the whole dependency graph, not just this package.
• You need a published support/EOL matrix. The release notes are terse; verify the maintainer's stated support window and backward-compatibility policy (semver on a minor bump implies no breaking changes, but confirm) before making it a long-term platform dependency.

How to Pitch It (Stakeholders)

For executives: Version 4.1.0 is a low-risk compatibility release that adds PHP 8 support. In practical terms it removes a dependency-level blocker to our PHP 8 upgrade, which is the main gating item for the runtime modernization work. There is no new functionality and no indication of breaking changes — it is a "keep the lights on and stay current" release.

For engineering: Treat 4.1.0 as the version to target for any PHP 8 environment. It is a minor version, so semver implies drop-in compatibility with 4.0.x; still, run the test suite and a dependency resolution check (composer why-not php 8.x) before rolling it across services, since transitive constraints are the usual failure point. Confirm whether 7.x remains supported within the 4.x line if you have services that cannot upgrade yet, and pin explicitly rather than floating if you need a stable target during the transition. Recommend adopting now and standardizing on 4.x fleet-wide.