chore(feedback) remove Feedback model

migrations_lockfile.txt

@@ -9,7 +9,7 @@ discover: 0003_discover_json_field
 
 explore: 0006_add_changed_reason_field_explore
 
-feedback: 0005_feedback_fk_not_db_contstr
+feedback: 0006_safe_del_feedback_model
 
 flags: 0001_squashed_0004_add_flag_audit_log_provider_column
 

src/sentry/feedback/migrations/0006_safe_del_feedback_model.py

@@ -0,0 +1,29 @@
+# Generated by Django 5.2.1 on 2025-09-12 16:33
+
+from sentry.new_migrations.migrations import CheckedMigration
+from sentry.new_migrations.monkey.models import SafeDeleteModel
+from sentry.new_migrations.monkey.state import DeletionAction
+
+
+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 = [
+        ("feedback", "0005_feedback_fk_not_db_contstr"),
+    ]
+
+    operations = [
+        SafeDeleteModel(name="feedback", deletion_action=DeletionAction.DELETE),
+    ]