migrations_lockfile.txt

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.

discover: 0003_discover_json_field

explore: 0006_add_changed_reason_field_explore

feedback: 0001_squashed_0004_index_together

flags: 0001_squashed_0004_add_flag_audit_log_provider_column

hybridcloud: 0023_correct_webhook_payload_constraint

insights: 0002_backfill_team_starred

monitors: 0008_fix_processing_error_keys

nodestore: 0001_squashed_0002_nodestore_no_dictfield

notifications: 0002_notificationmessage_jsonfield

preprod: 0014_commitcomparisons_fk

replays: 0006_add_bulk_delete_job

sentry: 0967_large_tables_legacy_json_field

social_auth: 0003_social_auth_json_field

tempest: 0001_squashed_0002_make_message_type_nullable

uptime: 0043_uptime_django_json_field

workflow_engine: 0083_add_status_to_action