Product Decisions This Supports

Framework upgrade planning: v1.2.0 adds Laravel 13 support, so teams planning or currently on Laravel 13 can keep this package in scope without forking or delaying upgrades.
Build vs. buy / adopt vs. maintain: The release shows active maintenance — nightly CI, PHPStan cleanup, and dependency bumps — which lowers the risk of adopting the package instead of building identity-resolution logic in-house.
Deprecation management: The updated deprecation warning for identity resolvers is a signal to audit current usage and avoid starting new work on that API. It does not indicate a removal in this release, but it should enter the roadmap as a migration watch item.
Roadmap priority: This is a maintenance/compatibility release. There are no new user-facing features, so it should not pull priority from feature roadmap work; treat it as an upgrade enabler.

When to Consider This Package

Consider it if you need the package’s identity-resolution capabilities and are on Laravel 13, or plan to upgrade soon. The release explicitly keeps the package compatible with the newer framework version.
Consider it if maintenance health matters to your team: regular CI runs, static analysis fixes, and dependency updates are good signals for a package you expect to keep in production.
Look elsewhere or pause if your product depends heavily on identity resolvers and you cannot absorb a deprecation/migration cycle. The warning update is not a breaking change, but it is a clear signal to plan.
Look elsewhere if you need new features or user-facing capabilities in the near term; v1.2.0 is compatibility and housekeeping only.
Evaluate carefully if you require vendor-backed long-term support or an SLA. This release improves maintainability but does not change the support model.

Executives: This is a low-risk maintenance release. It keeps the package compatible with Laravel 13 and shows healthy maintenance, with no new cost or breaking changes indicated. The identity-resolver deprecation is a watch item, not an immediate blocker.
Engineering: The upgrade is primarily a compatibility and tooling release. Run the test suite, confirm Laravel 13 compatibility, and audit any identity-resolver usage so migration work can be scoped separately.
Product: There are no new user-facing features in v1.2.0. Use this as a compatibility checkpoint, not a feature milestone, and keep identity-resolver migration on the technical-debt radar.
Overall: Adopt or retain the package for Laravel 13 projects where its identity-resolution functionality fits. Treat the deprecation warning as a planning input, not a reason to block current work.