Enumaton Laravel Package

Product Decisions This Supports

• Framework upgrade planning (primary signal): v2.1.0 adds Laravel 12 support and refreshes PHP version constraints. For a PM, the practical takeaway is that this dependency is not a blocker in a Laravel 11 → 12 upgrade. Confirm the new PHP floor (Laravel 12 requires PHP 8.2) against your hosting/runtime baseline before scheduling the upgrade.
• Build vs. buy: Enums are native to PHP 8.1+; this package is thin convenience tooling, not core domain logic. Adoption cost is low and reversibility is high — the "buy" case is really "avoid writing per-enum boilerplate for validation rules, option lists, and labels."
• Scope and consistency decisions: When enums are user-facing (form selects, API validation, display labels), a single convention for rendering and validating them prevents each squad from inventing its own helper. This is a standards decision as much as a library decision.
• Roadmap hygiene / dependency risk register: Maintenance-only release with a single contributor. Log it as a low-severity, non-zero risk item; a supported framework version reduces that risk but doesn't eliminate single-maintainer exposure.
• Feature feasibility: Because the package is small and stable, adding enum-backed filters, exports, or admin dropdowns carries little delivery risk — useful when estimating enum-adjacent stories.

When to Consider This Package

Consider it when:

• You are on Laravel 10, 11, or 12 with PHP 8.2+ (the supported band after this release) and use backed enums in more than a couple of places.
• You want validation rules, select options, and human-readable labels derived from enums without duplicating that logic per enum.
• You value a small, low-ceremony dependency over a larger enum/state-machine framework.

Look elsewhere or defer when:

• You are pinned to PHP 8.1 or Laravel 9 and below — this release likely raises the minimum runtime and may leave you on an older, unsupported line.
• You need database-level enum migration management, state transitions/workflows, or a rich cast/attribute system — that's a different category of tool.
• Your procurement or platform standards require active multi-maintainer support, security policy, or a formal LTS commitment.
• Enums appear in only one or two places — hand-rolled helpers may be cheaper than a dependency.

How to Pitch It (Stakeholders)

To executives: This is a small, free utility dependency, and its latest release confirms compatibility with Laravel 12. That removes a potential blocker from our framework upgrade path and lets us delete bespoke enum-handling code from a handful of features. Risk is limited to single-maintainer exposure, which we mitigate by pinning the version and keeping usage shallow.

To engineering: v2.1.0 is a maintenance release — Laravel 12 support plus updated PHP constraints; the changelog shows no breaking API changes. Actions: pin to ^2.1, verify our runtime meets the new PHP floor in CI and on hosting, and add a smoke test around enum validation and option rendering so a future minor bump surfaces regressions early. Treat it as convenience glue — keep domain logic framework-independent so it can be swapped out cheaply.