HandleEntrySchedule::$minute must not be accessed before initialization

[mynetx]

Bug description

I've set up Laravel Horizon on Forge, subscribed to Nightwatch and see this as No. 1 error.

Error: Typed property Statamic\Jobs\HandleEntrySchedule::$minute must not be accessed before initialization

Statamic\Jobs\HandleEntrySchedule->entries()
Statamic\Jobs\HandleEntrySchedule->entries()
Statamic\Jobs\HandleEntrySchedule->entries()
vendor/statamic/cms/src/Jobs/HandleEntrySchedule.php:36
Statamic\Jobs\HandleEntrySchedule->handle()
vendor/statamic/cms/src/Jobs/HandleEntrySchedule.php:31
Illuminate\Container\BoundMethod::{closure:Illuminate\Container\BoundMethod::call():35})
vendor/laravel/framework/src/Illuminate/Container/BoundMethod.php:36
Illuminate\Container\Util::unwrapIfClosure()
vendor/laravel/framework/src/Illuminate/Container/Util.php:43
Illuminate\Container\BoundMethod::callBoundMethod()
vendor/laravel/framework/src/Illuminate/Container/BoundMethod.php:96
Illuminate\Container\BoundMethod::call()
vendor

How to reproduce

Nothing - just set up the scheduler.

Logs

No log entries.

Environment

Environment
Application Name: ...
Laravel Version: 12.47.0
PHP Version: 8.4.16
Composer Version: 2.9.3
Environment: production
Debug Mode: OFF
URL: ...
Maintenance Mode: OFF
Timezone: UTC
Locale: de

Cache
Config: CACHED
Events: CACHED
Routes: CACHED
Views: CACHED

Drivers
Broadcasting: log
Cache: file
Database: mysql
Logs: nightwatch
Mail: smtp
Queue: redis
Session: file

Storage
public/storage: NOT LINKED

Statamic
Addons: 1
Sites: 1
Stache Watcher: Disabled (auto)
Static Caching: half
Version: 5.72.0 Solo

Statamic Addons
statamic-rad-pack/runway: 8.9.0

Installation

Fresh statamic/statamic site via CLI

Additional details

No response

[jasonvarga]

Weird. I don't understand how that could be.

The minute property is set in the constructor. 🤔

cms/src/Jobs/HandleEntrySchedule.php

Lines 20 to 27 in c0071e4

	public function __construct()
	{
	// We want to target the PREVIOUS minute because we can be sure that any entries that
	// were scheduled for then would now be considered published. If we were targeting
	// the current minute and the entry has defined a time with seconds later in the
	// same minute, it may still be considered scheduled when it gets dispatched.
	$this->minute = now()->subMinute();
	}