getsentry · s1gr1d · May 28, 2026 · May 28, 2026
diff --git a/develop-docs/backend/application-domains/tasks/index.mdx b/develop-docs/backend/application-domains/tasks/index.mdx
@@ -342,7 +342,7 @@ def test_schedule_task(self, mock_deliver: MagicMock) -> None:
     mock_deliver.delay.assert_called_with(webhook_one.id)
 ```
 
-<Alert type="warning">
+<Alert level="warning">
 Mocking tasks will not validate that parameters are JSON compatible, nor will it catch TypeErrors from signature mismatches.
 </Alert>
 

diff --git a/develop-docs/development-infrastructure/testing.mdx b/develop-docs/development-infrastructure/testing.mdx
@@ -285,7 +285,7 @@ with in_test_hide_transaction_boundary():
     users = user_service.get_many(filter={"user_ids": list(owners)})
 ```
 
-<Alert type="warning">
+<Alert level="warning">
 Bypassing safety checks is not recommended and usage can cause consistency
 issues and data loss.
 </Alert>

diff --git a/docs/contributing/approach/sdk-docs/write-getting-started.mdx b/docs/contributing/approach/sdk-docs/write-getting-started.mdx
@@ -4,7 +4,7 @@ noindex: true
 sidebar_order: 30
 ---
 
-<Alert type="info">
+<Alert level="info">
   This page describes the legacy "Getting Started" guide format. New SDKs and
   guides that have been updated should use the [Quick Start guide
   format](/contributing/approach/sdk-docs/write-quick-start/).

diff --git a/docs/contributing/approach/sdk-docs/write-quick-start.mdx b/docs/contributing/approach/sdk-docs/write-quick-start.mdx
@@ -6,7 +6,7 @@ sidebar_order: 25
 
 New SDKs should use the Quick Start guide format outlined on this page. You may still encounter Getting Started guides for existing SDKs.
 
-<Alert type="info" title="Note">
+<Alert level="info" title="Note">
   If you want to update an existing Getting Started Guide without refactoring it
   into a Quick Start guide, see [How to Write - Getting
   Started](/contributing/approach/sdk-docs/write-getting-started/). If you're
@@ -133,7 +133,7 @@ If the content you want to include doesn't already exist, create a new file for
 
 Integrate this content into your guide using the `PlatformSection` component.
 
