Product Decisions This Supports

Establishes esplora/memento 3.0.0 as a compatibility/maintenance release: adds Laravel 10, PHP 8.2, and PHPUnit 10 support.
Supports dependency-modernization decisions: teams moving to Laravel 10 / PHP 8.2 can keep or evaluate this package without it becoming an upgrade blocker.
Does not signal new user-facing features or expanded product use cases; no roadmap priority should be created from this release alone.
For build-vs-buy: if the package capability is already needed and in use, 3.0.0 is an upgrade decision, not a reason to replace or expand. Treat the major version as a potential breaking change until engineering verifies migration impact.
For existing users: plan the upgrade as technical hygiene. For new evaluations: consider only if the application is on the supported stack and the package’s capability fits the need.

When to Consider This Package

Consider it when you already use esplora/memento, or are evaluating the capability it provides, and your application is on Laravel 10 / PHP 8.2 or planning that upgrade.
Consider 3.0.0 if alignment with PHPUnit 10 and current Laravel/PHP support matters, after maintainers or engineering confirm no unexpected breaking API changes beyond version requirements.
Look elsewhere or stay on 2.x if you are pinned to older Laravel/PHP versions and cannot upgrade.
Look elsewhere if you require a package with a strong feature roadmap, frequent releases, or detailed migration documentation; this release is compatibility-focused and does not demonstrate new product functionality.
Require engineering validation of Composer constraints, changelog details, and test coverage before adopting it as a new dependency.

Executive summary: esplora/memento 3.0.0 is a maintenance/compatibility release that keeps the dependency aligned with Laravel 10, PHP 8.2, and PHPUnit 10. It reduces upgrade friction but adds no new product features.
For engineering: treat it as a major-version dependency upgrade. Update Composer constraints, run the full test suite, review breaking changes, and schedule in a maintenance window. Confirm whether older Laravel/PHP support was dropped.
For product: no roadmap change is expected. Approve the upgrade as technical hygiene if the package is already used; do not prioritize adoption for net-new functionality based on this release alone.