Django migrations lock file. This helps us avoid migration conflicts on master.
If you have a conflict in this file, it means that someone has committed a migration
ahead of you.

To resolve this, rebase against latest master and regenerate your migration. This file
will then be regenerated, and you should be able to merge without conflicts.

feedback: 0004_index_together
hybridcloud: 0014_apitokenreplica_add_hashed_token
nodestore: 0002_nodestore_no_dictfield
replays: 0004_index_together
sentry: 0674_monitor_clear_missed_timeout_as_error
social_auth: 0002_default_auto_field