Resque Laravel Package

Product Decisions This Supports

• Platform upgrade sequencing (PHP 8 baseline). The 5.0.3 release line is effectively "PHP 8 only," which converts this dependency into a hard gate on your runtime modernization. This is the input for deciding when the PHP 8 migration becomes mandatory rather than optional, and for sequencing it against other packages that still pin PHP 7.x.
• Security/compliance posture for background workers. Authentication support in StartWorkerCommand means worker processes can now connect to password-protected Redis. This directly unblocks the decision to run against managed Redis (AWS ElastiCache with AUTH, Azure Cache, GCP Memorystore with AUTH) instead of self-managed, unauthenticated instances — a common audit finding.
• Build vs. buy on queue infrastructure. Confirms this package remains a viable "buy/adopt" option for teams already standardized on the Resque job model and Ruby-Resque interoperability, rather than rebuilding job processing in-house.
• Roadmap gating for feature work. Any feature that depends on long-running worker fleets (bulk imports, report generation, webhook fan-out, media transcoding) can now be planned against a worker runtime that meets infra security requirements.
• Risk register / technical debt prioritization. The PHP 8-only stance is a forcing function: it either removes a legacy-support burden or blocks teams still on 7.4. PMs should treat it as a tracked upgrade item with an owner and a date, not a passive dependency bump.

When to Consider This Package

Adopt when:

• You are already on PHP 8.0+ across all environments (dev, CI, staging, prod) and have no near-term need to support 7.4.
• Your Redis instances require AUTH (managed cloud Redis, security-hardened clusters, SOC 2 / ISO-style controls) — the StartWorkerCommand auth addition is the specific capability that makes this workable.
• You need Resque-compatible job semantics, including interoperability with existing Ruby Resque producers/consumers or an inherited job payload format.
• You have, or are willing to build, your own operational tooling for worker supervision, retries, and visibility.

Look elsewhere when:

• You are greenfield on Laravel and have no Resque legacy. Laravel's native queue system with Horizon gives you a first-party dashboard, metrics, balancing strategies, and tagging — meaningfully less operational surface for a PM to own.
• You still must support PHP 7.4 in any environment. Pinning this release line will block you; stay on the prior branch and treat the upgrade as a scheduled project.
• You need out-of-the-box observability, autoscaling, or per-queue SLAs without custom instrumentation.
• Your team has no Redis operational experience — Resque-style polling workers are more infra-sensitive than a managed queue (SQS, Cloud Tasks) and will surface as on-call load.

Caveat on this release: the notes are terse. "PHP8only branch" reads as a branch/line designation rather than a clean semantic-version breaking-change announcement. Before committing to 5.0.3, confirm (a) the actual minimum PHP version, (b) whether the auth change is opt-in via config or alters existing connection behavior, and (c) whether 5.x is a rename of the branch or a published stable tag. That verification is a half-day engineering spike, not a planning assumption.

How to Pitch It (Stakeholders)

To executives: This release hardens our background job processing in two ways. First, it moves the package onto a PHP 8-only baseline, which aligns us with a supported, patched PHP runtime and reduces long-term maintenance and security-patch exposure. Second, it adds authentication support to worker processes, letting us run job workers against password-protected managed Redis — closing a control gap that typically appears in security reviews. Neither change adds user-facing features; both reduce operational and compliance risk. The main cost is a coordinated PHP 8 upgrade if any environment is still on 7.4, which we should scope before committing.

To engineering: Two changes of substance. (1) The 5.x line is PHP 8 only — verify our CI images, local dev containers, and any deploy targets are all 8.0+ before bumping, and check whether we have transitive constraints holding us back. (2) StartWorkerCommand now supports Redis authentication, so workers can connect to AUTH-protected instances; confirm whether this is opt-in config or a behavioral change to existing connections, and update our secrets management and worker startup configs accordingly. Also validate the tag is a published stable release rather than a branch head before we pin it. Recommend a spike plus a staged rollout to a non-production worker fleet first.