Merge branch 'master' of github.com:getsentry/sentry-docs into smi/quick-start/react-manual

Author: inventarSarah

.github/workflows/algolia-index.yml

@@ -48,6 +48,8 @@ jobs:
           DOCS_INDEX_NAME: ${{ secrets.DOCS_INDEX_NAME }}
           NEXT_PUBLIC_ALGOLIA_APP_ID: ${{ secrets.NEXT_PUBLIC_ALGOLIA_APP_ID }}
           NEXT_PUBLIC_ALGOLIA_SEARCH_KEY: ${{ secrets.NEXT_PUBLIC_ALGOLIA_SEARCH_KEY }}
+          SENTRY_DSN: https://[email protected]/0
+          NEXT_PUBLIC_SENTRY_DSN: https://[email protected]/0
 
       - name: Build index for developer docs
         run: yarn build:developer-docs && bun ./scripts/algolia.ts
@@ -58,4 +60,6 @@ jobs:
           DOCS_INDEX_NAME: ${{ secrets.DEVELOP_DOCS_INDEX_NAME }}
           NEXT_PUBLIC_ALGOLIA_APP_ID: ${{ secrets.NEXT_PUBLIC_ALGOLIA_APP_ID }}
           NEXT_PUBLIC_ALGOLIA_SEARCH_KEY: ${{ secrets.NEXT_PUBLIC_ALGOLIA_SEARCH_KEY }}
+          SENTRY_DSN: https://[email protected]/0
+          NEXT_PUBLIC_SENTRY_DSN: https://[email protected]/0
           NEXT_PUBLIC_DEVELOPER_DOCS: 1

app/[[...path]]/page.tsx

@@ -22,7 +22,7 @@ import {isDeveloperDocs} from 'sentry-docs/isDeveloperDocs';
 import {
   getDevDocsFrontMatter,
   getDocsFrontMatter,
-  getFileBySlug,
+  getFileBySlugWithCache,
   getVersionsFromDoc,
 } from 'sentry-docs/mdx';
 import {mdxComponents} from 'sentry-docs/mdxComponents';
