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: 0002_feedback_add_org_id_and_rename_event_id nodestore: 0002_nodestore_no_dictfield replays: 0003_add_size_to_recording_segment sentry: 0571_add_hybrid_cloud_foreign_key_to_slug_reservation social_auth: 0002_default_auto_field hybridcloud: 0002_add_slug_reservation_replica_model