I am against this change.

There are many applications who clear the cache in between deployments using cache:clear

As far as I understand it, this will also purge the password reset tokens.

(Or am I misunderstanding how the cache driver works in this case?)

you are correct with the default case. which is why I noted in the original PR that I highly recommend creating a dedicated cache "store" so you aren't clearing these.

I'm definitely open to creating an explicit "store" by default, but I was not sure what "driver" we would pick for that.

I think creating a different store (not exactly sure what that would imply) would be unneeded complexity for most of the Laravel Apps.

You currently only need one sqlite file for creating a new App (cache is also stored in the database). So no need for further complexity if a simple database table is enough for most use cases in my opinion.

I think the store property addresses this concern and the only real argument against using it (which is far more superior) is "we have to educate people on the new changes" and that's flaky at best.

I don't think we should do this.