I have seen below note in Django 3.2 release notes. This relevant commit updated making hash value algorithm based on user and timestamp. It now includes user email as well compared to previous version:
Previously (v3.1) it was:
return str(user.pk) + user.password + str(login_timestamp) + str(timestamp)
So I am worrying that upgrading from Django 3.1 to 3.2 will break my existing password reset tokens. It’s weird that this incompatibility is not mentioned in 3.2 release notes. Or maybe I am wrong about assuming this change incompatible?