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.

explore: 0002_add_starred_explore_query_model

feedback: 0004_index_together

hybridcloud: 0019_add_provider_webhook_payload

nodestore: 0002_nodestore_no_dictfield

remote_subscriptions: 0003_drop_remote_subscription

replays: 0004_index_together

sentry: 0863_update_organization_member_invite_model

social_auth: 0002_default_auto_field

tempest: 0002_make_message_type_nullable

uptime: 0031_translate_uptime_object_headers_to_lists_take_three

workflow_engine: 0042_workflow_fire_history_add_fired_actions_bool