Skip to content

Commit fb2b734

Browse files
chore(releases): delete new_groups column from release model (#88105)
- followup from - #88024 - #88046 - relates to #87322 - [notion doc](https://www.notion.so/sentry/Removing-new_groups-field-from-Release-model-1c28b10e4b5d801d8598dd15e7a5b215?showMoveTo=true&saveParent=true) for context & plan the `new_groups` field on the `Release` model was deprecated a long time ago: https://github.com/getsentry/sentry/blob/b88166941846ce4fdb4e2001453e421b41ba7e10/src/sentry/models/release.py#L210-L211
1 parent b114027 commit fb2b734

File tree

2 files changed

+32
-1
lines changed

2 files changed

+32
-1
lines changed

Diff for: migrations_lockfile.txt

+1-1
Original file line numberDiff line numberDiff line change
@@ -17,7 +17,7 @@ remote_subscriptions: 0003_drop_remote_subscription
1717

1818
replays: 0004_index_together
1919

20-
sentry: 0851_new_group_nullable
20+
sentry: 0852_delete_new_groups_column
2121

2222
social_auth: 0002_default_auto_field
2323

+31
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,31 @@
1+
# Generated by Django 5.1.7 on 2025-03-27 16:38
2+
3+
from sentry.new_migrations.migrations import CheckedMigration
4+
from sentry.new_migrations.monkey.fields import SafeRemoveField
5+
from sentry.new_migrations.monkey.state import DeletionAction
6+
7+
8+
class Migration(CheckedMigration):
9+
# This flag is used to mark that a migration shouldn't be automatically run in production.
10+
# This should only be used for operations where it's safe to run the migration after your
11+
# code has deployed. So this should not be used for most operations that alter the schema
12+
# of a table.
13+
# Here are some things that make sense to mark as post deployment:
14+
# - Large data migrations. Typically we want these to be run manually so that they can be
15+
# monitored and not block the deploy for a long period of time while they run.
16+
# - Adding indexes to large tables. Since this can take a long time, we'd generally prefer to
17+
# run this outside deployments so that we don't block them. Note that while adding an index
18+
# is a schema change, it's completely safe to run the operation after the code has deployed.
19+
# Once deployed, run these manually via: https://develop.sentry.dev/database-migrations/#migration-deployment
20+
21+
is_post_deployment = False
22+
23+
dependencies = [
24+
("sentry", "0851_new_group_nullable"),
25+
]
26+
27+
operations = [
28+
SafeRemoveField(
29+
model_name="release", name="new_groups", deletion_action=DeletionAction.DELETE
30+
),
31+
]

0 commit comments

Comments
 (0)