-<Alert type="info">
+<Alert level="info">
   If the SDK supports performance monitoring, add it to the list that links back
   into the SDK content from Product, stored in
   [`/docs/product/dashboards/sentry-dashboards/index.mdx`](https://github.com/getsentry/sentry-docs/blob/master/docs/product/dashboards/sentry-dashboards/index.mdx) (Sentry Dashboards index, which includes a Set Up section and platform redirect to tracing).

diff --git a/docs/platforms/apple/guides/ios/size-analysis/insights.mdx b/docs/platforms/apple/guides/ios/size-analysis/insights.mdx
@@ -34,7 +34,7 @@ Below are a list of available insights for iOS builds, followed by more details
 
 **How to fix**: Strip symbols from release builds and instead use debug symbols in separate dSYM files for crash reporters.
 
-<Alert type="warning">
+<Alert level="warning">
   Stripping symbols before creating a dSYM breaks crash symbolication. Confirm
   your release build still produces and uploads dSYMs (or another crash reporter
   has them) before stripping.
@@ -50,7 +50,7 @@ strip -rSTx AppBinary -o AppBinaryStripped
 
 To automate stripping in your project after building, add a Run Script phase that skips non-release builds and leaves Apple-signed frameworks untouched:
 
-<Alert type="warning">
+<Alert level="warning">
   This script will strip the main app binary along with any binaries in the
   `Frameworks/` directory. This is a sample script that **may require
   adjustments** for your project.
@@ -304,7 +304,7 @@ Xcode now limits the export trie to just that allowlist.
 
 **How to fix**: Enable [Source maps](https://reactnative.dev/docs/debugging-release-builds) when building your release app.
 
-<Alert type="warning">
+<Alert level="warning">
   Stripping debug information breaks crash symbolication. Source maps need to be
   uploaded separately to your crash reporter.
 </Alert>
diff --git a/docs/platforms/dotnet/common/user-feedback/index.mdx b/docs/platforms/dotnet/common/user-feedback/index.mdx
@@ -25,7 +25,7 @@ var eventId = SentrySdk.CaptureMessage("An event that will receive user feedback
 SentrySdk.CaptureFeedback("It broke.", "user@example.com", "The User", associatedEventId: eventId);
 ```
 
-<Alert type="info">
+<Alert level="info">
 
 Note that Sentry will reject and drop any feedback events where the email address is invalid. To avoid this, the Sentry SDK for .NET removes invalid email addresses before sending feedback. Ideally you should validate the email address before calling this API.
 

diff --git a/docs/platforms/javascript/common/configuration/event-loop-block.mdx b/docs/platforms/javascript/common/configuration/event-loop-block.mdx
@@ -60,7 +60,7 @@ For detailed usage instructions and configuration options, see the [`eventLoopBl
 
 ## Deprecated Application Not Responding (ANR) Integration
 
-<Alert type="warning">
+<Alert level="warning">
 
 **Deprecated**: The `anrIntegration` is deprecated. Please use the [`eventLoopBlockIntegration`](../integrations/event-loop-block) instead for better performance and more comprehensive monitoring.
 

diff --git a/docs/platforms/javascript/common/configuration/integrations/anr.mdx b/docs/platforms/javascript/common/configuration/integrations/anr.mdx
@@ -24,7 +24,7 @@ supported:
   - javascript.tanstackstart-react
 ---
 
-<Alert type="warning">
+<Alert level="warning">
 
 **Deprecated**: This integration is deprecated. Please use the [`eventLoopBlockIntegration`](./event-loop-block) instead for better performance and more comprehensive monitoring.
 

diff --git a/docs/platforms/javascript/common/configuration/integrations/httpclient.mdx b/docs/platforms/javascript/common/configuration/integrations/httpclient.mdx
@@ -60,7 +60,7 @@ Default: `[/.*/]`
 
 _Type: `boolean`_
 
-<Alert type="warning">
+<Alert level="warning">
   This option has to be specified on the root Sentry.init options, not the
   integration options!
 </Alert>

diff --git a/docs/platforms/javascript/guides/angular/manual-setup.mdx b/docs/platforms/javascript/guides/angular/manual-setup.mdx
@@ -4,7 +4,7 @@ sidebar_order: 1
 description: "Learn how to set up the Sentry Angular SDK manually."
 ---
 
-<Alert type="info">
+<Alert level="info">
   For the fastest setup, we recommend using the [wizard
   installer](/platforms/javascript/guides/angular).
 </Alert>

diff --git a/docs/platforms/javascript/guides/cloudflare/frameworks/nextjs.mdx b/docs/platforms/javascript/guides/cloudflare/frameworks/nextjs.mdx
@@ -14,7 +14,7 @@ Before you begin, make sure you have:
 - A Next.js application configured for Cloudflare Workers with [OpenNext](https://opennext.js.org/cloudflare)
 - The Sentry SDK [installed and configured](/platforms/javascript/guides/nextjs/) in your Next.js application
 
-<Alert type="info">
+<Alert level="info">
   If you haven't deployed a Next.js app to Cloudflare Workers before, follow
   Cloudflare's [Next.js deployment
   guide](https://developers.cloudflare.com/workers/framework-guides/web-apps/nextjs/)

diff --git a/docs/platforms/javascript/guides/nextjs/manual-setup/index.mdx b/docs/platforms/javascript/guides/nextjs/manual-setup/index.mdx
@@ -10,7 +10,7 @@ categories:
   - server-node
 ---
 
-<Alert type="info">
+<Alert level="info">
   For the fastest setup, we recommend using the [wizard
   installer](/platforms/javascript/guides/nextjs).
 </Alert>
@@ -230,7 +230,7 @@ The example above samples 100% of traces in development and 10% in production. M
 
 Create a [Next.js Instrumentation file](https://nextjs.org/docs/app/building-your-application/optimizing/instrumentation) named `instrumentation.ts` in your project root (or `src` folder). This file imports your server and edge configurations and exports `onRequestError` to capture server-side errors.
 
-<Alert type="info">
+<Alert level="info">
   The `onRequestError` hook requires `@sentry/nextjs` version `8.28.0` or higher
   and Next.js 15.
 </Alert>
@@ -585,7 +585,7 @@ If your application uses both the App Router and Pages Router:
 2. Add a `pages/_error.tsx` file for Pages Router error handling (see [Pages Router Setup](/platforms/javascript/guides/nextjs/manual-setup/pages-router/))
 3. Both routers share the same Sentry configuration files
 
-<Alert type="info">
+<Alert level="info">
   The Sentry SDK automatically detects which router is being used and applies
   the appropriate instrumentation.
 </Alert>

diff --git a/docs/platforms/javascript/guides/nextjs/manual-setup/pages-router.mdx b/docs/platforms/javascript/guides/nextjs/manual-setup/pages-router.mdx
@@ -4,7 +4,7 @@ sidebar_order: 2
 description: "Manual setup for Next.js applications using the Pages Router."
 ---
 
-<Alert type="info">
+<Alert level="info">
   For the fastest setup, we recommend using the [wizard
   installer](/platforms/javascript/guides/nextjs).
 </Alert>
@@ -71,7 +71,7 @@ pnpm add @sentry/nextjs
 
 Extend your app's default Next.js options by adding `withSentryConfig` into your `next.config.ts` (or `next.config.js`) file.
 
-<Alert type="info">
+<Alert level="info">
   Pages Router applications typically use Webpack. The Webpack configuration
   includes auto-instrumentation options that automatically wrap your API routes
   and page data fetching methods.
@@ -467,7 +467,7 @@ If your application uses both the App Router and Pages Router:
 2. Add the `pages/_error.tsx` file from this guide for Pages Router error handling
 3. Both routers share the same Sentry configuration files
 
-<Alert type="info">
+<Alert level="info">
   The Sentry SDK automatically detects which router is being used and applies
   the appropriate instrumentation.
 </Alert>

diff --git a/docs/platforms/javascript/guides/nextjs/manual-setup/webpack-setup.mdx b/docs/platforms/javascript/guides/nextjs/manual-setup/webpack-setup.mdx
@@ -8,7 +8,7 @@ This guide covers the configuration differences for **Next.js applications using
 
 For a complete reference of all build configuration options, see the [Build Configuration](/platforms/javascript/guides/nextjs/configuration/build/) documentation.
 
-<Alert type="info">
+<Alert level="info">
   If you're using Next.js 15+ with Turbopack (the default), you don't need this
   guide. See the [main manual
   setup](/platforms/javascript/guides/nextjs/manual-setup/) instead.
@@ -74,7 +74,7 @@ export default withSentryConfig(nextConfig, {
 
 With Webpack, you can exclude specific routes from automatic instrumentation. This is useful for health check endpoints or routes that shouldn't be monitored.
 
-<Alert type="info">
+<Alert level="info">
   This option has no effect when using Turbopack, as Turbopack relies on Next.js
   telemetry features instead of build-time instrumentation.
 </Alert>

diff --git a/docs/platforms/javascript/guides/nuxt/manual-setup.mdx b/docs/platforms/javascript/guides/nuxt/manual-setup.mdx
@@ -4,7 +4,7 @@ sidebar_order: 1
 description: "Learn how to manually set up Sentry in your Nuxt app and capture your first errors."
 ---
 
-<Alert type="info">
+<Alert level="info">
   For the fastest setup, we recommend using the [wizard
   installer](/platforms/javascript/guides/nuxt).
 </Alert>

diff --git a/docs/platforms/javascript/guides/react-router/manual-setup.mdx b/docs/platforms/javascript/guides/react-router/manual-setup.mdx
@@ -11,7 +11,7 @@ description: "Learn how to manually set up Sentry in your React Router v7 app an
   you have any feedback or concerns.
 </Alert>
 
-<Alert type="info">
+<Alert level="info">
   For the fastest setup, we recommend using the [wizard
   installer](/platforms/javascript/guides/react-router).
 </Alert>

diff --git a/docs/platforms/javascript/guides/remix/manual-setup.mdx b/docs/platforms/javascript/guides/remix/manual-setup.mdx
@@ -4,7 +4,7 @@ sidebar_order: 1
 description: "Learn how to manually set up Sentry in your Remix app and capture your first errors."
 ---
 
-<Alert type="info">
+<Alert level="info">
   For the fastest setup, we recommend using the [wizard
   installer](/platforms/javascript/guides/remix).
 </Alert>

diff --git a/docs/platforms/javascript/guides/sveltekit/manual-setup.mdx b/docs/platforms/javascript/guides/sveltekit/manual-setup.mdx
@@ -4,7 +4,7 @@ sidebar_order: 1
 description: "Learn how to manually set up Sentry in your SvelteKit app and capture your first errors."
 ---
 
-<Alert type="info">
+<Alert level="info">
   For the fastest setup, we recommend using the [wizard
   installer](/platforms/javascript/guides/sveltekit).
 </Alert>

diff --git a/docs/platforms/javascript/guides/sveltekit/manual-setup__v10.7.0.mdx b/docs/platforms/javascript/guides/sveltekit/manual-setup__v10.7.0.mdx
@@ -4,7 +4,7 @@ sidebar_order: 1
 description: "Learn how to manually set up Sentry in your SvelteKit app and capture your first errors."
 ---
 
-<Alert type="info">
+<Alert level="info">
   For the fastest setup, we recommend using the [wizard
   installer](/platforms/javascript/guides/sveltekit).
 </Alert>

diff --git a/docs/product/monitors-and-alerts/monitors/index.mdx b/docs/product/monitors-and-alerts/monitors/index.mdx
@@ -47,7 +47,7 @@ Monitors are made of attributes that define when to create an issue, and actions
 - Set the assignee
 - Connect [Custom Alerts](/product/monitors-and-alerts/alerts/) like external notifications and ticket creation to pair with your Monitor
 
-<Alert type="note">
+<Alert level="note">
 
 Assignees set by [ownership rules](/product/issues/ownership-rules/) will override assignees set by Monitors.
 

diff --git a/docs/product/monitors-and-alerts/monitors/uptime-monitoring/index.mdx b/docs/product/monitors-and-alerts/monitors/uptime-monitoring/index.mdx
@@ -87,7 +87,7 @@ Uptime checks include spans called _uptime request spans_ that Sentry automatica
 - Request lifecycle: You can see the full journey from the initial uptime check through your application's response
 - Enhanced debugging: You can see more details about exactly where and why the failure occurred to distinguish between uptime-related issues and other application problems
 
-<Alert type="info">
+<Alert level="info">
 Uptime request spans are free and will not count against your [span quota](/pricing/quotas/manage-transaction-quota/). These spans are always created, even if you have sampling disabled.
 </Alert>
 

diff --git a/platform-includes/logs/usage/javascript.astro.mdx b/platform-includes/logs/usage/javascript.astro.mdx
@@ -2,7 +2,7 @@
 
 <Include name="logs/javascript-usage-nodejs.mdx" />
 
-<Alert type="warning" title="Runtime Support">
+<Alert level="warning" title="Runtime Support">
 
 Using `printf` log syntax only works server-side in the Node.js and Bun runtimes.
 

diff --git a/platform-includes/logs/usage/javascript.nextjs.mdx b/platform-includes/logs/usage/javascript.nextjs.mdx
@@ -2,7 +2,7 @@
 
 <Include name="logs/javascript-usage-nodejs.mdx" />
 
-<Alert type="warning" title="Runtime Support">
+<Alert level="warning" title="Runtime Support">
 
 Using `printf` log syntax only works server-side in the Node.js and Bun runtimes.
 

diff --git a/platform-includes/logs/usage/javascript.nuxt.mdx b/platform-includes/logs/usage/javascript.nuxt.mdx
@@ -2,7 +2,7 @@
 
 <Include name="logs/javascript-usage-nodejs.mdx" />
 
-<Alert type="warning" title="Runtime Support">
+<Alert level="warning" title="Runtime Support">
 
 Using `printf` log syntax only works server-side in the Node.js and Bun runtimes.
 

diff --git a/platform-includes/logs/usage/javascript.react-router.mdx b/platform-includes/logs/usage/javascript.react-router.mdx
@@ -2,7 +2,7 @@
 
 <Include name="logs/javascript-usage-nodejs.mdx" />
 
-<Alert type="warning" title="Runtime Support">
+<Alert level="warning" title="Runtime Support">
 
 Using `printf` log syntax only works server-side in the Node.js and Bun runtimes.
 

diff --git a/platform-includes/logs/usage/javascript.remix.mdx b/platform-includes/logs/usage/javascript.remix.mdx
@@ -2,7 +2,7 @@
 
 <Include name="logs/javascript-usage-nodejs.mdx" />
 
-<Alert type="warning" title="Runtime Support">
+<Alert level="warning" title="Runtime Support">
 
 Using `printf` log syntax only works server-side in the Node.js and Bun runtimes.
 

diff --git a/platform-includes/logs/usage/javascript.solidstart.mdx b/platform-includes/logs/usage/javascript.solidstart.mdx
@@ -2,7 +2,7 @@
 
 <Include name="logs/javascript-usage-nodejs.mdx" />
 
-<Alert type="warning" title="Runtime Support">
+<Alert level="warning" title="Runtime Support">
 
 Using `printf` log syntax only works server-side in the Node.js and Bun runtimes.
 

diff --git a/platform-includes/logs/usage/javascript.sveltekit.mdx b/platform-includes/logs/usage/javascript.sveltekit.mdx
@@ -2,7 +2,7 @@
 
 <Include name="logs/javascript-usage-nodejs.mdx" />
 
-<Alert type="warning" title="Runtime Support">
+<Alert level="warning" title="Runtime Support">
 
 Using `printf` log syntax only works server-side in the Node.js and Bun runtimes.
 

diff --git a/platform-includes/logs/usage/javascript.tanstackstart-react.mdx b/platform-includes/logs/usage/javascript.tanstackstart-react.mdx
@@ -2,7 +2,7 @@
 
 <Include name="logs/javascript-usage-nodejs.mdx" />
 
-<Alert type="warning" title="Runtime Support">
+<Alert level="warning" title="Runtime Support">
 
 Using `printf` log syntax only works server-side in the Node.js and Bun runtimes.
 

diff --git a/platform-includes/metrics/default-attributes/apple.mdx b/platform-includes/metrics/default-attributes/apple.mdx
@@ -27,7 +27,7 @@ If there is an active span when the metric is recorded, the following attribute
 
 - `span_id`: The span ID of the active span.
 
-<Alert type="info">
+<Alert level="info">
 The `trace_id` is set as a top-level field on the metric (not as an attribute) to enable distributed tracing correlation. When a span is active, the SDK uses that span's trace ID; otherwise, it falls back to the propagation context's trace ID.
 </Alert>
 

diff --git a/platform-includes/performance/add-spans-example/native.mdx b/platform-includes/performance/add-spans-example/native.mdx
@@ -97,7 +97,7 @@ perform_checkout();
 
 After the client called either function, the following transactions inherit that trace from the `propagation_context` and no longer act as trace boundaries.
 
-<Alert type="warning" title="Downstream SDK usage">
+<Alert level="warning" title="Downstream SDK usage">
   If you interact with the Native SDK in the context of a downstream SDK (for
   instance Android, .NET, Unity, or Unreal), we urge you not to use
   `sentry_regenerate_trace()` since it would interfere with the traces managed