Merge branch 'master' into lcian/feat/rust-logs

Author: lcian

.vscode/settings.json

@@ -14,6 +14,8 @@
     "**/src/wizard/**": true
   },
   "cSpell.words": [
-    "laravel"
+    "laravel",
+    "subprocessor",
+    "subprocessors"
   ]
 }

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.10.1",
+    "@sentry/nextjs": "9.27.0",
     "@spotlightjs/spotlight": "^2.1.1",
     "next": "15.2.3",
     "next-auth": "^4.24.5",
@@ -68,4 +68,4 @@
     "@types/react": "npm:[email protected]",
     "@types/react-dom": "npm:[email protected]"
   }
-}
+}

develop-docs/development-infrastructure/testing.mdx

@@ -363,10 +363,10 @@ See the [Frontend Handbook](/frontend/#testing) for more Jest testing tips.
 
 ```shell
 # Run jest in interactive mode
-yarn test
+pnpm test
 
 # Run a single test
-yarn test tests/js/spec/views/issueList/overview.spec.js
+pnpm test tests/js/spec/views/issueList/overview.spec.js
 ```
 
 ### API Fixtures

develop-docs/self-hosted/index.mdx

@@ -17,7 +17,7 @@ The difference only resides on a few things that are impossible to be hosted by
 - Pricing tiers & Billing system.
 - [Spike protection](https://docs.sentry.io/pricing/quotas/spike-protection/), as it is tightly coupled with Billing Quotas.
 - [Spend Allocation](https://docs.sentry.io/pricing/quotas/spend-allocation/), as it is tightly coupled with Billing Quotas.
-- AI & ML features (such as autofix), although the code is open at [getsentry/seer](https://github.com/getsentry/seer).
+- Seer and other AI & ML features, although the code is open at [getsentry/seer](https://github.com/getsentry/seer).
 - [Data Storage Location](https://docs.sentry.io/organization/data-storage-location/), because you own your data.
 - [iOS Symbolication](https://docs.sentry.io/platforms/apple/data-management/debug-files/symbol-servers#built-in-repositories), because Apple does not provide a public symbol server, nor do they allow us to distribute the Debug Information Files (DIFs) ourselves.
 

docs/contributing/environment.mdx

@@ -43,7 +43,7 @@ You will now be able to access docs via http://localhost:3000.
 
 A few linters are available. Run `yarn lint` to apply them all.
 
-Some lints can be autofixed with eslint
+Some lints can be auto-fixed with eslint
 
 ```bash
 yarn lint:eslint:fix

docs/platforms/apple/common/index.mdx

@@ -311,6 +311,31 @@ func applicationDidFinishLaunching() {
 ```
 </PlatformSection>
 
+<PlatformSection supported={[ "apple.macos"]}>
+
+## Uncaught NSExceptions
+
+On macOS, the Sentry Apple SDK can't capture uncaught exceptions out of the box, therefore we recommend enabling `enableUncaughtNSExceptionReporting` in your `SentryOptions`. Alternatively, you can use the `SentryCrashExceptionApplication` class. Please visit <PlatformLink to="/usage/#capturing-uncaught-exceptions">capturing uncaught exceptions</PlatformLink> for more information.
+
+```swift {tabTitle:Swift}
+import Sentry
+
+SentrySDK.start { options in
+    options.dsn = "___PUBLIC_DSN___"
+    options.enableUncaughtNSExceptionReporting = true
+}
+```
+```objc {tabTitle:Objective-C}
+@import Sentry;
+
+[SentrySDK startWithConfigureOptions:^(SentryOptions *options) {
+    options.dsn = @"___PUBLIC_DSN___";
+    options.enableUncaughtNSExceptionReporting = YES;
+}];
+```
+
+</PlatformSection>
+
 ## Verify
 
 Verify that your app is sending events to Sentry by adding the following snippet, which includes an intentional error. You should see the error reported in Sentry within a few minutes.
@@ -342,13 +367,6 @@ if (error) {
 }
 ```
 
-<PlatformSection supported={[ "apple.macos"]}>
-
-## Uncaught Exceptions
-
-On macOS, the Sentry Apple SDK can't capture uncaught exceptions out of the box. Please visit <PlatformLink to="/usage/#capturing-uncaught-exceptions">capturing uncaught exceptions</PlatformLink> for more information.
-
-</PlatformSection>
 
 ## Next Steps
 

docs/platforms/godot/configuration/options.mdx

@@ -127,7 +127,7 @@ Specifies the types of errors captured as breadcrumbs. Accepts a single value or
 - `MASK_SCRIPT`: Script errors will be captured.
 - `MASK_SHADER`: Shader errors will be captured.
 
-```gdscript
+```GDScript
 var mask = SentryOptions.MASK_ERROR | SentryOptions.MASK_SCRIPT
 options.logger_breadcrumb_mask = mask
 ```
@@ -138,7 +138,7 @@ options.logger_breadcrumb_mask = mask
 
 Specifies the types of errors captured as events. Accepts a single value or a bitwise combination of `GodotErrorMask` masks.
 
-```gdscript
+```GDScript
 var mask = SentryOptions.MASK_ERROR | SentryOptions.MASK_SCRIPT
 options.logger_event_mask = mask
 ```
@@ -178,7 +178,7 @@ thread-safe APIs and only use Godot-specific APIs after you've checked that you'
 
 If assigned, this callback runs before a message or error event is sent to Sentry. It takes `SentryEvent` as a parameter and returns either the same event object, with or without modifications, or `null` to skip reporting the event. You can assign it in a [configuration script](#configuration-script). This can be used, for instance, for stripping PII before sending.
 
-```gdscript
+```GDScript
 func _before_send(event: SentryEvent) -> SentryEvent:
 	if event.environment.contains("editor"):
 		# Discard event if running from the editor.
@@ -191,19 +191,15 @@ func _before_send(event: SentryEvent) -> SentryEvent:
 
 </ConfigKey>
 
-<ConfigKey name="on-crash">
+<ConfigKey name="before-capture-screenshot">
 
-If assigned, this callback runs before a crash event is sent to Sentry. In contrast to `before_send`, it is only called when a crash occurred. It takes `SentryEvent` as a parameter and returns either the same event object, with or without modifications, or `null` to skip reporting the event. You can assign it in a [configuration script](#configuration-script).
+If assigned, this callback runs before a screenshot is captured. It takes `SentryEvent` as a parameter and returns `false` to skip capturing the screenshot, or `true` to capture the screenshot.
 
-```gdscript
-func _on_crash(event: SentryEvent) -> SentryEvent:
-	if event.environment.contains("editor"):
-		# Discard event if running from the editor.
-		return null
-	if event.message.contains("Bruno"):
-		# Remove sensitive information from the event.
-		event.message = event.message.replace("Bruno", "REDACTED")
-	return event
+```GDScript
+func _before_capture_screenshot(event: SentryEvent) -> bool:
+	if is_showing_sensitive_info():
+		return false # Don't capture screenshot!
+	return true
 ```
 
 </ConfigKey>

docs/platforms/godot/configuration/stack-traces.mdx

@@ -214,7 +214,7 @@ For more information, refer to [Sentry CLI](/cli/) documentation.
 You can also upload debug files for the Sentry SDK itself by running the following command from your project directory:
 
 ```bash {tabTitle:Bash/PowerShell}
-sentry-cli debug-files upload --org ___ORG_SLUG___ --project ___PROJECT_SLUG___ addons/sentrysdk/
+sentry-cli debug-files upload --org ___ORG_SLUG___ --project ___PROJECT_SLUG___ addons/sentry/
 ```
 
 This uploads the SDK's debug files to Sentry. You can repeat this step for any other native extension used in your Godot project.

docs/platforms/javascript/common/configuration/integrations/vercelai.mdx

@@ -46,7 +46,44 @@ To enhance the spans collected by this integration, we recommend providing a `fu
 ```javascript
 const result = await generateText({
   model: openai("gpt-4-turbo"),
-  experimental_telemetry: { functionId: "my-awesome-function" },
+  experimental_telemetry: {
+    isEnabled: true,
+    functionId: "my-awesome-function",
+  },
+});
+```
+
+## Options
+
+### `recordInputs`
+
+Requires SDK version `9.27.0` or higher.
+
+_Type: `boolean`_
+
+Records inputs to the `ai` function call.
+
+Defaults to `true` if `sendDefaultPii` is `true` or if you explicitly set `experimental_telemetry.isEnabled` to `true` in your `ai` function callsites.
+
+```javascript
+Sentry.init({
+  integrations: [Sentry.vercelAIIntegration({ recordInputs: true })],
+});
+```
+
+### `recordOutputs`
+
+Requires SDK version `9.27.0` or higher.
+
+_Type: `boolean`_
+
+Records outputs to the `ai` function call.
+
+Defaults to `true` if `sendDefaultPii` is `true` or if you explicitly set `experimental_telemetry.isEnabled` to `true` in your `ai` function callsites.
+
+```javascript
+Sentry.init({
+  integrations: [Sentry.vercelAIIntegration({ recordOutputs: true })],
 });
 ```
 
@@ -61,7 +98,7 @@ const result = await generateText({
 });
 ```
 
-If you want to collect inputs and outputs for a specific call, you must specifically opt-in to each function call by setting `experimental_telemetry.recordInputs` and `experimental_telemetry.recordOutputs` to `true`.
+If you set `experimental_telemetry.recordInputs` and `experimental_telemetry.recordOutputs` it will override the default behavior of collecting inputs and outputs for that function call.
 
 ```javascript
 const result = await generateText({

docs/platforms/javascript/common/index.mdx

@@ -47,7 +47,7 @@ Select which Sentry features you'd like to install in addition to Error Monitori
 <PlatformCategorySection notSupported={["server"]}>
   <PlatformSection notSupported={["javascript", "javascript.cordova"]}>
     <OnboardingOptionButtons
-      options={["error-monitoring", "performance", "session-replay"]}
+      options={["error-monitoring", "performance", "session-replay", "user-feedback"]}
     />
   </PlatformSection>
 </PlatformCategorySection>
@@ -78,7 +78,7 @@ Select which Sentry features you'd like to install in addition to Error Monitori
 
 <PlatformSection notSupported={["javascript.nextjs"]}>
 
-Sentry captures data by using an SDK within your application’s runtime.
+Sentry captures data by using an SDK within your application's runtime.
 
 </PlatformSection>