ref: move notifications models to a separate django app (#93582)

this breaks the migration cycle between sentry<=>workflow_engine

<!-- Describe your PR here. -->

Author: asottile-sentry

migrations_lockfile.txt

@@ -19,11 +19,13 @@ monitors: 0006_add_is_upserting
 
 nodestore: 0001_squashed_0002_nodestore_no_dictfield
 
+notifications: 0001_move_notifications_models
+
 preprod: 0004_add_django_jsonfield
 
 replays: 0001_squashed_0005_drop_replay_index
 
-sentry: 0927_dashboard_add_unique_constraint_user_dashboard
+sentry: 0928_move_notifications_models
 
 social_auth: 0001_squashed_0002_default_auto_field
 

src/sentry/conf/server.py

@@ -3425,20 +3425,21 @@ def custom_parameter_sort(parameter: dict) -> tuple[str, int]:
 # Specifies the list of django apps to include in the lockfile. If Falsey then include
 # all apps with migrations
 MIGRATIONS_LOCKFILE_APP_WHITELIST = (
+    "explore",
+    "feedback",
     "flags",
+    "hybridcloud",
+    "insights",
+    "monitors",
     "nodestore",
+    "notifications",
+    "preprod",
     "replays",
     "sentry",
     "social_auth",
-    "feedback",
-    "hybridcloud",
+    "tempest",
     "uptime",
     "workflow_engine",
-    "tempest",
-    "explore",
-    "insights",
-    "monitors",
-    "preprod",
 )
 # Where to write the lockfile to.
 MIGRATIONS_LOCKFILE_PATH = os.path.join(PROJECT_ROOT, os.path.pardir, os.path.pardir)

src/sentry/migrations/0928_move_notifications_models.py

@@ -0,0 +1,95 @@
+# Generated by Django 5.2.1 on 2025-06-14 16:22
+
+from django.db import migrations
+
+from sentry.new_migrations.migrations import CheckedMigration
+
+
+class Migration(CheckedMigration):
+    # This flag is used to mark that a migration shouldn't be automatically run in production.
+    # This should only be used for operations where it's safe to run the migration after your
+    # code has deployed. So this should not be used for most operations that alter the schema
+    # of a table.
+    # Here are some things that make sense to mark as post deployment:
+    # - Large data migrations. Typically we want these to be run manually so that they can be
+    #   monitored and not block the deploy for a long period of time while they run.
+    # - Adding indexes to large tables. Since this can take a long time, we'd generally prefer to
+    #   run this outside deployments so that we don't block them. Note that while adding an index
+    #   is a schema change, it's completely safe to run the operation after the code has deployed.
+    # Once deployed, run these manually via: https://develop.sentry.dev/database-migrations/#migration-deployment
+
+    is_post_deployment = False
+
+    dependencies = [
+        ("sentry", "0927_dashboard_add_unique_constraint_user_dashboard"),
+    ]
+
+    operations = [
+        migrations.SeparateDatabaseAndState(
+            state_operations=[
+                migrations.RemoveField(
+                    model_name="notificationactionproject",
+                    name="action",
+                ),
+                migrations.RemoveField(
+                    model_name="notificationactionproject",
+                    name="project",
+                ),
+                migrations.RemoveField(
+                    model_name="notificationmessage",
+                    name="action",
+                ),
+                migrations.RemoveField(
+                    model_name="notificationmessage",
+                    name="group",
+                ),
+                migrations.RemoveField(
+                    model_name="notificationmessage",
+                    name="incident",
+                ),
+                migrations.RemoveField(
+                    model_name="notificationmessage",
+                    name="parent_notification_message",
+                ),
+                migrations.RemoveField(
+                    model_name="notificationmessage",
+                    name="rule_fire_history",
+                ),
+                migrations.RemoveField(
+                    model_name="notificationmessage",
+                    name="trigger_action",
+                ),
+                migrations.AlterUniqueTogether(
+                    name="notificationsettingoption",
+                    unique_together=None,
+                ),
+                migrations.RemoveField(
+                    model_name="notificationsettingoption",
+                    name="user",
+                ),
+                migrations.AlterUniqueTogether(
+                    name="notificationsettingprovider",
+                    unique_together=None,
+                ),
+                migrations.RemoveField(
+                    model_name="notificationsettingprovider",
+                    name="user",
+                ),
+                migrations.DeleteModel(
+                    name="NotificationAction",
+                ),
+                migrations.DeleteModel(
+                    name="NotificationActionProject",
+                ),
+                migrations.DeleteModel(
+                    name="NotificationMessage",
+                ),
+                migrations.DeleteModel(
+                    name="NotificationSettingOption",
+                ),
+                migrations.DeleteModel(
+                    name="NotificationSettingProvider",
+                ),
+            ]
+        )
+    ]

src/sentry/notifications/apps.py

@@ -0,0 +1,8 @@
+from django.apps import AppConfig
+
+
+class Config(AppConfig):
+    name = "sentry.notifications"
+
+    def ready(self):
+        pass