[5.4] Do not touch the user timestamps when updating the remember_token. #17135
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
As discussed with @taylorotwell
It makes no sense to touch the
updated_at
field of the user when hisremember_token
is set or updated.Note:
\Illuminate\Foundation\Auth\ResetsPasswords::resetPassword
: the password is modified too, soupdated_at
should be modified too.Also see #16660 (comment)