chore(feedback) remove field

Author: jerryzhou196

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_feedback_remove_fk
 
 flags: 0001_squashed_0004_add_flag_audit_log_provider_column
 

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

@@ -0,0 +1,32 @@
+# Generated by Django 5.2.1 on 2025-09-12 15:54
+
+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 = [
+        ("feedback", "0005_feedback_fk_not_db_contstr"),
+    ]
+
+    operations = [
+        migrations.RemoveField(
+            model_name="feedback",
+            name="environment",
+        ),
+    ]

src/sentry/feedback/models.py

@@ -4,7 +4,6 @@
 from sentry.backup.scopes import RelocationScope
 from sentry.db.models import BoundedBigIntegerField, Model, region_silo_model, sane_repr
 from sentry.db.models.fields import UUIDField
-from sentry.db.models.fields.foreignkey import FlexibleForeignKey
 
 
 @region_silo_model
@@ -18,7 +17,6 @@ class Feedback(Model):
     feedback_id = UUIDField(unique=True)
     date_added = models.DateTimeField(default=timezone.now)
     organization_id = BoundedBigIntegerField(db_index=True)
-    environment = FlexibleForeignKey("sentry.Environment", null=True, db_constraint=False)
 
     # This "data" field is the data coming from the Sentry event and includes things like contexts
     # As we develop the product more, we will add more specific columns and rely on this JSON field less and less