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: 0016_add_control_cacheversion

nodestore: 0002_nodestore_no_dictfield

remote_subscriptions: 0003_drop_remote_subscription

replays: 0004_index_together

sentry: 0793_remove_db_constraint_alert_rule_exclusion

social_auth: 0002_default_auto_field

uptime: 0018_add_trace_sampling_field_to_uptime

workflow_engine: 0014_model_additions_for_milestones