Events

Each lifecycle transition dispatches an event from RoundlyConsulting\Posts\Events carrying the post’s id as public readonly int|string $postId:

use Illuminate\Support\Facades\Cache;
use Illuminate\Support\Facades\Event;
use RoundlyConsulting\Posts\Events\PostPublished;

Event::listen(PostPublished::class, fn (PostPublished $e) => Cache::forget("post:{$e->postId}"));

Events fire only when the status actually changes — every schedule() fires PostScheduled, since it always moves the date — so a repeated call or a racing publishDue() run never fires one twice.

The package itself listens to PostPublished (to warm media variants) and to reports’ ReportResolved and ReportThresholdReached (to auto-unpublish). Creating a post as Published or Scheduled fires PostPublished or PostScheduled as well.