migrations default to md5 instead of sha256

[olliezyuhscripta]

noticed migrations_hash_algorithm defaults to md5 in config.py even though sha256 is available

migrations_hash_algorithm: Literal["md5", "sha256"] = "md5"

i know its just for migration file tracking not crypto, but md5 is deprecated everywhere and you already have sha256 wired up. seems like a trivial swap

also the comment says "you cannot change the hash_algorithm after migrations have already been applied once" so new users who pick the default get stuck with md5 forever

[Apoorva5544]

I've opened a PR for this: #7176

[reallyticsai]

Got it, let's address this. In our production deployments, we've seen the importance of using secure hashing algorithms like SHA-256 over MD5 for migration file tracking. MD5 is indeed deprecated, and we've had to update our systems to use SHA-256 for better security and reliability.

Here's what we can do:

• Update the migrations_hash_algorithm default to sha256.
• Add a note in the documentation to inform users that the default has been changed and that they should not rely on the old md5 default.

Additionally, we can create a migration script to handle the conversion of existing migrations from MD5 to SHA-256, ensuring that users who have already applied migrations can update their hashes without losing any data.

Would you like to proceed with this plan?