Merge branch 'master' of github.com:getsentry/sentry-docs into smi/react/router-clean-up

Author: inventarSarah

develop-docs/backend/application-domains/database-migrations/index.mdx

@@ -134,9 +134,9 @@ This is complicated due to our deploy process. When we deploy, we run migrations
 
 To avoid this, follow these steps:
 
-- Make a PR to remove all uses of the column in the codebase in a separate PR. This mostly helps with code cleanliness. This should be merged ahead of the migration prs, but we don't need to worry about whether it is deployed first.
+- First, if the column is either not nullable, or doesn't have a `db_default` set, then make a PR to make it nullable via `null=True`.
+- Then, remove all uses of the column in the codebase in a separate PR; this mostly helps with code cleanliness. This should be merged ahead of the next migration PRs, but we don't need to worry about whether it is deployed first.
 - Make another PR that:
-    - Checks if the column is either not nullable, or doesn't have a `db_default` set. If either of these is true, then make it nullable via `null=True`.
     - If the column is a foreign key, remove the database level foreign key constraint it by setting `db_constraint=False`.
     - Remove the column and in the generated migration use `SafeRemoveField(..., deletion_action=DeletionAction.MOVE_TO_PENDING)` to replace `RemoveField(...)`. This only marks the state for the column as removed.
     - Combine these migrations together to save making multiple deploys

docs/contributing/pages/components.mdx

@@ -130,6 +130,12 @@ Render an expandable section to provide additional information to users on deman
   provide optional information that can help users be more successful.
 </Expandable>
 
