ref(db): Migrate create_or_update to update_or_create

[vgrozdanic]

Continues the migration away from Sentry's legacy create_or_update helper toward Django's built-in update_or_create.

All three files removed from the allowlist in tests/sentry/test_no_create_or_update_usage.py.

Return values were ignored at all sites, so no caller changes are needed.

[cursor]

Cursor Bugbot has reviewed your changes and found 1 potential issue.

Bugbot Autofix prepared a fix for the issue found in the latest run.

• ✅ Fixed: No unique constraint causes MultipleObjectsReturned error
  • Added try-except blocks to catch MultipleObjectsReturned and fall back to filter().update() for backward compatibility with existing duplicate rows.

Or push these changes by commenting:

@cursor push 62de5983df

Preview (62de5983df)

diff --git a/src/sentry/tasks/assemble.py b/src/sentry/tasks/assemble.py
--- a/src/sentry/tasks/assemble.py
+++ b/src/sentry/tasks/assemble.py
@@ -426,23 +426,38 @@
 
             # If a release version is passed, we want to create the weak association between a bundle and a release.
             if self.release:
-                ReleaseArtifactBundle.objects.update_or_create(
-                    organization_id=self.organization.id,
-                    release_name=self.release,
-                    # In case no dist is provided, we will fall back to "" which is the NULL equivalent for our
-                    # tables.
-                    dist_name=self.dist or NULL_STRING,
-                    artifact_bundle=artifact_bundle,
-                    defaults=new_date_added,
-                )
+                try:
+                    ReleaseArtifactBundle.objects.update_or_create(
+                        organization_id=self.organization.id,
+                        release_name=self.release,
+                        # In case no dist is provided, we will fall back to "" which is the NULL equivalent for our
+                        # tables.
+                        dist_name=self.dist or NULL_STRING,
+                        artifact_bundle=artifact_bundle,
+                        defaults=new_date_added,
+                    )
+                except ReleaseArtifactBundle.MultipleObjectsReturned:
+                    ReleaseArtifactBundle.objects.filter(
+                        organization_id=self.organization.id,
+                        release_name=self.release,
+                        dist_name=self.dist or NULL_STRING,
+                        artifact_bundle=artifact_bundle,
+                    ).update(**new_date_added)
 
             for project_id in self.project_ids:
-                ProjectArtifactBundle.objects.update_or_create(
-                    organization_id=self.organization.id,
-                    project_id=project_id,
-                    artifact_bundle=artifact_bundle,
-                    defaults=new_date_added,
-                )
+                try:
+                    ProjectArtifactBundle.objects.update_or_create(
+                        organization_id=self.organization.id,
+                        project_id=project_id,
+                        artifact_bundle=artifact_bundle,
+                        defaults=new_date_added,
+                    )
+                except ProjectArtifactBundle.MultipleObjectsReturned:
+                    ProjectArtifactBundle.objects.filter(
+                        organization_id=self.organization.id,
+                        project_id=project_id,
+                        artifact_bundle=artifact_bundle,
+                    ).update(**new_date_added)
 
             # Instead of doing a `create_or_update` one-by-one, we will instead:
             # - Use a `bulk_create` with `ignore_conflicts` to insert new rows efficiently

_{This Bugbot Autofix run was free. To enable autofix for future PRs, go to the Cursor dashboard.}

[jjbayer]

PR description still mentions "four".