Queue Promises Laravel Package

Product Decisions This Supports

• Build vs. buy (renewed signal): A v1.9.0 that lands PHP 8.5 and Carbon 3 compatibility is a maintenance-health data point, not a feature. It tells you the maintainer is tracking upstream runtime and dependency changes. That is the single strongest argument for keeping this in the "buy/consume" column rather than forking or rebuilding in-house — the unglamorous compatibility work is exactly what you'd otherwise own.
• Platform upgrade planning: This release is a prerequisite artifact for any roadmap item gated on "move to PHP 8.5" or "upgrade Carbon to v3." Both are cross-cutting upgrades: they touch CI images, lockfiles, static analysis, and every transitive dependency. Having this package already green removes one line item from a long migration checklist.
• Carbon 3 migration sequencing: "Carbon 3 support fix" implies date/time behavior changes are being absorbed here. Any feature area with date math, timezone handling, billing periods, scheduling, or reporting windows should be flagged for regression testing during the Carbon 3 cutover — this is a QA scoping decision, not just an engineering one.
• Support-window / EOL compliance: If you are carrying a PHP-version support commitment (internal platform policy, customer SLAs, or a security-review requirement), forward-compat releases are the evidence you cite. Worth capturing in your dependency register so the next security questionnaire doesn't start from zero.
• Risk burn-down on the dependency portfolio: A patch-level, non-breaking compat release reduces "we're stuck on an unsupported runtime" risk without consuming roadmap capacity. Cheap risk reduction is the easiest thing to say yes to.
• Roadmap non-event: Nothing here adds user-facing capability. Do not let this crowd out feature prioritization; slot it as routine maintenance, not as a deliverable.

When to Consider This Package

• Adopt the upgrade when: you are planning or currently executing a PHP 8.5 or Carbon 3 migration and this package sits on the critical path; or you maintain a formal dependency-review cadence and want the ecosystem current before it becomes urgent.
• Adopt cautiously / verify first when: your application is still pinned to Carbon 2. Confirm whether v1.9.0 supports both Carbon 2 and 3 or has effectively moved to 3-only — the release note describes a fix, not a compatibility matrix, and that ambiguity is a blocker until resolved.
• Defer when: you are mid-freeze, or on a PHP version with years of support remaining and no Carbon 3 work planned. There is no functional pull here; deferring costs you nothing but a later catch-up.
• Look elsewhere when: the maintainer's release cadence is otherwise silent (this being an isolated compat patch rather than a pattern), the package has no stated support policy for the PHP versions you need, or the underlying capability is commoditized enough that a first-party or framework-native alternative removes a dependency entirely. Compatibility patches keep a package alive; they don't make it strategically important.
• Standing caveat: adoption criteria for the capability this package provides still need to be assessed on their own merits. This release only clears the maintenance filter, which is necessary but not sufficient.

How to Pitch It (Stakeholders)

• To executives: "A dependency we rely on shipped a maintenance release that keeps it compatible with the newest PHP runtime and the current Carbon date library. No new features, no breaking changes, no cost beyond a routine version bump. It reduces the risk of a forced, rushed upgrade later and it's a positive signal about the maintainer's responsiveness — which is the thing we actually care about when deciding whether to keep depending on third-party code."
• To engineering: "v1.9.0 adds PHP 8.5 support and fixes Carbon 3 compatibility. Treat it as a patch bump: upgrade, run the suite, and confirm two things before closing — whether Carbon 2 is still supported, and whether any date/time-sensitive tests change behavior under Carbon 3. If you're already on Carbon 2 only, tell me now so we can put that migration on the roadmap rather than discovering it during an unrelated incident."
• Framing to avoid: don't present this as a feature or a milestone. It's hygiene. The pitch is risk reduced at near-zero cost, and the honest caveat is that a compat patch is table stakes — it justifies keeping the dependency, not expanding the investment in it.