Update Sentry configuration and dependencies to resolve type conflicts

Author: cursoragent

apps/changelog/package.json

@@ -68,6 +68,7 @@
   "resolutions": {
     "@types/react": "npm:[email protected]",
     "@types/react-dom": "npm:[email protected]",
-    "@sentry/core": "9.27.0"
+    "@sentry/core": "9.27.0",
+    "@sentry/types": "9.27.0"
   }
 }

package.json

@@ -138,7 +138,8 @@
   "resolutions": {
     "dompurify": "3.2.4",
     "@types/dompurify": "3.0.5",
-    "@sentry/core": "9.27.0"
+    "@sentry/core": "9.27.0",
+    "@sentry/types": "9.27.0"
   },
   "volta": {
     "node": "20.11.0",

src/instrumentation-client.ts

@@ -16,19 +16,13 @@ Sentry.init({
   // in development and sample at a lower rate in production
   replaysSessionSampleRate: 0.1,
 
-  // You can remove this option if you're not planning to use the Sentry Session Replay feature:
+  // Simplified integrations to avoid type conflicts
   integrations: [
     Sentry.replayIntegration({
       // Additional Replay configuration goes in here, for example:
       maskAllText: false,
       blockAllMedia: false,
     }),
-    Sentry.thirdPartyErrorFilterIntegration({
-      filterKeys: ['sentry-docs'],
-      behaviour: 'apply-tag-if-contains-third-party-frames',
-    }),
-    // Use the correct integration function for v9.27.0
-    Sentry.browserTracingIntegration(),
   ],
 });