Weave Code
Task Bundle Laravel Package
php-task/task-bundle
Symfony integration for php-task. Provides handler discovery, flexible task execution, management and debug commands, database persistence for tasks and executions, plus run statistics for every task execution.
Symfony integration for php-task library
Frequently asked questions about Task Bundle
- Is php-task/task-bundle a Laravel package?
- No. php-task/task-bundle is a Symfony bundle integration for the php-task library, not a first-class Laravel package. Laravel consumes Symfony components transitively, so the package may be usable as an optional console execution layer, but adoption should be treated as a Symfony-component integration. Validate Composer constraint compatibility before installing it in a Laravel application.
- How do I install php-task/task-bundle?
- Install it with Composer using composer require php-task/task-bundle. In a Symfony application you then register the bundle in the kernel according to the project documentation. In Laravel there is no bundle registration step, so you would need to evaluate console, container, and configuration wiring yourself. Check the official php-task documentation for the supported setup.
- Which Symfony versions does php-task/task-bundle support?
- Version 4.1.0 adds Symfony 8 support according to the release context. The release notes do not state whether Symfony 6.4 and 7.x support was widened alongside Symfony 8 or replaced by it. Inspect the package composer constraints and confirm the specific Symfony version your application pins. Do not assume Symfony 8 support implies backward compatibility with older ranges.
- Does php-task/task-bundle replace Laravel's scheduler?
- No. It is not Laravel scheduler integration; it provides task-definition and execution primitives layered over Symfony Console concepts. Laravel's native scheduler covers the common recurring-task case. Use TaskBundle only if its handler discovery, runner abstractions, persistence, or statistics features are genuinely needed and its dependency graph resolves cleanly.
- What features does php-task/task-bundle provide?
- It provides handler discovery, different task run possibilities, management and debug commands, database persistence for tasks and executions, and run statistics for each task execution. These features sit on top of the php-task library. The bundle is intended to integrate those task and runner abstractions into a host framework's console and kernel wiring.
- Will upgrading php-task/task-bundle from 4.0.4 to 4.1.0 require code changes?
- The context describes 4.1.0 as a minor additive compatibility release with no stated API changes. For existing 4.x consumers, the work is primarily Composer constraint resolution rather than code changes. Still run the full test suite and console-command smoke tests, and review the resolved symfony/* lockfile diff before rolling forward.
- How do I check Laravel compatibility for php-task/task-bundle?
- Build an explicit support matrix covering PHP version, Symfony constraint such as 6.4, 7.x, or 8.x, and Laravel version, then validate the exact cell you intend to run. Branch-isolate the upgrade with composer update php-task/task-bundle --with-dependencies and capture the resolved Symfony dependency tree. A conflict with versions Laravel pins blocks adoption regardless of the package's own quality.
- What are the main risks of adopting php-task/task-bundle?
- The release itself is low risk, but the dependency graph is moderate risk because it is unclear whether Symfony 8 support widened the constraints or raised the floor. Symfony 8 is early in its adoption curve, so other dependencies may not yet have compatible releases. The project also has a low bus factor, so assign an internal owner and define a fallback before adopting it.
- Is php-task/task-bundle actively maintained?
- Version 4.1.0 adds Symfony 8 support, which shows the package is tracking the current Symfony release train. However, the context describes a single-PR, single-contributor release cadence with a low bus factor. Support is community OSS with no vendor SLA, so define internal escalation paths and an operational owner.
- How should I test php-task/task-bundle in a Laravel or Symfony application?
- Update only this package with composer update php-task/task-bundle --with-dependencies on an isolated branch, then capture the resolved symfony/* tree. Run the full test suite plus console-command smoke tests and scan for deprecation notices. Roll forward only if the lockfile diff is limited to expected packages. In Laravel, also validate command registration and container wiring behavior.
Weaver
How can I help you explore Laravel packages today?