Skip to content

feat: require pollora/hook 2.0 - #474

Merged
ogorzalka merged 2 commits into
release/v13.36.0from
feat/require-hook-2
Oct 13, 2026
Merged

ogorzalka merged 2 commits into
release/v13.36.0from
feat/require-hook-2

Conversation

@ogorzalka

Copy link
Copy Markdown
Member

Step 4 of the pollora/schedule plan, framework side. Needs pollora/hook v2.0.0 (released) and pollora/schedule v0.1.2.

  • pollora/hook ^2.0: asynchronous actions queue through the WP-Cron and Action Scheduler drivers of pollora/schedule. Async\Drivers\WpCronDriver and ActionSchedulerDriver are gone with no alias; the framework never used them. ->async(), #[Async], Async::fake(), via() and their options are unchanged, work queued by 1.x runs once the upgrade is in, and the queue driver (QueueDriver) is untouched.
  • AsyncInspector::overdueCronEvents() no longer counts the events Action Scheduler keeps: the cron option has indexed them, with a driver key, since feat: choose the scheduling driver, list and migrate scheduled events #470, so pollora:doctor would have called them overdue WP-Cron events.

use_laravel_scheduler and QueueDriver stay for step 5.

Checked on pollora-test with hook 2.0 linked: 3 messages queued under 1.4.1 run under 2.0, and with the site on Action Scheduler via('wp-cron') stays an unmarked WP-Cron event.

@ogorzalka
ogorzalka merged commit 2d5f13e into release/v13.36.0 Oct 13, 2026
10 checks passed
@ogorzalka
ogorzalka deleted the feat/require-hook-2 branch October 13, 2026 14:08
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant