Merge branch 'master' into cameroncooke/docs/snapshotpreviews-metadata

Author: cameroncooke

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>
 

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>

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/).

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).

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>

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.
 

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.
 

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.
 

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>

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>