+<Expandable title="Expandable with a code block">
+  ```js
+  const foo = 'bar';
+  ```
+</Expandable>
+
 ```markdown {tabTitle:Example}
 <Expandable title="Here's something worth noting">
   This is an expandable section in an `'info'` alert style.

docs/platforms/android/troubleshooting/index.mdx

@@ -318,3 +318,5 @@ This problem is only relevant to these specific versions: `sentry-android-core`
 </Alert>
 
 Check [this issue](https://github.com/getsentry/sentry-android-gradle-plugin/issues/329) for more details.
+
+<PageGrid />

docs/platforms/android/troubleshooting/mixed-versions/index.mdx

@@ -0,0 +1,50 @@
+---
+title: Mixed Versions
+description: "Troubleshoot and resolve mixed Android SDK dependency versions."
+sidebar_order: 1000
+---
+
+Using multiple Android SDK dependencies with mixed versions is not supported as it is very likely to lead to a crash later on. For this reason we chose to crash the application on SDK init instead.
+
+## Multiple Dependencies With Mixed Versions
+
+The following snippet shows a mixed version conflict caused by using `sentry` with version `8.6.0` and `sentry-android` with version `8.7.0`. To fix the issue, set the same version for all dependencies or <PlatformLink to="/configuration/bill-of-materials/">use `sentry-bom`</PlatformLink>. This may also happen if you are using an internal library which has a different version defined.
+
+```groovy {tabTitle:Gradle}{filename:build.gradle}
+implementation('io.sentry:sentry:8.6.0')
+implementation('io.sentry:sentry-android:8.7.0')
+```
+```xml {tabTitle:Maven}{filename:pom.xml}
+<dependencyManagement>
+    <dependencies>
+        <dependency>
+            <groupId>io.sentry</groupId>
+            <artifactId>sentry</artifactId>
+            <version>8.6.0</version>
+        </dependency>
+        <dependency>
+            <groupId>io.sentry</groupId>
+            <artifactId>sentry-android</artifactId>
+            <version>8.7.0</version>
+        </dependency>
+    </dependencies>
+</dependencyManagement>
+```
+
+## Build Plugin And Explicit Dependency
+
+When using our Gradle or Maven plugin and manually defining additional Sentry Android SDK dependencies, it is also possible to end up with mixed versions. The following snippet shows the plugin being configured to use version `8.0.0` but there is an additional dependency that has been set to version `8.1.0`. To fix the issue,  set the same version or <PlatformLink to="/configuration/bill-of-materials/">use `sentry-bom`</PlatformLink>.
+
+```groovy {tabTitle:Gradle}{filename:build.gradle}
+plugins { id "io.sentry.android.gradle" version "5.3.0" }
+
+dependencies {
+	implementation 'io.sentry:sentry-okhttp:8.1.0'
+}
+
+sentry {
+	autoInstallation {
+		sentryVersion = "8.0.0"
+	}
+}
+```

docs/platforms/java/common/troubleshooting/index.mdx

@@ -0,0 +1,7 @@
+---
+title: Troubleshooting
+description: "Troubleshoot and resolve common issues with the Java SDK."
+sidebar_order: 9000
+---
+
+<PageGrid />

docs/platforms/java/common/troubleshooting/mixed-versions/index.mdx

@@ -0,0 +1,54 @@
+---
+title: Mixed Versions
+description: "Troubleshoot and resolve mixed Java SDK dependency versions."
+sidebar_order: 1000
+---
+
+Using multiple Java SDK dependencies with mixed versions is not supported as it is very likely to lead to a crash later on. For this reason we chose to crash the application on SDK init instead.
+
+## Multiple Dependencies With Mixed Versions
+
+The following snippet shows a mixed version conflict caused by using `sentry` with version `8.6.0` and `sentry-logback` with version `8.7.0`. To fix the issue please set the same version for all dependencies or <PlatformLink to="/configuration/bill-of-materials/">use `sentry-bom`</PlatformLink>. This may also happen if you are using an internal library which has a different version defined.
+
+```groovy {tabTitle:Gradle}{filename:build.gradle}
+implementation('io.sentry:sentry:8.6.0')
+implementation('io.sentry:sentry-logback:8.7.0')
+```
+```xml {tabTitle:Maven}{filename:pom.xml}
+<dependencyManagement>
+    <dependencies>
+        <dependency>
+            <groupId>io.sentry</groupId>
+            <artifactId>sentry</artifactId>
+            <version>8.6.0</version>
+        </dependency>
+        <dependency>
+            <groupId>io.sentry</groupId>
+            <artifactId>sentry-logback</artifactId>
+            <version>8.7.0</version>
+        </dependency>
+    </dependencies>
+</dependencyManagement>
+```
+
+## Build Plugin And Explicit Dependency
+
+When using our Gradle or Maven plugin and manually defining additional Sentry Java SDK dependencies, it is also possible to end up with mixed versions. The following snippet shows the plugin being configured to use version `8.0.0`, but there is an additional dependency that has been set to version `8.1.0`. To fix the issue, set the same version or <PlatformLink to="/configuration/bill-of-materials/">use `sentry-bom`</PlatformLink>.
+
+```groovy {tabTitle:Gradle}{filename:build.gradle}
+plugins { id "io.sentry.android.gradle" version "5.3.0" }
+
+dependencies {
+	implementation 'io.sentry:sentry-opentelemetry-agentless-spring:8.1.0'
+}
+
+sentry {
+	autoInstallation {
+		sentryVersion = "8.0.0"
+	}
+}
+```
+
+## Agent Version And Build Time Version
+
+When using `sentry-opentelemetry-agent` you may end up using a version of the Agent that differs from other Sentry Java SDK dependencies you are using. This is also not supported. Use the same version for `sentry-opentelemetry-agent` and all other Java SDK dependencies.

docs/platforms/javascript/common/tracing/index.mdx

@@ -4,7 +4,7 @@ description: "Learn how to enable tracing in your app."
 sidebar_order: 4000
 ---
 
-With [tracing](/product/insights/overview/), Sentry automatically tracks your software performance across your application services, measuring metrics like throughput and latency, and displaying the impact of errors across multiple systems. 
+With [tracing](/product/insights/overview/), Sentry automatically tracks your software performance across your application services, measuring metrics like throughput and latency, and displaying the impact of errors across multiple systems.
 
 <PlatformCategorySection supported={["server", "serverless"]}>
   <Alert>
@@ -45,7 +45,7 @@ With [tracing](/product/insights/overview/), Sentry automatically tracks your so
 
 The two options are mutually exclusive. If both are set, <PlatformIdentifier name="traces-sampler" /> will take precedence.
 
-Learn more about tracing <PlatformLink to="/configuration/options/#tracing-options">options</PlatformLink>, how to use the <PlatformLink to="/configuration/sampling/#setting-a-sampling-function">tracesSampler</PlatformLink> function, or how to <PlatformLink to="/configuration/sampling/#sampling-transaction-events">sample transactions</PlatformLink>.
+You can find more in-depth explanations and examples about sampling configuration in [Configure Sampling](./configure-sampling).
 
 ## Distributed Tracing
 

docs/platforms/javascript/common/troubleshooting/index.mdx

@@ -105,7 +105,7 @@ To fix this, change the `tracePropagationTargets` option during SDK initializati
 </PlatformCategorySection>
 
 <PlatformCategorySection notSupported={['browser']}>
-<PlatformSection notSupported={['javascript.aws-lambda', 'javascript.azure-functions', 'javascript.bun', 'javascript.cloudflare', 'javascript.deno', 'javascript.electron', 'javascript.gcp-functions']}>
+<PlatformSection notSupported={['javascript.aws-lambda', 'javascript.azure-functions', 'javascript.bun', 'javascript.cloudflare', 'javascript.deno', 'javascript.electron', 'javascript.gcp-functions', 'javascript.tanstackstart-react']}>
 <Expandable permalink title="Error: 'import-in-the-middle' failed to wrap">
  When using ESM, by default all packages are wrapped under the hood by
  [import-in-the-middle](https://www.npmjs.com/package/import-in-the-middle).

docs/platforms/javascript/guides/remix/manual-setup.mdx

@@ -124,22 +124,6 @@ function App() {
 export default withSentry(App);
 ```
 
-You can disable or configure `ErrorBoundary` using a second parameter to `withSentry`.
-
-```tsx
-withSentry(App, {
-  wrapWithErrorBoundary: false,
-});
-
-// or
-
-withSentry(App, {
-  errorBoundaryOptions: {
-    fallback: <p>An error has occurred</p>,
-  },
-});
-```
-
 ### Server-side Configuration
 
 Create an instrumentation file (named here as `instrument.server.mjs`) in your project. Add your initialization code in this file for the server-side SDK.

docs/platforms/javascript/guides/svelte/index.mdx

@@ -131,7 +131,18 @@ Once you've done this, the SDK will automatically capture unhandled errors and p
 
 This snippet includes an intentional error, so you can test that everything is working as soon as you set it up.
 
-```jsx {tabTitle:Svelte} {filename:SomeCmponent.svelte}
+```jsx {tabTitle:Svelte v5+} {filename:SomeCmponent.svelte}
+<button
+  type="button"
+  onclick={() => {
+    throw new Error("Sentry Frontend Error");
+  }}
+>
+  Throw error
+</button>
+```
+
+```jsx {tabTitle:Svelte v3/v4} {filename:SomeCmponent.svelte}
 <button
   type="button"
   on:click={() => {