Merge remote-tracking branch 'origin/master' into lforst-tanstack-start

Author: Luca Forstner

.github/CODEOWNERS

@@ -12,7 +12,7 @@
 # /src/wizard/android/ @getsentry/team-mobile-core
 # /src/platforms/apple/ @getsentry/team-mobile-core
 # /src/wizard/apple/ @getsentry/team-mobile-core
-# /src/platforms/flutter/ @getsentry/team-mobile-cross-platform
+# /src/platforms/dart/guides/flutter/ @getsentry/team-mobile-cross-platform
 # /src/wizard/flutter/ @getsentry/team-mobile-cross-platform
 # /src/platforms/dart/ @getsentry/team-mobile-cross-platform
 # /src/wizard/dart/ @getsentry/team-mobile-cross-platform

.github/ISSUE_TEMPLATE/issue-content-01-sdks.yml

@@ -1,6 +1,7 @@
-name: "📝 SDK Documentation"
-labels: ["Type: Content", "SDKs"]
+name: '📝 SDK Documentation'
+labels: ['Type: Content', 'SDKs']
 description: Missing, incorrect, or unclear documentation of SDKs.
+type: Improvement
 body:
   - type: markdown
     attributes:

.github/ISSUE_TEMPLATE/issue-content-02-product.yml

@@ -1,6 +1,7 @@
-name: "📝 Product Documentation"
-labels: ["Type: Content", "Product"]
+name: '📝 Product Documentation'
+labels: ['Type: Content', 'Product']
 description: Missing, incorrect, or unclear documentation of product features.
+type: Improvement
 body:
   - type: markdown
     attributes:

.github/ISSUE_TEMPLATE/issue-content-03-develop.yml

@@ -1,6 +1,7 @@
-name: "📝 Documentation on develop.sentry.dev"
-labels: ["Type: Content", "Develop"]
+name: '📝 Documentation on develop.sentry.dev'
+labels: ['Type: Content', 'Develop']
 description: Missing, incorrect, or unclear developer documentation.
+type: Improvement
 body:
   - type: markdown
     attributes:
@@ -35,4 +36,3 @@ body:
       value: |-
         ## Thanks 🙏
         Check our [triage docs](https://open.sentry.io/triage/) for what to expect next.
-  

.github/ISSUE_TEMPLATE/issue-platform-404.yml

@@ -1,7 +1,7 @@
-name: "💻 Docs Platform: 🔗 404 Error"
-labels: "Type: Platform,404"
+name: '💻 Docs Platform: 🔗 404 Error'
+labels: 'Type: Platform,404'
 description: Broken links, missing pages, and other 404 errors.
-
+type: Bug
 body:
   - type: textarea
     id: url

.github/ISSUE_TEMPLATE/issue-platform-bug.yml

@@ -1,5 +1,6 @@
-name: "💻 Docs Platform: 🐞 Bug"
-labels: "Type: Platform,Bug"
+name: '💻 Docs Platform: 🐞 Bug'
+labels: 'Type: Platform'
+type: Bug
 description: Problems with the technical platform of our docs.
 body:
   - type: textarea

.github/ISSUE_TEMPLATE/issue-platform-improvement.yml

@@ -1,6 +1,7 @@
-name: "💻 Docs Platform: ✨ Improvement"
-labels: "Type: Platform,Improvement"
+name: '💻 Docs Platform: ✨ Improvement'
+labels: 'Type: Platform'
 description: Ideas on how we can improve the technical capabilities of our docs platform.
+type: Improvement
 body:
   - type: textarea
     id: problem

apps/changelog/package.json

@@ -25,7 +25,7 @@
     "@radix-ui/react-icons": "^1.3.2",
     "@radix-ui/react-toolbar": "^1.1.0",
     "@radix-ui/themes": "^3.1.3",
-    "@sentry/nextjs": "9.2.0",
+    "@sentry/nextjs": "9.3.0",
     "@spotlightjs/spotlight": "^2.1.1",
     "next": "15.1.2",
     "next-auth": "^4.24.5",

develop-docs/application-architecture/feedback-architecture.mdx

@@ -93,9 +93,8 @@ In Relay v24.5.1, we migrated feedback to its own kafka topic + consumer,
 
 ### Attachments
 
-We only use attachments for the widget’s screenshot feature, which allows users
-to submit **at most 1 screenshot per feedback**. Attachments are another [item type](/sdk/data-model/envelopes/#attachment)
-in an envelope.
+Attachments are another [item type](/sdk/data-model/envelopes/#attachment)
+in an envelope. We use attachments for the widget’s screenshot feature.
 
 - SDK v8.0.0+, Relay v24.5.1+: Sends the feedback and attachment items in the same envelope.
 - SDK < v8, all Relay versions: Sends a separate envelope for each item.

develop-docs/sdk/data-model/event-payloads/exception.mdx

@@ -111,6 +111,14 @@ the root exception (the last to be listed in the exception values).
 
 : An optional flag indicating that this exception is part of an exception group type specific to the platform or language.
 
+`source`
+
+: An optional string value describing the source of the exception. The SDK should populate this with the name of the property or attribute of the parent exception that this exception was acquired from. In the case of an array, it should include the zero-based array index as well.
+
+- Python Examples: `"__context__"`, `"__cause__"`, `"exceptions[0]"`, `"exceptions[1]"`
+- .NET Examples: `"InnerException"`, `"InnerExceptions[0]"`, `"InnerExceptions[1]"`
+- JavaScript Examples: `"cause"`, `"errors[0]"`, `"errors[1]"`
+
 `meta`
 
 : Optional information from the operating system or runtime on the exception