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: 0007_cleanup_failed_safe_deletes

flags: 0001_squashed_0004_add_flag_audit_log_provider_column

hybridcloud: 0027_region_cache_version_to_cell_cache_version

insights: 0002_backfill_team_starred

monitors: 0013_delete_monitor_is_muted_field

nodestore: 0001_squashed_0002_nodestore_no_dictfield

notifications: 0004_notificationmessage_group_action_date_added_idx

preprod: 0027_add_distribution_state_fields

releases: 0004_cleanup_failed_safe_deletes

replays: 0007_organizationmember_replay_access

seer: 0005_delete_seerorganizationsettings

sentry: 1053_protect_projectdebugfile_file

social_auth: 0003_social_auth_json_field

tempest: 0003_use_encrypted_char_field

uptime: 0055_backfill_2xx_status_assertion

workflow_engine: 0110_owner_team_break_fk