fix 404s (#12961)

getsentry · Mar 7, 2025 · 5141af6 · 5141af6
1 parent 10e4a72
commit 5141af6
Show file tree

Hide file tree

Showing 2 changed files with 2 additions and 2 deletions.
diff --git a/docs/platforms/javascript/common/enriching-events/identify-user/index.mdx b/docs/platforms/javascript/common/enriching-events/identify-user/index.mdx
@@ -45,7 +45,7 @@ You can also clear the currently set user:
 <PlatformContent includePath="enriching-events/unset-user" />
 
 <PlatformCategorySection supported={["server"]}>
-<PlatformSection notSupported={['javascript.bun', 'javascript.cloudflare', 'javascript.deno', 'javascript.react-router']}>
+<PlatformSection notSupported={['javascript.bun', 'javascript.cloudflare', 'javascript.deno', 'javascript.react-router', 'javascript.aws-lambda', 'javascript.azure-functions', 'javascript.gcp-functions']}>
 `Sentry.setUser()` will set the user for the currently active request - see <PlatformLink to="/enriching-events/request-isolation">Request Isolation</PlatformLink> for more information. For example, if you want to set the user for a single request, you can do this like this:
 </PlatformSection>
 <PlatformContent includePath="enriching-events/set-user-request" />

diff --git a/includes/migration/javascript-v8/browser-other-changes.mdx b/includes/migration/javascript-v8/browser-other-changes.mdx
@@ -34,7 +34,7 @@ Sentry.init({
 
 The xhr transport via `makeXHRTransport` transport has been removed. Only `makeFetchTransport` is available now. This means that the Sentry SDK requires the `fetch` API to be available in the environment.
 
-<PlatformSection notSupported={['javascript.wasm', 'javascript.capacitor']}>
+<PlatformSection notSupported={['javascript.wasm', 'javascript.capacitor', 'javascript.azure-functions']}>
 ### Removal of the `Offline` integration
 
 The `Offline` integration has been removed in favor of the <PlatformLink to="/configuration/transports/#makebrowserofflinetransport">offline transport wrapper</PlatformLink>