Merge branch 'master' into bot/bump-api-schema-to-0121ea4e

Author: a-hariti

app/platform-redirect/page.tsx

@@ -1,3 +1,4 @@
+import {Metadata} from 'next';
 import {redirect} from 'next/navigation';
 
 import {Alert} from 'sentry-docs/components/alert';
@@ -7,6 +8,13 @@ import {SmartLink} from 'sentry-docs/components/smartLink';
 import {extractPlatforms, getDocsRootNode, nodeForPath} from 'sentry-docs/docTree';
 import {setServerContext} from 'sentry-docs/serverContext';
 
+export const metadata: Metadata = {
+  robots: 'noindex',
+  title: 'Platform Specific Content',
+  description:
+    'The page you are looking for is customized for each platform. Select your platform below and we’ll direct you to the most specific documentation on it.',
+};
+
 export default async function Page({
   searchParams: {next = '', platform},
 }: {

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

@@ -34,6 +34,6 @@ Read more about [setting up BrowserTracing](./../../../tracing/).
 
 ```JavaScript
 Sentry.init({
-  integrations: [new Sentry.browserTracingIntegration()],
+  integrations: [Sentry.browserTracingIntegration()],
 });
 ```

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

@@ -1,8 +1,17 @@
 ---
 title: Debug
-description: "Allows you to inspect the contents of a processed event and hint object that gets passed to beforeSend or beforeSendTransaction."
+description: "Allows you to inspect the contents of a processed event and hint object that gets passed to beforeSend or beforeSendTransaction. (deprecated)"
 ---
 
+{/* TODO(v9): Remove this page and all references to it */}
+
+<Alert title="Deprecation Notice">
+
+The `Debug` Integration is deprecated and will be removed in the next major version of the SDK.
+To log outgoing events, we recommend using <PlatformLink to="/configuration/options/#hooks">Hook Options</PlatformLink> in `Sentry.init()`.
+
+</Alert>
+
 _Import name: `Sentry.debugIntegration`_
 
 This integration allows you to inspect the contents of a processed event and hint object that gets passed to `beforeSend` or `beforeSendTransaction`. It will always run as the last integration, no matter when it was registered.

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

@@ -1,8 +1,17 @@
 ---
 title: SessionTiming
-description: "Adds session timing data to events."
+description: "Adds session timing data to events. (deprecated)"
 ---
 
+{/* TODO(v9): Remove this page and all references to it */}
+
+<Alert title="Deprecation Notice">
+
+The `SessionTiming` Integration is deprecated and will be removed in the next major version of the SDK.
+To capture session durations alongside events, we recommend using <PlatformLink to="/enriching-events/context/">Context</PlatformLink>.
+
+</Alert>
+
 _Import name: `Sentry.sessionTimingIntegration`_
 
 This integration adds duration data for sessions to events.

platform-includes/debug-symbols-apple/_default.mdx

@@ -25,7 +25,13 @@ For this to work, your project settings for `DEBUG_INFORMATION_FORMAT` must be s
 
 <OrgAuthTokenNote />
 
-```bash
+You can also upload your code for source context. This feature allows Sentry to display snippets of your code next to the event stack traces.
+
+<OnboardingOptionButtons
+  options={[{ id:"source-context", checked: false }]}
+/> 
+
+```bash {"onboardingOptions": {"source-context": "2"}}
 sentry-cli debug-files upload --auth-token ___ORG_AUTH_TOKEN___ \
   --include-sources \
   --org ___ORG_SLUG___ \
@@ -44,7 +50,7 @@ Sentry can display snippets of your code next to event stack traces. This featur
 
 <OrgAuthTokenNote />
 
-```ruby {tabTitle:Current Fastlane plugin}
+```ruby {tabTitle:Current Fastlane plugin} {"onboardingOptions": {"source-context": "5"}}
 sentry_debug_files_upload(
   auth_token: '___ORG_AUTH_TOKEN___',
   org_slug: '___ORG_SLUG___',
@@ -53,7 +59,7 @@ sentry_debug_files_upload(
 )
 ```
 
-```ruby {tabTitle:Fastlane plugin before 1.20.0}
+```ruby {tabTitle:Fastlane plugin before 1.20.0} {"onboardingOptions": {"source-context": "5"}}
 sentry_upload_dif(
   auth_token: '___ORG_AUTH_TOKEN___',
   org_slug: '___ORG_SLUG___',
@@ -94,7 +100,7 @@ Another option is to use warnings, and then set `GCC_TREAT_WARNINGS_AS_ERRORS` t
 
 <OrgAuthTokenNote />
 
-```bash {tabTitle:Warn on failures - nonblocking}
+```bash {tabTitle:Warn on failures - nonblocking} {"onboardingOptions": {"source-context": "10"}}
 if [[ "$(uname -m)" == arm64 ]]; then
     export PATH="/opt/homebrew/bin:$PATH"
 fi
@@ -103,7 +109,9 @@ if which sentry-cli >/dev/null; then
 export SENTRY_ORG=___ORG_SLUG___
 export SENTRY_PROJECT=___PROJECT_SLUG___
 export SENTRY_AUTH_TOKEN=___ORG_AUTH_TOKEN___
-ERROR=$(sentry-cli debug-files upload --include-sources "$DWARF_DSYM_FOLDER_PATH" 2>&1 >/dev/null)
+ERROR=$(sentry-cli debug-files upload \ 
+--include-sources \
+"$DWARF_DSYM_FOLDER_PATH" 2>&1 >/dev/null)
 if [ ! $? -eq 0 ]; then
 echo "warning: sentry-cli - $ERROR"
 fi
@@ -112,7 +120,7 @@ echo "warning: sentry-cli not installed, download from https://github.com/getsen
 fi
 ```
 
-```bash {tabTitle:Error on failures - blocking}
+```bash {tabTitle:Error on failures - blocking} {"onboardingOptions": {"source-context": "10"}}
 if [[ "$(uname -m)" == arm64 ]]; then
     export PATH="/opt/homebrew/bin:$PATH"
 fi
@@ -121,7 +129,9 @@ if which sentry-cli >/dev/null; then
 export SENTRY_ORG=___ORG_SLUG___
 export SENTRY_PROJECT=___PROJECT_SLUG___
 export SENTRY_AUTH_TOKEN=___ORG_AUTH_TOKEN___
-ERROR=$(sentry-cli debug-files upload --include-sources "$DWARF_DSYM_FOLDER_PATH" --force-foreground 2>&1 >/dev/null)
+ERROR=$(sentry-cli debug-files upload \
+--include-sources \ 
+"$DWARF_DSYM_FOLDER_PATH" --force-foreground 2>&1 >/dev/null)
 if [ ! $? -eq 0 ]; then
 echo "error: sentry-cli - $ERROR"
 fi

platform-includes/getting-started-primer/javascript.nextjs.mdx

@@ -9,8 +9,16 @@ Features:
 
 <Note>
 
-`next dev --turbo` is not supported while Turbopack is in beta. Running your devserver with Turbopack will cause the Sentry Next.js SDK not to be loaded in the browser. Data from serverside instrumentation will also be inaccurate or incomplete.
+The Sentry SDK does not fully support `next dev --turbo` while Turbopack does not ship all the features required to run Sentry.
+
+Currently, when you run your devserver with Turbopack, the Sentry Next.js SDK will not be loaded in the browser.
+Keep this in mind when configuring the SDK.
+
+Note that this only affects the devserver.
+The Sentry SDK will run without issues when you do a production build, even if you develop locally with Turbopack.
 
 To support the SDK in the browser with Turbopack, [follow the feature request for client-side instrumentation in the Next.js repository](https://github.com/vercel/next.js/discussions/69294).
 
+You can track Sentry's Turbopack support in the [GitHub Issue in the Sentry SDK repository](https://github.com/getsentry/sentry-javascript/issues/8105).
+
 </Note>

src/components/onboarding/index.tsx

@@ -48,13 +48,23 @@ const optionDetails: Record<
       </span>
     ),
   },
+  'source-context': {
+    name: 'Source context',
+    description: (
+      <span>
+        Upload your source code to allow Sentry to display snippets of your code next to
+        the event stack traces.
+      </span>
+    ),
+  },
 };
 
 const OPTION_IDS = [
   'error-monitoring',
   'performance',
   'profiling',
   'session-replay',
+  'source-context',
 ] as const;
 
 type OptionId = (typeof OPTION_IDS)[number];