@@ -106,9 +106,9 @@ export default async function Page(props: {params: Promise<{path?: string[]}>})
 
   if (isDeveloperDocs) {
     // get the MDX for the current doc and render it
-    let doc: Awaited<ReturnType<typeof getFileBySlug>> | null = null;
+    let doc: Awaited<ReturnType<typeof getFileBySlugWithCache>>;
     try {
-      doc = await getFileBySlug(`develop-docs/${params.path?.join('/') ?? ''}`);
+      doc = await getFileBySlugWithCache(`develop-docs/${params.path?.join('/') ?? ''}`);
     } catch (e) {
       if (e.code === 'ENOENT') {
         // eslint-disable-next-line no-console
@@ -144,9 +144,9 @@ export default async function Page(props: {params: Promise<{path?: string[]}>})
   }
 
   // get the MDX for the current doc and render it
-  let doc: Awaited<ReturnType<typeof getFileBySlug>> | null = null;
+  let doc: Awaited<ReturnType<typeof getFileBySlugWithCache>>;
   try {
-    doc = await getFileBySlug(`docs/${pageNode.path}`);
+    doc = await getFileBySlugWithCache(`docs/${pageNode.path}`);
   } catch (e) {
     if (e.code === 'ENOENT') {
       // eslint-disable-next-line no-console

apps/changelog/package.json

@@ -25,7 +25,7 @@
     "@radix-ui/react-icons": "^1.3.2",
     "@radix-ui/react-toolbar": "^1.1.0",
     "@radix-ui/themes": "^3.1.3",
-    "@sentry/nextjs": "9.9.0",
+    "@sentry/nextjs": "9.10.1",
     "@spotlightjs/spotlight": "^2.1.1",
     "next": "15.2.3",
     "next-auth": "^4.24.5",
@@ -68,4 +68,4 @@
     "@types/react": "npm:[email protected]",
     "@types/react-dom": "npm:[email protected]"
   }
-}
+}

apps/changelog/sentry.client.config.ts renamed to apps/changelog/src/instrumentation-client.ts

@@ -1,7 +1,3 @@
-// This file configures the initialization of Sentry on the client.
-// The config you add here will be used whenever a users loads a page in their browser.
-// https://docs.sentry.io/platforms/javascript/guides/nextjs/
-
 import * as SentryCore from '@sentry/core';
 import * as Sentry from '@sentry/nextjs';
 import * as Spotlight from '@spotlightjs/spotlight';

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

develop-docs/development-infrastructure/continuous-integration.mdx

@@ -32,7 +32,7 @@ You might also be interested in <Link to="/development/environment/#troubleshoot
 
 **Problem:**
 
-When pushing your build to staging and you it fails the `Ensure test image` step on Travis.
+When pushing your build to staging and it fails the `Ensure test image` step on Travis.
 
 **Solution:**
 

develop-docs/sdk/data-model/event-payloads/contexts.mdx

@@ -8,7 +8,7 @@ related to the current user and the environment. For example, the device or
 application version. Its canonical name is `contexts`.
 
 The `contexts` type can be used to define arbitrary contextual data on the
-event. It accepts an object of key/value pairs. The key is the “alias” of the
+event. It accepts an object of key/value pairs. The key is the "alias" of the
 context and can be freely chosen. However, as per policy, it should match the
 type of the context unless there are two values for a type. You can omit `type`
 if the key name is the type.
@@ -273,7 +273,7 @@ To summarize:
 
 : _Optional_. Typically provides the full name, full version, and release alias. This maps to `PRETTY_NAME` in [`/etc/os-release`](https://www.freedesktop.org/software/systemd/man/latest/os-release.html#PRETTY_NAME=) (examples: `Ubuntu 22.04.4 LTS`, `Raspian GNU/Linux 10 (buster)`).
 
-### Example OS Context
+**Example OS Context**
 
 The OS Context for the 3 major OSs should look like this:
 
@@ -468,7 +468,7 @@ Examples: `"Apple Metal"` or `"Direct3D11"`
 
 : _Optional_. Are geometry shaders available on the device?
 
-### Example GPU Context
+**Example GPU Context**
 
 ```json
 {
@@ -496,7 +496,7 @@ The `type` and default key is `"state"`.
 
 : **Required**. Object with two keys: _Optional_ `type` for naming the state library (e.g.: Redux, MobX, Vuex) and **Required** `value` that holds the state object.
 
-### Example State Context
+**Example State Context**
 
 ```json
 {
@@ -598,7 +598,7 @@ The `type` and default key is `"cloud_resource"`.
 
 - Example: `t4g.medium`
 
-### Example Cloud Resource Context
+**Example Cloud Resource Context**
 
 The following example illustrates the contexts part of the <Link to="/sdk/data-model/event-payloads/">event payload</Link> and omits other attributes for simplicity.
 
@@ -720,7 +720,7 @@ The `route` currently supports the following predefined fields if it's a map:
 
 If the route is set to a string (e.g. `"route": "foo"`), it will be normalized into a map (e.g. `"route": {"name": "foo"}`) server-side.
 
-### Example Trace Context
+**Example Trace Context**
 
 ```json
 {
@@ -766,7 +766,7 @@ envelope endpoint.
 
 : **Required**. The replay_id associated with the event.
 
-### Example Replay Context
+**Example Replay Context**
 
 ```json
 {
@@ -792,7 +792,7 @@ This is mostly set on transactions in a web server environment where one transac
 
 - Example: `200`
 
-### Example Response Context
+**Example Response Context**
 
 ```json
 {
@@ -822,7 +822,7 @@ The required field is `package` which should contain the package or framework wh
 
 - Example: `true`
 
-### Example Response Context
+**Example Response Context**
 
 ```json
 {
@@ -852,7 +852,7 @@ The feature flag context contains information about the flags evaluated prior to
 - Example: `false`
 
 
-### Example Feature Flag Context
+**Example Feature Flag Context**
 
 ```json
 {

docs/concepts/migration/index.mdx

@@ -48,7 +48,7 @@ Below is a non-exhaustive list of some items that will not be relocated:
 - Issues
 - Events
 - Replays and/or other [Event Attachments](/platforms/javascript/enriching-events/attachments/)
-- Source Maps, [Debug Information Files](/cli/dif/) and/or [Artifact Bundles](/platforms/javascript/sourcemaps/troubleshooting_js/artifact-bundles/)
+- Source Maps, [Debug Information Files](/cli/dif/) and/or [Debug IDs](/platforms/javascript/sourcemaps/troubleshooting_js/debug-ids/)
 - Release information, including any references to external repositories via specific Pull Requests
 - Deployment information
 - Custom Avatars

docs/concepts/search/searchable-properties/session-replay.mdx

@@ -226,9 +226,9 @@ A release is a version of your code deployed to an environment. You can create a
 
 - **Type:** string
 
-### `replayType`
+### `replay_type`
 
-The reason a replay was triggered. For example, `session` when `replaysSessionSampleRate` takes effect, or `error` when `replaysOnErrorSampleRate` is sampled instead of `session`.
+The reason a replay was triggered. For example, `session` when `replaysSessionSampleRate` takes effect, or `buffer` when `replaysOnErrorSampleRate` is sampled instead of `session`. Learn more in the [Session Replay docs](/platforms/javascript/session-replay/understanding-sessions/).
 
 - **Type:** string
 

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.