that's quite the breaking change @taylorotwell ?

The documentation states the second argument can be ignored (set to null) this change makes it mandatory

https://laravel.com/docs/11.x/queries#upserts

@coclav Maybe I'm missing it, but I don't see where the documentation says the second argument can be null?

@AndrewMast His colleague here. The IDE types were wrong as stated here in this PR, but I think he meant the alert box below that upsert part on the docs that have the following:

... In addition, the MariaDB and MySQL database drivers ignore the second argument of the upsert ...

We're fixing these conflicts with these patch releases over Laravel framework this way:

// Error version
Model::upsert($data, null);
Model::query()->upsert($data, null);

// Fixed version
Model::upsert($data, []); // this one version forward to DB builder so should be same as the one below
Model::query()->upsert($data, []);