Repository navigation
Update java-v9 branch - #20099
Update java-v9 branch#20099
Conversation
…19928) ## DESCRIBE YOUR PR Every page embedded the full platform/guide list up to three times (header, mobile nav, platform selector), in both its HTML and RSC payload. The selector's copy was also computed per page to link to "the same page" on every other platform. This serves the list once as a static `/platforms.json` (34 KB, ~5 KB gzipped), which client components preload in the background when the browser is idle. When switching platforms, the selector resolves the target URL on demand with `HEAD` requests, keeping the existing fallback order (platforms: same page → parent → root; guides: same page → root). Measured locally (full `next build` vs `master`, 4 static workers, warm MDX cache): - Static generation: **71.9s → ~57s (~−20%)** - Build output: **6.9 GB → 4.0 GB (−42%)** - Sidebar nav HTML is identical on all pages The selector shows a loading row (or an error with retry) if it's opened before the list has loaded, and a spinner on the trigger while the target page resolves. **Note: this does change the UI a bit, switching guides is slower than before (e.g. when you are on page X in guide A and switch to guide B in the dropdown).** IMHO that is an acceptable tradeoff here and it is not _too_ slow. ## IS YOUR CHANGE URGENT? Help us prioritize incoming PRs by letting us know when the change needs to go live. Select exactly one option. For deadlines, replace `YYYY-MM-DD` with the due date. You can update this information later by editing the PR description. - [ ] Urgent deadline (GA date, etc.): YYYY-MM-DD - [ ] Other deadline: YYYY-MM-DD - [x] No deadline: Not urgent, can wait up to 1 week+ ## SLA - Teamwork makes the dream work, so please add a reviewer to your PRs. - Please give the docs team up to 1 week to review your PR unless you've supplied a deadline. Thanks in advance for your help! ## PRE-MERGE CHECKLIST _Make sure you've checked the following before merging your changes:_ - [ ] Checked Vercel preview for correctness, including links - [ ] PR was reviewed and approved by any necessary SMEs (subject matter experts) - [ ] PR was reviewed and approved by a member of the [Sentry docs team](https://github.com/orgs/getsentry/teams/docs) 🤖 Generated with [Claude Code](https://claude.com/claude-code) --------- Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
Sentry Python SDK 3.0 raises the minimum supported version of many instrumented libraries and drops Python 3.6. Update each integration's supported versions to match the SDK's enforced minimums, and remove Python 3.6-only instructions like installing aiocontextvars. Add a Supported Versions page that lists the minimum version of each integration's library. A 2.x version of the page keeps the previous minimums for users who haven't upgraded yet. Readers can switch between them with the version selector, and the legacy support alert on integration pages links to the 2.x page. Refs PY-1931 Can view V2 version here: https://sentry-docs-git-py-1931-version-changes.sentry.dev/platforms/python/integrations/supported-versions__v2.x Can view V3 version here: https://sentry-docs-git-py-1931-version-changes.sentry.dev/platforms/python/integrations/supported-versions/ ## IS YOUR CHANGE URGENT? Help us prioritize incoming PRs by letting us know when the change needs to go live. Select exactly one option. For deadlines, replace `YYYY-MM-DD` with the due date. You can update this information later by editing the PR description. - [ ] Urgent deadline (GA date, etc.): YYYY-MM-DD - [ ] Other deadline: YYYY-MM-DD - [x] No deadline: Not urgent, can wait up to 1 week+ ## SLA - Teamwork makes the dream work, so please add a reviewer to your PRs. - Please give the docs team up to 1 week to review your PR unless you've supplied a deadline. Thanks in advance for your help! ## PRE-MERGE CHECKLIST _Make sure you've checked the following before merging your changes:_ - [ ] Checked Vercel preview for correctness, including links - [ ] PR was reviewed and approved by any necessary SMEs (subject matter experts) - [ ] PR was reviewed and approved by a member of the [Sentry docs team](https://github.com/orgs/getsentry/teams/docs) ## LEGAL BOILERPLATE <!-- Sentry employees and contractors can delete or ignore this section. --> Look, I get it. The entity doing business as "Sentry" was incorporated in the State of Delaware in 2015 as Functional Software, Inc. and is gonna need some rights from me in order to utilize my contributions in this here PR. So here's the deal: I retain all rights, title and interest in and to my contributions, and by keeping this boilerplate intact I confirm that Sentry can use, modify, copy, and redistribute my contributions, under Sentry's choice of terms. ## EXTRA RESOURCES - [Sentry Docs contributor guide](https://docs.sentry.io/contributing/)
) <!-- Keep the urgency section so automation can prioritize this PR. You may delete other sections you don't need. --> ## DESCRIBE YOUR PR The Azure Functions (isolated worker) guide sets up tracing with `TracerProviderBuilder.AddSentry()` and `SentryOptions.UseOpenTelemetry()` from `Sentry.OpenTelemetry`. Both have been obsolete since sentry-dotnet 6.12.0, so anyone following the guide gets obsolete warnings. The guide now uses the OTLP exporter, as the `Sentry.Samples.OpenTelemetry.AzureFunctions` sample does: - Install `Sentry.OpenTelemetry.Exporter` instead of `Sentry.OpenTelemetry`. `OpenTelemetry` is no longer listed because it comes in transitively. The Package Manager tab now lists the two OpenTelemetry packages it was missing. - `AddSentryOtlpExporter(dsn)` and `UseOtlp()` replace `AddSentry()` and `UseOpenTelemetry()`. The tracing sentence now links to the OpenTelemetry (OTLP) page. - The "enabling tracing" link under Features pointed at the generic tracing concepts page. It now goes to the .NET OpenTelemetry (OTLP) page too. Closes getsentry/sentry-dotnet#5715 ### Notes for review - The snippet drops `TracesSampleRate` and `DisableSentryHttpMessageHandler`, which the sample still sets. Under `UseOtlp()` Sentry creates no transactions of its own, so `TracesSampleRate` has no effect, and the OTLP page already says not to set it. `SentryHttpMessageHandler` already skips span creation under `UseOtlp()`. Against 6.12.1, an `IHttpClientFactory` request sent with the handler on still carries a single `sentry-trace` value, and it matches `traceparent`. - The snippet's error-monitoring-only variant didn't compile. `using OpenTelemetry;` and `using Sentry.OpenTelemetry;` sat outside the performance block, but only the performance option installs those packages. Neither is needed now: `AddSentryOtlpExporter` lives in `OpenTelemetry.Trace`, and `UseOtlp` lives in `Sentry`, which the SDK adds as an implicit using. The snippet now includes `using Microsoft.Extensions.DependencyInjection;`, which `AddOpenTelemetry()` needs. - Both variants of the snippet compile without warnings against Sentry 6.12.1, using the Functions template's `ImplicitUsings`. - #19925 (merges at 7.0.0 GA) makes the same OTLP changes on this page, and also moves the options into `SentrySdk.Init`. When it merges `master` it will conflict in the `logging.AddSentry` block and on the tracing sentence. That sentence is reworded here into active voice. ## IS YOUR CHANGE URGENT? Help us prioritize incoming PRs by letting us know when the change needs to go live. Select exactly one option. For deadlines, replace `YYYY-MM-DD` with the due date. You can update this information later by editing the PR description. - [ ] Urgent deadline (GA date, etc.): YYYY-MM-DD - [ ] Other deadline: YYYY-MM-DD - [x] No deadline: Not urgent, can wait up to 1 week+ 🤖 Generated with [Claude Code](https://claude.com/claude-code) --------- Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
Co-authored-by: sentry-api-schema-updater[bot] <271575301+sentry-api-schema-updater[bot]@users.noreply.github.com>
Co-authored-by: sentry-api-schema-updater[bot] <271575301+sentry-api-schema-updater[bot]@users.noreply.github.com>
Co-authored-by: sentry-api-schema-updater[bot] <271575301+sentry-api-schema-updater[bot]@users.noreply.github.com>
Co-authored-by: sentry-api-schema-updater[bot] <271575301+sentry-api-schema-updater[bot]@users.noreply.github.com>
…ng (#20001) ## DESCRIBE YOUR PR The Bump API Schema SHA workflow got rate-limited by the GitHub API and wrote the error body (`{"message":"API rate limit exceeded for ..."}`) into `SENTRY_API_SCHEMA_SHA`. It then admin-merged the change ([#19999](#19999)). That broke `master` for about 10 minutes, until the next run ([#20000](#20000)) replaced it with a real SHA. The workflow called the commits API without authentication and never checked what came back. It now: - Sends the GitHub App token it already creates. That token has access to `sentry-api-schema`, so the request gets the much higher authenticated rate limit. - Uses `curl --fail`, so an HTTP error fails the job instead of returning the error body. - Fails the job unless the response is a 40-character hex SHA, so nothing else gets written into the file or merged. It also fixes `-sSl` to `-sSL`. Lowercase `-l` is curl's FTP `--list-only` flag; `-L` follows redirects, which is what was meant. ## IS YOUR CHANGE URGENT? - [x] No deadline: Not urgent, can wait up to 1 week+ ## PRE-MERGE CHECKLIST - [ ] Checked Vercel preview for correctness, including links - [ ] PR was reviewed and approved by any necessary SMEs (subject matter experts) - [ ] PR was reviewed and approved by a member of the [Sentry docs team](https://github.com/orgs/getsentry/teams/docs) <!-- junior-request-attribution:start --> via @sergical. <!-- junior-request-attribution:end --> <!-- junior-session-footer:start --> <!-- junior-conversation-id:slack%3AC8H0BQRDJ%3A1792070558.468179 --> -- [View Junior Session](https://junior-prod.sentry.dev/conversations/slack%3AC8H0BQRDJ%3A1792070558.468179) [[Sentry]](https://sentry.sentry.io/explore/conversations/slack%3AC8H0BQRDJ%3A1792070558.468179/?project=4510944073809921) <!-- junior-session-footer:end --> Co-authored-by: sentry-junior[bot] <264270552+sentry-junior[bot]@users.noreply.github.com> Co-authored-by: Sergiy Dybskiy <sergiy.dybskiy@sentry.io>
Co-authored-by: sentry-api-schema-updater[bot] <271575301+sentry-api-schema-updater[bot]@users.noreply.github.com>
Co-authored-by: sentry-api-schema-updater[bot] <271575301+sentry-api-schema-updater[bot]@users.noreply.github.com>
Co-authored-by: sentry-api-schema-updater[bot] <271575301+sentry-api-schema-updater[bot]@users.noreply.github.com>
…8.59.0 (#19995) Since Java/Android SDK 8.59.0 ([getsentry/sentry-java#6184](getsentry/sentry-java#6184)), direct `Sentry.logger()` and `Sentry.metrics()` calls are captured regardless of `logs.enabled` / `metrics.enabled`. `logs.enabled` now only gates automatic logging integrations, and `metrics.enabled` has no effect. The Java and Android Logs setup pages still say `logs.enabled` is required to enable logging, and the Metrics options pages (Java, Spring Boot, Android) still say `metrics.enabled=false` disables metrics entirely. This adjusts those sentences in place, keeping the existing structure and examples for older SDK versions. The flags are removed entirely in v9; that guidance is handled separately in #19962. Refs SDK-1533 <!-- junior-request-attribution:start --> via **johdax**. <!-- junior-request-attribution:end --> <!-- junior-session-footer:start --> <!-- junior-conversation-id:slack%3AD0ANK27LVV0%3A1792069918.618529 --> -- [View Junior Session](https://junior-prod.sentry.dev/conversations/slack%3AD0ANK27LVV0%3A1792069918.618529) [[Sentry]](https://sentry.sentry.io/explore/conversations/slack%3AD0ANK27LVV0%3A1792069918.618529/?project=4510944073809921) <!-- junior-session-footer:end --> Co-authored-by: sentry-junior[bot] <264270552+sentry-junior[bot]@users.noreply.github.com> Co-authored-by: Johannes Daxboeck <johannes.daxboeck@sentry.io>
Co-authored-by: sentry-api-schema-updater[bot] <271575301+sentry-api-schema-updater[bot]@users.noreply.github.com>
Co-authored-by: sentry-api-schema-updater[bot] <271575301+sentry-api-schema-updater[bot]@users.noreply.github.com>
Co-authored-by: sentry-api-schema-updater[bot] <271575301+sentry-api-schema-updater[bot]@users.noreply.github.com>
Co-authored-by: sentry-api-schema-updater[bot] <271575301+sentry-api-schema-updater[bot]@users.noreply.github.com>
…in settings (#19970) ## DESCRIBE YOUR PR The Unreal plugin settings are regrouped into feature-based sections (getsentry/sentry-unreal#1633), so several docs pages pointed to settings paths and names that no longer exist. - Updates settings paths and display names on the native backend, debug symbols, tags, screenshots, metrics and session replay pages (for example, **General > Native** is now **Crash Handling**, and the build filters moved from "Misc" to **Core > Advanced**). - Reorganizes the Options page to follow the same sections as the editor: Core, Crash Handling, Enriching Events, App Hangs, Release Health, Tracing, Logs, Metrics, Hooks, Privacy & PII, Transport, Offline Caching, Session Replay, Debug Symbols and Crash Reporter. Existing option entries are moved unchanged, so links to them keep working. - Replaces the plugin settings screenshots (settings window, debug symbols, screenshots, automatic breadcrumbs and tags) with ones that show the new layout. - Adds entries for options that weren't documented yet: diagnostic logging level, Editor DSN, build filters, promoted builds only, Android crash capture mode, tags promotion, in-app include and exclude, session tracking, user consent, HTTP proxy, shutdown timeout and database location. Also fixes existing inaccuracies: - Corrects the defaults of `Debug` (`true`), `AttachStacktrace` (`true`) and `CacheMaxItems` (`30`) to match the plugin. - Documents out-of-process screenshot capturing on Xbox development kits (`XAppCaptureTakeDiagnosticScreenshot`, native backend required) in addition to Windows. - Lists macOS with the native backend as a supported platform for the external crash reporter. - Removes the outdated "default for the `github` plugin package" note from `CrashpadWaitForUpload`. This should be merged when the Unreal SDK release that includes getsentry/sentry-unreal#1633 and getsentry/sentry-unreal#1637 is published. ## IS YOUR CHANGE URGENT? - [ ] Urgent deadline (GA date, etc.): YYYY-MM-DD - [x] Other deadline: next Unreal SDK release - [ ] No deadline: Not urgent, can wait up to 1 week+ ## PRE-MERGE CHECKLIST - [ ] Checked Vercel preview for correctness, including links - [ ] PR was reviewed and approved by any necessary SMEs (subject matter experts) - [ ] PR was reviewed and approved by a member of the [Sentry docs team](https://github.com/orgs/getsentry/teams/docs) ## Related Items - getsentry/sentry-unreal#1633 - getsentry/sentry-unreal#1637
…aced on AI SDK v7 (#20031) The Vercel AI integration page lists `generateObject()` and `streamObject()` as traced with no version caveat, but on AI SDK v7 they produce no spans. The AI SDK deprecated both in v6, and v7 doesn't publish them to the `ai:telemetry` channel the integration reads. The AI SDK team confirmed this is intentional and that both will be removed in the next major. This marks the two functions as v6 and below, and adds a note pointing to `generateText()` / `streamText()` with an `output` setting. That path is traced on v7 and produces the same `invoke_agent` and `generate_content` spans. 🤖 Generated with [Claude Code](https://claude.com/claude-code) --------- Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com> Co-authored-by: Andrei <168741329+andreiborza@users.noreply.github.com>
…20032) ## DESCRIBE YOUR PR The Sentry Dart Plugin setup guide put `auth_token` straight into the `pubspec.yaml` and `sentry.properties` examples, which suggests committing a secret to source control. This changes the default to setting the token with the `SENTRY_AUTH_TOKEN` environment variable. - Adds a "Set Your Auth Token" step with an `export SENTRY_AUTH_TOKEN=...` snippet and a note about CI secrets - Removes `auth_token` from the `pubspec.yaml` and `sentry.properties` examples - Notes in the configuration reference that the env var is the preferred way to set it (`auth_token` is still supported) - Points the Flutter troubleshooting note at `SENTRY_AUTH_TOKEN` The plugin already supports this. Its config validation accepts `SENTRY_AUTH_TOKEN` when `auth_token` isn't set, and sentry-cli picks up the variable from the environment. ## IS YOUR CHANGE URGENT? - [ ] Urgent deadline (GA date, etc.): YYYY-MM-DD - [ ] Other deadline: YYYY-MM-DD - [x] No deadline: Not urgent, can wait up to 1 week+ ## PRE-MERGE CHECKLIST - [ ] Checked Vercel preview for correctness, including links - [ ] PR was reviewed and approved by any necessary SMEs (subject matter experts) - [ ] PR was reviewed and approved by a member of the [Sentry docs team](https://github.com/orgs/getsentry/teams/docs) <!-- junior-request-attribution:start --> via **Gino Buenaflor**. <!-- junior-request-attribution:end --> <!-- junior-session-footer:start --> <!-- junior-conversation-id:slack%3AC0AESKKH28H%3A1792152626.656829 --> -- [View Junior Session](https://junior-prod.sentry.dev/conversations/slack%3AC0AESKKH28H%3A1792152626.656829) [[Sentry]](https://sentry.sentry.io/explore/conversations/slack%3AC0AESKKH28H%3A1792152626.656829/?project=4510944073809921) <!-- junior-session-footer:end --> Co-authored-by: sentry-junior[bot] <264270552+sentry-junior[bot]@users.noreply.github.com>
…9814) ## DESCRIBE YOUR PR Adds a "Scale Thresholds to the Chart Interval" section to the widget builder docs. It covers the new **Interval** option for time-series widget thresholds, added in getsentry/sentry#124735 and getsentry/sentry#124744. The section explains how Fixed and time-window thresholds differ, walks through a scaling example, and lists when the dropdown shows up: time-series widgets where each query has a single `count`, `count_if`, `sum`, or `failure_count` aggregate, or an equation. The dropdown stays disabled until a threshold value is entered. ## IS YOUR CHANGE URGENT? - [ ] Urgent deadline (GA date, etc.): YYYY-MM-DD - [ ] Other deadline: YYYY-MM-DD - [x] No deadline: Not urgent, can wait up to 1 week+ ## PRE-MERGE CHECKLIST - [ ] Checked Vercel preview for correctness, including links - [ ] PR was reviewed and approved by any necessary SMEs (subject matter experts) - [ ] PR was reviewed and approved by a member of the [Sentry docs team](https://github.com/orgs/getsentry/teams/docs) <!-- junior-request-attribution:start --> via **shaun.kaasten**. <!-- junior-request-attribution:end --> <!-- junior-session-footer:start --> <!-- junior-conversation-id:slack%3AD0BAS2BU2TC%3A1791229795.832609 --> -- [View Junior Session](https://junior-prod.sentry.dev/conversations/slack%3AD0BAS2BU2TC%3A1791229795.832609) [[Sentry]](https://sentry.sentry.io/explore/conversations/slack%3AD0BAS2BU2TC%3A1791229795.832609/?project=4510944073809921) <!-- junior-session-footer:end --> Co-authored-by: sentry-junior[bot] <264270552+sentry-junior[bot]@users.noreply.github.com> Co-authored-by: Shaun Kaasten <shaun.kaasten@sentry.io>
Co-authored-by: sentry-api-schema-updater[bot] <271575301+sentry-api-schema-updater[bot]@users.noreply.github.com>
Co-authored-by: sentry-api-schema-updater[bot] <271575301+sentry-api-schema-updater[bot]@users.noreply.github.com>
Co-authored-by: sentry-api-schema-updater[bot] <271575301+sentry-api-schema-updater[bot]@users.noreply.github.com>
Co-authored-by: sentry-api-schema-updater[bot] <271575301+sentry-api-schema-updater[bot]@users.noreply.github.com>
Co-authored-by: sentry-api-schema-updater[bot] <271575301+sentry-api-schema-updater[bot]@users.noreply.github.com>
Co-authored-by: sentry-api-schema-updater[bot] <271575301+sentry-api-schema-updater[bot]@users.noreply.github.com>
Co-authored-by: sentry-api-schema-updater[bot] <271575301+sentry-api-schema-updater[bot]@users.noreply.github.com>
Co-authored-by: sentry-api-schema-updater[bot] <271575301+sentry-api-schema-updater[bot]@users.noreply.github.com>
Co-authored-by: sentry-api-schema-updater[bot] <271575301+sentry-api-schema-updater[bot]@users.noreply.github.com>
Co-authored-by: Alexander Dinauer <adinauer@users.noreply.github.com>
The top-level Python SDK API for custom tracing instrumentation will be rewired to span streaming in the upcoming 3.0 major. Create a versioned copy of the relevant pages, once with the old API (<3.0), and one for 3.0+. Direct link to preview: - [span streaming migration guide](https://sentry-docs-git-ivana-stream-migration-guide-versioned.sentry.dev/platforms/python/tracing/streamed-spans/migration-guide/) - [streamed spans page](https://sentry-docs-git-ivana-stream-migration-guide-versioned.sentry.dev/platforms/python/tracing/streamed-spans/) ## IS YOUR CHANGE URGENT? Help us prioritize incoming PRs by letting us know when the change needs to go live. Select exactly one option. For deadlines, replace `YYYY-MM-DD` with the due date. You can update this information later by editing the PR description. - [ ] Urgent deadline (GA date, etc.): YYYY-MM-DD - [ ] Other deadline: YYYY-MM-DD - [x] No deadline: Not urgent, can wait up to 1 week+ ## SLA - Teamwork makes the dream work, so please add a reviewer to your PRs. - Please give the docs team up to 1 week to review your PR unless you've supplied a deadline. Thanks in advance for your help! ## PRE-MERGE CHECKLIST _Make sure you've checked the following before merging your changes:_ - [x] Checked Vercel preview for correctness, including links - [ ] PR was reviewed and approved by any necessary SMEs (subject matter experts) - [ ] PR was reviewed and approved by a member of the [Sentry docs team](https://github.com/orgs/getsentry/teams/docs) ## LEGAL BOILERPLATE <!-- Sentry employees and contractors can delete or ignore this section. --> Look, I get it. The entity doing business as "Sentry" was incorporated in the State of Delaware in 2015 as Functional Software, Inc. and is gonna need some rights from me in order to utilize my contributions in this here PR. So here's the deal: I retain all rights, title and interest in and to my contributions, and by keeping this boilerplate intact I confirm that Sentry can use, modify, copy, and redistribute my contributions, under Sentry's choice of terms. ## EXTRA RESOURCES - [Sentry Docs contributor guide](https://docs.sentry.io/contributing/)
## DESCRIBE YOUR PR Documents the `buildTimeInstrumentation` option of `sentrySvelteKit`. SvelteKit had no entry for it. Users who need to keep a package unbundled (see getsentry/sentry-javascript#25470) also need to know that `ssr.external` turns off build-time instrumentation for that package. ## IS YOUR CHANGE URGENT? - [ ] Urgent deadline (GA date, etc.): YYYY-MM-DD - [ ] Other deadline: YYYY-MM-DD - [x] No deadline: Not urgent, can wait up to 1 week+ ## PRE-MERGE CHECKLIST - [ ] Checked Vercel preview for correctness, including links - [ ] PR was reviewed and approved by any necessary SMEs (subject matter experts) - [ ] PR was reviewed and approved by a member of the [Sentry docs team](https://github.com/orgs/getsentry/teams/docs)
Co-authored-by: sentry-api-schema-updater[bot] <271575301+sentry-api-schema-updater[bot]@users.noreply.github.com>
Co-authored-by: sentry-api-schema-updater[bot] <271575301+sentry-api-schema-updater[bot]@users.noreply.github.com>
Co-authored-by: sentry-api-schema-updater[bot] <271575301+sentry-api-schema-updater[bot]@users.noreply.github.com>
## Describe your PR Add Trace View guidance for the upcoming trace waterfall features. Readers can understand time compression, pin an attribute to compare span values, and click a Web Vital pill to inspect the surrounding spans. Include the supplied screenshots and demonstration GIF. Split the change into one commit per feature, each with its supporting images. ## Is your change urgent? - [ ] Urgent deadline (GA date, etc.): YYYY-MM-DD - [ ] Other deadline: YYYY-MM-DD - [x] No deadline: Not urgent, can wait up to 1 week+ ## Verification - Prettier and `git diff --check` pass. - The page and local images compile with the repository's MDX image plugins after each commit. - Independent content review found no actionable issues. The Sentry Plain Speech brand audit is complete. ## Pre-merge Checklist - [ ] Checked Vercel preview for correctness, including links - [ ] PR was reviewed and approved by any necessary SMEs (subject matter experts) - [ ] PR was reviewed and approved by a member of the [Sentry docs team](https://github.com/orgs/getsentry/teams/docs) --------- Co-authored-by: Codex <noreply@openai.com>
Co-authored-by: sentry-api-schema-updater[bot] <271575301+sentry-api-schema-updater[bot]@users.noreply.github.com>
…19874) ## DESCRIBE YOUR PR This documents `withSentry` from `@sentry/nextjs/cloudflare` (getsentry/sentry-javascript#24998, SDK 11.6.0) on the Next.js on Cloudflare page. The page now shows the custom Worker that wraps the OpenNext entry, what `sentry.server.config.ts` and `sentry.edge.config.ts` still do in the Worker, and the order the SDK uses to pick the release. ## IS YOUR CHANGE URGENT? Help us prioritize incoming PRs by letting us know when the change needs to go live. Select exactly one option. For deadlines, replace `YYYY-MM-DD` with the due date. You can update this information later by editing the PR description. - [ ] Urgent deadline (GA date, etc.): YYYY-MM-DD - [ ] Other deadline: YYYY-MM-DD - [x] No deadline: Not urgent, can wait up to 1 week+ ## SLA - Teamwork makes the dream work, so please add a reviewer to your PRs. - Please give the docs team up to 1 week to review your PR unless you've supplied a deadline. Thanks in advance for your help! ## PRE-MERGE CHECKLIST _Make sure you've checked the following before merging your changes:_ - [ ] Checked Vercel preview for correctness, including links - [ ] PR was reviewed and approved by any necessary SMEs (subject matter experts) - [ ] PR was reviewed and approved by a member of the [Sentry docs team](https://github.com/orgs/getsentry/teams/docs) ## LEGAL BOILERPLATE <!-- Sentry employees and contractors can delete or ignore this section. --> Look, I get it. The entity doing business as "Sentry" was incorporated in the State of Delaware in 2015 as Functional Software, Inc. and is gonna need some rights from me in order to utilize my contributions in this here PR. So here's the deal: I retain all rights, title and interest in and to my contributions, and by keeping this boilerplate intact I confirm that Sentry can use, modify, copy, and redistribute my contributions, under Sentry's choice of terms. ## EXTRA RESOURCES - [Sentry Docs contributor guide](https://docs.sentry.io/contributing/) Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
Co-authored-by: sentry-api-schema-updater[bot] <271575301+sentry-api-schema-updater[bot]@users.noreply.github.com>
Adds a Pi Durable card to the agent integrations section of the docs homepage, linking to the standalone [Pi Durable guide](https://docs.sentry.io/platforms/javascript/guides/pi-durable/). <img width="1029" height="389" alt="Firefox 2026-10-19 14 06 26" src="https://github.com/user-attachments/assets/ee60d9e3-2e0b-4031-84ec-167006bde689" /> <img width="1038" height="391" alt="Firefox 2026-10-19 14 06 19" src="https://github.com/user-attachments/assets/6a6cdb19-ed81-4287-aa92-f26ec59dfa43" /> ## IS YOUR CHANGE URGENT? Help us prioritize incoming PRs by letting us know when the change needs to go live. Select exactly one option. For deadlines, replace `YYYY-MM-DD` with the due date. You can update this information later by editing the PR description. - [ ] Urgent deadline (GA date, etc.): YYYY-MM-DD - [ ] Other deadline: YYYY-MM-DD - [x] No deadline: Not urgent, can wait up to 1 week+ Co-authored-by: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
## DESCRIBE YOUR PR We're deprecating the old 3-arg combinators for a new one that allows arbitrary conditions, so this updates how we refer to them so its clear there's a new format and for which datasets ## IS YOUR CHANGE URGENT? Help us prioritize incoming PRs by letting us know when the change needs to go live. Select exactly one option. For deadlines, replace `YYYY-MM-DD` with the due date. You can update this information later by editing the PR description. - [ ] Urgent deadline (GA date, etc.): YYYY-MM-DD - [ ] Other deadline: YYYY-MM-DD - [x] No deadline: Not urgent, can wait up to 1 week+ ## SLA - Teamwork makes the dream work, so please add a reviewer to your PRs. - Please give the docs team up to 1 week to review your PR unless you've supplied a deadline. Thanks in advance for your help! ## PRE-MERGE CHECKLIST _Make sure you've checked the following before merging your changes:_ - [ ] Checked Vercel preview for correctness, including links - [ ] PR was reviewed and approved by any necessary SMEs (subject matter experts) - [ ] PR was reviewed and approved by a member of the [Sentry docs team](https://github.com/orgs/getsentry/teams/docs) ## LEGAL BOILERPLATE <!-- Sentry employees and contractors can delete or ignore this section. --> Look, I get it. The entity doing business as "Sentry" was incorporated in the State of Delaware in 2015 as Functional Software, Inc. and is gonna need some rights from me in order to utilize my contributions in this here PR. So here's the deal: I retain all rights, title and interest in and to my contributions, and by keeping this boilerplate intact I confirm that Sentry can use, modify, copy, and redistribute my contributions, under Sentry's choice of terms. ## EXTRA RESOURCES - [Sentry Docs contributor guide](https://docs.sentry.io/contributing/)
…20017) ## DESCRIBE YOUR PR Removes the `SplitLayout` component everywhere. Pages that used it now render their text and code as regular docs content, with the standard docs spacing. - Removes the `<SplitLayout>`, `<SplitSection>`, `<SplitSectionText>`, and `<SplitSectionCode>` wrapper lines from all 169 MDX files that used them, including the quick start guides. Only the tag lines and the blank lines around them change. Parsing each file before and after shows the same content once the wrappers are ignored. - Deletes `src/components/splitLayout/` and its registration in `src/mdxComponents.ts`. - Drops the SplitLayout guidance from `.claude/skills/technical-docs/SKILL.md`. Step numbering is unaffected. `StepConnector` finds its `h2` headings with a descendant selector, so it doesn't depend on these wrappers. This replaces #19984, which made SplitLayout render as a single column. ### Merge order Merge this **first**. After it merges, the quick start template PRs that also edit these files (#19980 Ruby, #19981 Dart and Flutter, #19982 Python, #19983 JavaScript) will need `master` merged in. Those conflicts are limited to the removed wrapper tags. ## IS YOUR CHANGE URGENT? - [ ] Urgent deadline (GA date, etc.): YYYY-MM-DD - [ ] Other deadline: YYYY-MM-DD - [x] No deadline: Not urgent, can wait up to 1 week+ ## PRE-MERGE CHECKLIST - [ ] Checked Vercel preview for correctness, including links - [ ] PR was reviewed and approved by any necessary SMEs (subject matter experts) - [ ] PR was reviewed and approved by a member of the [Sentry docs team](https://github.com/orgs/getsentry/teams/docs) <!-- junior-request-attribution:start --> via **shannon.anahata**. <!-- junior-request-attribution:end --> <!-- junior-session-footer:start --> <!-- junior-conversation-id:slack%3AD0BB8KQT6MU%3A1792013336.218129 --> -- [View Junior Session](https://junior-prod.sentry.dev/conversations/slack%3AD0BB8KQT6MU%3A1792013336.218129) [[Sentry]](https://sentry.sentry.io/explore/conversations/slack%3AD0BB8KQT6MU%3A1792013336.218129/?project=4510944073809921) <!-- junior-session-footer:end --> --------- Co-authored-by: sentry-junior[bot] <264270552+sentry-junior[bot]@users.noreply.github.com> Co-authored-by: Shannon Anahata <shannon.anahata@sentry.io>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
Please update the IS YOUR CHANGE URGENT? section of the PR description:
This information helps the Docs team prioritize your review. |
|
The change loads the SDK list in the browser instead of on every page. It also ships a large documentation content sync. An issue escalates when not-found events rise or client errors rise. Services: Mention PlanWhat changedThe platform selector no longer receives the full SDK list from the server. RiskA failed Intended effectPlatform docs must keep loading after the selector no longer embeds the SDK list.
Regression watchWatch client crashes, not-found rate, and page time on the same docs path.
Not observableClient fetches of |
Co-authored-by: sentry-api-schema-updater[bot] <271575301+sentry-api-schema-updater[bot]@users.noreply.github.com>
Weekly automated sync of
masterintojava-v9.This brings in 52 commits from
master.Please review, then merge with a merge commit (do not squash).
via Junior system actor
scheduler.--
View Junior Session [Sentry]