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.

ai_monitoring: 0002_add_date_updated_index

discover: 0004_discover_starred_and_last_visited

explore: 0016_update_if_syntax_on_spans

feedback: 0007_cleanup_failed_safe_deletes

flags: 0005_increase_flag_max_length

hybridcloud: 0043_add_dashboard_create_scope

insights: 0001_squashed_0002_backfill_team_starred

investigations: 0010_add_investigation_seen_and_comment

monitors: 0001_squashed_0013_delete_monitor_is_muted_field

nodestore: 0001_squashed_0002_nodestore_no_dictfield

notifications: 0013_add_notificationmessage_parent_lookup_index

preprod: 0001_squashed_0030_add_images_errored_to_snapshot_comparison

releases: 0004_cleanup_failed_safe_deletes

replays: 0001_squashed_0007_organizationmember_replay_access

seer: 0037_rename_agentic_triage_result

sentry: 1209_update_if_syntax_on_dashboard_spans

social_auth: 0001_squashed_0003_social_auth_json_field

tempest: 0001_squashed_0003_use_encrypted_char_field

uptime: 0056_encrypt_uptime_subscription_headers_body

workflow_engine: 0121_add_activation_id_to_detector_state
