Queue Serialization w/ Carbon?

[ahinkle]

I've been investigating an issue with queue serialization in Laravel and I'm trying to determine if it's a Laravel bug or truly how Laravel implements queue deserialization.

Laravel 11.34.2
PHP 8.3

In my console scheduler, I have:

// Console.php
Schedule::job(MyJobClass::class)->daily();

Now, in my job:

// MyJobClass.php
public function __construct(
    public ?Carbon $date = null,
) {
    // dd($date); is a new carbon object?
}

When the job is scheduled via the console, $date is a new Carbon instance of today, However, if I fire the job manually (sync or non-console with no arguments), the expected null is passed.

It seems something in the job deserialization process during scheduling is instantiating a new Carbon object. I moved the logic to the handle() method as a workaround, but I'm curious—what quirks in queue serialization might be causing this?