Subject of the issue

When invalidating a token, an amount of minutes is calculated to specify how much the token should stay in the Blacklist
The problem is in the way it's calculated seems wrong, at least in my case it was wrong it just needs to be turned to positive before returning, and also for some reason the "diffInRealMinutes" Carbon method is used, I didn't find it anywhere in Carbon's actual Doc

Your environment

Steps to reproduce

Try logging in with the login, and then using the refresh route

Expected behavior

Here the token from login should be invalidated by default
So you should expect a new entry in the cache table in the database (if all the configurations are exactly as the defaults of Laravel 11.x)

Actual behavior

No entry is introduced, and the token is still valid (you can actually perform many consecutive calls to refresh with the same token)