Skip to content

Update java-v9 branch - #20839

Merged
adinauer merged 141 commits into
java-v9from
master
Nov 17, 2026
Merged

adinauer merged 141 commits into
java-v9from
master

Conversation

@sentry-junior

@sentry-junior sentry-junior Bot commented Nov 17, 2026

Copy link
Copy Markdown
Contributor

Weekly automated sync of master into java-v9, so the Java v9 docs branch keeps picking up changes landed on master and doesn't drift further.

This brings in 141 commits from master. Any merge conflicts need to be resolved by a human reviewer.

Please merge with a merge commit (not squash) after review, so the commit history of master is preserved on java-v9.

via automation sched_ad73d0ab6d1d56c93807b4c35dcc4acd · Run ID sched_ad73d0ab6d1d56c93807b4c35dcc4acd:1794904200000.

--

View Session [Sentry]

sentry-junior Bot and others added 30 commits November 10, 2026 10:15
## DESCRIBE YOUR PR

The Java `shutdownTimeoutMillis` docs say the option "controls how many
seconds to wait before shutting down", but the value is in milliseconds
(default `2000`, which is two seconds). A user following the current
text and setting `2` would get a 2 ms timeout.

**Source evidence (sentry-java `8.63.0`):**
[`sentry/src/main/java/io/sentry/SentryOptions.java`](https://github.com/getsentry/sentry-java/blob/8.63.0/sentry/src/main/java/io/sentry/SentryOptions.java)
declares `private long shutdownTimeoutMillis = 2000; // 2s`, and
`setShutdownTimeoutMillis(long)` documents the parameter as "the
shutdown timeout in millis". The Java drain docs
(`platform-includes/configuration/drain-example/java.mdx`) already
describe it as milliseconds.

**Corrected wording:** "Controls how many milliseconds to wait before
shutting down. … The default is `2000` (two seconds)."

cc @adinauer @runningcode @markushi @romtsn

## IS YOUR CHANGE URGENT?

Help us prioritize incoming PRs by letting us know when the change needs
to go live.

- [ ] Urgent deadline (GA date, etc.): YYYY-MM-DD
- [ ] Other deadline: YYYY-MM-DD
- [x] No deadline: Not urgent, can wait up to 1 week+

<!-- junior-request-attribution:start -->
via [automation
`sched_fe39d4dd0d4e77a4b4463de325041d04`](https://junior-prod.sentry.dev/automations/sched_fe39d4dd0d4e77a4b4463de325041d04)
· Run ID `sched_fe39d4dd0d4e77a4b4463de325041d04:1794297600000`.
<!-- junior-request-attribution:end -->

<!-- junior-session-footer:start -->
<!--
junior-conversation-id:agent-dispatch%3Adispatch_b9504a85e9a51c0857a164aec8606f80
-->

--

[View
Session](https://junior-prod.sentry.dev/conversations/agent-dispatch%3Adispatch_b9504a85e9a51c0857a164aec8606f80)
[[Sentry]](https://sentry.sentry.io/explore/conversations/agent-dispatch%3Adispatch_b9504a85e9a51c0857a164aec8606f80/?project=4510944073809921)

<!-- junior-session-footer:end -->

Co-authored-by: sentry-junior[bot] <264270552+sentry-junior[bot]@users.noreply.github.com>
…start guides (#19981)

## DESCRIBE YOUR PR

Applies the quick start template from #19295 (Ember) to the Dart and
Flutter quick starts.

- Removes the onboarding option checkboxes and `___PRODUCT_OPTION___`
markers.
- Configure names the features each guide sets up: Error Monitoring,
Logs, Application Metrics, and Tracing, plus Session Replay for Flutter.
The init snippets include those options by default, and a note explains
that unwanted options can be removed. Flutter's Configure step now shows
the `SentryFlutter.init` the wizard creates, so the snippet is visible
even when the wizard is used.
- Adds **Send Logs** and **Send Application Metrics** as their own steps
(`Sentry.logger` / `Sentry.metrics`, which need no enable flag in the
current SDK). Send Logs links to the `sentry_logging` integration.
- Simplifies Verify to a single test error. Flutter keeps the wizard's
sample exception flow. Next Steps is trimmed.
- `flutter/manual-setup.mdx` is unchanged. It's a separate manual flow
and still uses the shared Dart logs/metrics verify includes.

## 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>
Co-authored-by: Shannon Anahata <shannonanahata@gmail.com>
Co-authored-by: inventarSarah <sarah@codingwriter.com>
## DESCRIBE YOUR PR

Broadens the `invalid` discard reason to cover any data that is dropped
because it is invalid, including data in an invalid SDK state, not only
data that fails validation. It applies only when no more specific reason
fits.

The case that prompted this: transaction-based SDKs drop child spans
that finish after their transaction was sent. A child span can't outlive
its transaction, so the span is invalid, but it didn't strictly "fail
validation." JS already reports this case as `invalid`. We discussed
this in the SDK team channel.

New wording: "Telemetry item failed validation or was otherwise invalid,
and no more specific reason applies."

The reason is already registered, so this only changes the spec. This
bumps the spec to `1.26.0` and sets the discard-reasons section's
`since` to `1.26.0`, following the spec lifecycle.

Refs getsentry/sentry-rust#1397

## 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 @szokeasaurusrex.
<!-- junior-request-attribution:end -->

<!-- junior-session-footer:start -->
<!-- junior-conversation-id:slack%3ACUCRT2B70%3A1793710228.570199 -->

--

[View
Session](https://junior-prod.sentry.dev/conversations/slack%3ACUCRT2B70%3A1793710228.570199)
[[Sentry]](https://sentry.sentry.io/explore/conversations/slack%3ACUCRT2B70%3A1793710228.570199/?project=4510944073809921)

<!-- junior-session-footer:end -->

---------

Co-authored-by: sentry-junior[bot] <264270552+sentry-junior[bot]@users.noreply.github.com>
Co-authored-by: Daniel Szoke <7881302+szokeasaurusrex@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

The OTLP traces and logs endpoints went GA in May 2026, but the docs
still show the "open beta" banner. This PR removes the banner from:

- `docs/concepts/otlp/index.mdx` (the [OTLP landing
page](https://docs.sentry.io/concepts/otlp/))
- `docs/concepts/otlp/direct/traces.mdx`
- `docs/concepts/otlp/direct/logs.mdx`

It also removes the **alpha** stability callout from
`docs/concepts/otlp/forwarding/pipelines/sentry-exporter.mdx`, at the
docs owner's request. Note: upstream, the exporter in
`opentelemetry-collector-contrib`
(`exporter/sentryexporter/metadata.yaml`) is still `alpha: [traces,
logs]`. Promoting it there is being discussed separately with the code
owners.

GA references:
- getsentry/relay#5951 moves `relay-otlp-traces-endpoint` and
`relay-otel-logs-endpoint` into `GRADUATED_FEATURE_FLAGS`
- getsentry/sentry#115049 and getsentry/sentry#115051 ("The OTLP
endpoints are GA")
- getsentry/sentry-options-automator#7708

**Not changed:**
- `docs/concepts/otlp/direct/claude-platform.mdx` still includes the
open beta banner. Anthropic's OpenTelemetry export on the Claude
Platform is itself in beta, and the page already says so in its body
text. Reviewers: should that page drop the Sentry banner too and rely
only on the body text?

Related: the announcement discussion getsentry/sentry#85902 still says
"Open Beta" and may need a GA update.

## 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 @dingsdax.
<!-- junior-request-attribution:end -->

<!-- junior-session-footer:start -->
<!-- junior-conversation-id:slack%3AC096V5NJXQU%3A1794241656.085869 -->

--

[View
Session](https://junior-prod.sentry.dev/conversations/slack%3AC096V5NJXQU%3A1794241656.085869)
[[Sentry]](https://sentry.sentry.io/explore/conversations/slack%3AC096V5NJXQU%3A1794241656.085869/?project=4510944073809921)

<!-- junior-session-footer:end -->

---------

Co-authored-by: sentry-junior[bot] <264270552+sentry-junior[bot]@users.noreply.github.com>
Co-authored-by: Johannes Daxböck <114897+dingsdax@users.noreply.github.com>
<!-- Keep the urgency section so automation can prioritize this PR. You
may delete other sections you don't need. -->

## DESCRIBE YOUR PR

This documents the `isStreamingResponse` option of the Cloudflare SDK
(getsentry/sentry-javascript#24932) in the Cloudflare section of the
options page. It explains what `true`, `false`, and `undefined` do,
which responses the SDK treats as streamed by default (now including RSC
`text/x-component` responses without a `Content-Length`), and shows the
streamed SSR example for HTML.

getsentry/sentry-javascript#24932 merged on 2026-10-19 and isn't
released yet. `availableSince` is set to `11.9.0`, the next minor.
Update the version if the release differs, and merge only after the
release is out.

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

<!-- junior-request-attribution:start -->
via **Jan Peer Stöcklmair**.
<!-- junior-request-attribution:end -->

<!-- junior-session-footer:start -->
<!-- junior-conversation-id:slack%3AC0CA6TD3QRK%3A1792429376.732779 -->

--

[View Junior
Session](https://junior-prod.sentry.dev/conversations/slack%3AC0CA6TD3QRK%3A1792429376.732779)
[[Sentry]](https://sentry.sentry.io/explore/conversations/slack%3AC0CA6TD3QRK%3A1792429376.732779/?project=4510944073809921)

<!-- junior-session-footer:end -->

---------

Co-authored-by: sentry-junior[bot] <264270552+sentry-junior[bot]@users.noreply.github.com>
Co-authored-by: Jan VamPeer Stöcklmair <jan.peer@sentry.io>
## DESCRIBE YOUR PR

We want team review enforcement on these pages

## IS YOUR CHANGE URGENT?

- [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:_

- [N/A, no changes] Checked Vercel preview for correctness, including
links
- [X] 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)
…20638)

## DESCRIBE YOUR PR

Replaces #20557.

Adds a `<ConventionAttributes>` MDX component that renders span
attribute tables straight from
[`@sentry/conventions`](https://github.com/getsentry/sentry-conventions),
so the develop docs stop drifting from the conventions repo. The AI
agents module page is the first user.

- New `ConventionAttributes` component (with tests), registered in
`mdxComponents.ts`
- All attribute tables on the AI agents page now render from
conventions; footnotes the convention briefs already cover are dropped
- Depends on `@sentry/conventions@^0.33.0`, which ships
getsentry/sentry-conventions#784 through #788

Preview:
https://develop-docs-git-cleptric-featconvention-attributes-component.sentry.dev/sdk/telemetry/traces/modules/ai-agents/

## 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: sentry-junior[bot] <264270552+sentry-junior[bot]@users.noreply.github.com>
Co-authored-by: Johannes Daxböck <johannes.daxboeck@sentry.io>
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
…19977)

## DESCRIBE YOUR PR

This moves the pages under Cloudflare → Frameworks into their framework
guides as "Quick Start (Cloudflare)", right below the default quick
start, for example `/guides/nextjs/cloudflare/`. This applies to Astro,
Hono, Next.js, Nuxt, Remix, SvelteKit and TanStack Start. The pages keep
their content, and the old URLs redirect.

- Next.js on Cloudflare is now a full quick start (wizard, Wrangler
configuration, `withSentry` Worker entry for OpenNext and vinext,
verification).
- The Hydrogen guides move into the React Router guide (Hydrogen
2025.5.0 and later) and the Remix guide (older versions, as "Hydrogen
(Legacy)").
- Cloudflare → Frameworks redirects to the Cloudflare quick start, which
links to every framework page.
- The TanStack Start page now installs `@sentry/tanstackstart-react`,
which its code imports, and its Wrangler and source maps sections render
again.

Each framework with quick starts for more than one runtime also gets [a
runtime
selector](https://sentry-docs-git-jp-poc-c-runtime-quick-starts.sentry.dev/platforms/javascript/guides/nextjs/cloudflare/).
It is static HTML, so the Markdown export for agents has the same links
as a "Runtime" list:

<img width="1288" height="483" alt="Image"
src="https://github.com/user-attachments/assets/ebe5e40a-9b92-4b63-93fd-197032a552fc"
/>

## Hono decision

The Hono page moves as it is: it shows the Cloudflare install and
configure steps, and links to the Hono quick start for the rest. The
Hono quick start already covers Cloudflare in its runtime tabs, so the
alternative is to redirect the old page there. A full Cloudflare quick
start and the runtime selector for Hono will come in a follow up,
because the Hono guide needs some rework.

## Known issues

- No Bun or Deno quick starts for Next.js and Nuxt, because the SDK repo
has no tests for them on these runtimes.
- The Next.js verify step builds with `opennextjs-cloudflare`, so it
does not apply to vinext apps.

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

---------

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
Co-authored-by: sentry-junior[bot] <264270552+sentry-junior[bot]@users.noreply.github.com>
… starts (#19974)

## DESCRIBE YOUR PR

This turns the Express, Fastify, Hapi and Koa guides into landing pages
that link to the Node.js, Bun and Deno quick starts, because the runtime
SDKs instrument these frameworks automatically. Their subpages redirect
to the Node.js guide.

<img width="300" alt="Image"
src="https://github.com/user-attachments/assets/c13aa129-cea4-41e2-a35a-d3bd89936332"
/>

The runtime quick starts get a "Framework" dropdown with 2 groups:

- **Set up with this guide** (Express, Fastify, Koa, Hapi): swaps in the
framework's snippets, such as error capture and the test route, and
labels each changed block. A line under the dropdown links to the
changed steps. The selection is kept in `?framework=express`.
- **Set up with its own guide** (Next.js, Nuxt, Hono, Elysia and
others): opens that framework's guide. On Cloudflare, the dropdown
replaces the list of framework guides.

FWIW the dropdown is onkly for humans. Agents already find everything in
the respective guide, such as Express. Meta frameworks, that are not
based on an integration are baked-in into the markdown, so agents finds
it too:
https://sentry-docs-git-jp-poc-selector-2-all-frameworks.sentry.dev/platforms/javascript/guides/node.md

<img width="400" alt="Image"
src="https://github.com/user-attachments/assets/cba3ad92-d9f0-43a1-8980-538d68f37349"
/>

<img width="200" alt="Image"
src="https://github.com/user-attachments/assets/afde2d83-7a35-421e-91ac-56d2df72b0f6"
/>

In addition, `/platform-redirect/` links for these guides go to the
Node.js page when the guide does not have the requested page.

The selector is ported from #19683.

## Known issues

- Express, Fastify, Koa and Hapi are not in the Cloudflare dropdown,
because they have no tested setup on Workers.
- The table of contents does not show headings that only exist in a
swapped-in snippet.
- The framework snippets load in the browser, so the `.md` export and
agents get only the runtime steps. The setup code is the same for every
framework, only the examples differ.

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

---------

Co-authored-by: Francesco Novy <francesco.novy@sentry.io>
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
Co-authored-by: sentry-junior[bot] <264270552+sentry-junior[bot]@users.noreply.github.com>
## DESCRIBE YOUR PR

This links the runtime quick starts of the agent guides, so a reader or
a coding agent can start on one page and find the setup for their
runtime. Pi Durable, Mastra and Flue set `runtime` in their frontmatter,
so they show the runtime selector from #19977, and Pi Durable gets new
Deno and Bun quick starts.

- The framework dropdown on the Node.js, Bun, Deno and Cloudflare quick
starts gets an "Agent frameworks" group (Eve, Flue, Mastra and Pi
Durable). Each entry opens the quick start for that runtime.
- On Deno, the app loads the Sentry import hook with `--preload`, and
`deno.json` needs `nodeModulesDir`. On Bun, the app must be built with
`sentryBunPlugin`, because Bun has no runtime hook.

## Dropdown decision

"Agent frameworks" comes before "Set up with its own guide", so the
agent guides are near the top of the dropdown. The alternative is to
show them last.

## Known issues

- The SDK repo has no tests for Pi Durable on Deno or Bun yet. Both
setups were tested locally with a fake model provider.

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

---------

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
## DESCRIBE YOUR PR

This lists the JavaScript runtimes (Browser JavaScript, Node.js, Bun,
Deno and Cloudflare) first in the sidebar platform selector and in the
platform grid on the SDKs page, under a "Runtimes" title. The other
JavaScript guides follow under "Frameworks and more". While searching,
the titles are hidden and results keep their relevance order.

The sidebar is now grouped:

<img width="275" height="424" alt="Image"
src="https://github.com/user-attachments/assets/00ba8b77-0172-437e-96b3-e45f3fd24b02"
/>

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

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>
Document the Web tunneling options and add a setup guide for forwarding Godot events through a user-chosen server endpoint to help avoid ad blockers. Include GDScript configuration, a JavaScript handler for POST requests, and delivery verification steps.
Documents automatic frame, rendering, and memory metrics introduced in Godot SDK 2.4.0, plus network metrics coming in 2.5.0. Covers configuration in Project Settings, GDScript, and C#, along with metric definitions, attributes, and collection limitations. Links the general configuration reference to the Application Metrics guide.
The Getting Started agent guide only reported onboarding progress
through the Sentry MCP server, and only when an onboarding code appeared
in the user's first message. Since
[#130292](getsentry/sentry#130292) merged,
handoff agents arrive at this guide directly after CLI login, with the
run code in the handoff guide rather than in the user's first message.
That left CLI-only handoff agents with no progress instructions at all.

This adds a `sentry api` route to the Onboarding Progress section so CLI
agents can report, widens the code trigger to also accept a code from
"the Sentry handoff guide that sent you here", renames `connect_mcp` to
`connect_agent` in the stage table, and drops the MCP-only framing
throughout (heading, intro, field prefixes, stop conditions).

Refs VDY-366

**Merge gates**
- sentry PR [#130281](getsentry/sentry#130281)
(`connect_agent` alias) deployed to all cells
- sentry PR [#130290](getsentry/sentry#130290)
(`extra.method` on connect) deployed to all cells
- toolkit PR [#2063](getsentry/toolkit#2063)
(MCP accepts `connect_agent`) deployed to hosted MCP

**Handoff side**
The one-sentence run code handover goes in Evan's
[#130263](getsentry/sentry#130263).

**Verification**
- No `update.` prefix remains in the section; `connect_mcp` and the old
heading are gone
- Route table, heading, intro, CLI/MCP bullets, stop codes, and stage
table all checked
- Prettier, typos, lychee, and trailing-slashes need to run locally
(node_modules not installed in sandbox)

---------

Co-authored-by: Cursor <cursoragent@cursor.com>
Co-authored-by: Evan Purkhiser <evanpurkhiser@gmail.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

Lighthouse lists render-blocking CSS as the top performance issue. Most
of the cost is one stylesheet, about 89 KiB over the network, and most
of that is the all-in-one `@radix-ui/themes/styles.css`. That file ships
all 30 Radix color scales, and the site uses 7 of them.

This PR imports Radix Themes in parts so we only ship the colors we use:

- Replaced `@import '@radix-ui/themes/styles.css'` in `app/globals.css`
with Radix's split files: `tokens/base.css`, `components.css` and
`utilities.css`.
- Import only the 7 color scales the site uses: `gray`, `sand` (gray
color), `iris` (accent color), `amber` (callouts), and `red`, `green`
and `yellow` (content separator labels).
- Kept the same import order as `styles.css`. I checked that every
selector in `styles.css` is still covered by the split files, apart from
the color scales we dropped on purpose.
- Added a comment saying any new Radix color has to be added to the
import list. Otherwise it renders unstyled.

Expected savings: about 23 KiB compressed from the main stylesheet,
roughly a quarter of it. This is a modest gain, likely tens of
milliseconds to first paint on mobile, not a big jump in score.

Preview:
https://sentry-docs-git-coolguyzone-perfradix-color-tokens.sentry.dev/

## 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>
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>
Follow-up to #19990: correct setup and verification across the base .NET
quick start and all 19 integration guides, checked against SDK 6.12.1.

Most setup inaccuracies predate the template migration. This also
corrects the new claim that `Sentry.Profiling` installs on .NET
Framework and adds the tracing option missing from the WinForms VB
examples.

- Fix package prerequisites, missing imports and terminators, ASP.NET
Core and MAUI compatibility guidance, EF6 application-lifetime disposal,
and the Google Cloud Functions user-factory interface.
- Separate AppKit/macOS initialization from iOS and Mac Catalyst, scope
Cocoa features to supported targets, and mark native tracing on Apple
and Android as opt-in through `Native.EnableTracing`.
- Use the OTLP exporter and OpenTelemetry sampling for the Blazor Server
example; remove duplicate logging registration from Blazor WebAssembly.
- Clarify which integration initializes Sentry, enable structured logs
where needed, and verify logging through the configured provider or
appender.
- Add shared verification steps for logs, metrics, and traces, including
manual transactions where sampling alone doesn't create tracing data.

Validation: 31 focused documentation tests and all applicable pre-commit
checks passed, including typo, external-link, and trailing-slash checks.
All 22 changed MDX files compiled through the repository pipeline with
website telemetry disabled in the temporary validation harness; shared
includes, JSON examples, and the new OTLP link resolved. The .NET SDK is
unavailable locally, so C#/VB snippets were source-checked but not
compiled or run.

## 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+

---------

Co-authored-by: Shannon Anahata <shannonanahata@gmail.com>
Co-authored-by: Ricardo Colombo Oliveira <github@ricoliv.com>
Co-authored-by: Alex Krawiec <alex.krawiec@sentry.io>
Co-authored-by: James Crosswell <jamescrosswell@users.noreply.github.com>
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>
sentry-junior Bot and others added 8 commits November 16, 2026 14:53
Bump to latest Sentry SDK version (11.12.0) so the site's own Sentry
instrumentation stays current.

<!-- junior-request-attribution:start -->
via @chargome.
<!-- junior-request-attribution:end -->

<!-- junior-session-footer:start -->
<!-- junior-conversation-id:slack%3AC092LQMHRJN%3A1794825914.751479 -->

--

[View
Session](https://junior-prod.sentry.dev/conversations/slack%3AC092LQMHRJN%3A1794825914.751479)
[[Sentry]](https://sentry.sentry.io/explore/conversations/slack%3AC092LQMHRJN%3A1794825914.751479/?project=4510944073809921)

<!-- junior-session-footer:end -->

Co-authored-by: sentry-junior[bot] <264270552+sentry-junior[bot]@users.noreply.github.com>
Co-authored-by: Charly Gomez <20254395+chargome@users.noreply.github.com>
)

Browser events still get dropped by ad blockers unless users write their
own tunnel, this is now shipped spread out v11.10~v11.13 releases
## DESCRIBE YOUR PR

Adds a .NET crons page for the new Quartz.NET packages: `Sentry.Quartz`
for Quartz.NET 4.x (`q.AddSentry()`) and `Sentry.Quartz3` for Quartz.NET
3.x (`SentryJobListener`). Jobs opt in with `[SentryMonitorSlug]`, and
the trigger's schedule is sent as the monitor config unless
`SendMonitorConfig` is turned off. The crons index links to it next to
Hangfire.

SDK PRs: getsentry/sentry-dotnet#5505,
getsentry/sentry-dotnet#5668

## IS YOUR CHANGE URGENT?

- [ ] Urgent deadline (GA date, etc.): YYYY-MM-DD
- [ ] Other deadline: YYYY-MM-DD
- [x] None: Not urgent, can wait up to 1 week+

---------

Co-authored-by: Claude <noreply@anthropic.com>
Co-authored-by: James Crosswell <jamescrosswell@users.noreply.github.com>
#20834)

## DESCRIBE YOUR PR

Adds an entry to the [Apple troubleshooting
page](https://docs.sentry.io/platforms/apple/troubleshooting/) for the
Xcode error users see since we revoked our Apple Distribution signing
certificate on November 13, 2026:

```txt
The signature of "Sentry.xcframework" cannot be validated and may have been compromised.
Validation Error: The signing certificate has been revoked (CSSMERR_TP_CERT_REVOKED)
```

It covers the pre-built binary products (`Sentry`, `Sentry-Dynamic`, and
others) from `9.34.0` and earlier, and points to the pinned
getsentry/sentry-cocoa#9645, which has the per-SDK fix (cocoa, React
Native, Dart).

The entry is the first one on the page.

## IS YOUR CHANGE URGENT?

- [x] Urgent deadline (GA date, etc.): ASAP
- [ ] Other deadline: YYYY-MM-DD
- [ ] 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 **Chris Aigner**.
<!-- junior-request-attribution:end -->

<!-- junior-session-footer:start -->
<!-- junior-conversation-id:slack%3AD0AQP8D75GR%3A1794850583.586679 -->

--

[View
Session](https://junior-prod.sentry.dev/conversations/slack%3AD0AQP8D75GR%3A1794850583.586679)
[[Sentry]](https://sentry.sentry.io/explore/conversations/slack%3AD0AQP8D75GR%3A1794850583.586679/?project=4510944073809921)

<!-- junior-session-footer:end -->

---------

Co-authored-by: sentry-junior[bot] <264270552+sentry-junior[bot]@users.noreply.github.com>
Co-authored-by: Chris Aigner <christoph.aigner@sentry.io>
## DESCRIBE YOUR PR

The .NET Quartz.NET Crons page now covers `MonitorAllJobs` and
`ExcludedJobs`, which monitor every scheduled job without the
`SentryMonitorSlug` attribute.

SDK PR: getsentry/sentry-dotnet#5741

Stacked on #19790.

## 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+

---------

Co-authored-by: Claude <noreply@anthropic.com>
Co-authored-by: James Crosswell <jamescrosswell@users.noreply.github.com>
…20706)

## DESCRIBE YOUR PR

The `prettier` and `eslint` hooks were local `language: node` hooks with
no `additional_dependencies`, so their environment never had either tool
installed. Under `prek`, any commit touching JS/TS fails with "No such
file or directory". `pre-commit` 4.6.1+ refuses to install them, and
older `pre-commit` 404s while downloading Node, because nodeenv took the
`node: "22"` pin literally. Details are in the issue.

Both tools are already dev dependencies, so the hooks now run them
through `pnpm exec` as `language: system` hooks, like `lychee` and
`trailing-slashes` already do. The `default_language_version` node pin
only existed for these two hooks, so it's gone.

This assumes `pnpm install` has been run, which the contributing guide
already requires.

Closes #20705

## 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>
<!-- Keep the urgency section so automation can prioritize this PR. You
may delete other sections you don't need. -->

## DESCRIBE YOUR PR

Documents automatic WebView trace propagation in the Cocoa SDK:
getsentry/sentry-cocoa#9538 adds the option, and
getsentry/sentry-cocoa#9539 exposes it through SentryObjC. It follows
#20399, which documented the manual
`SentryWebViewTracing.addTracePropagation` API.

- **Options page:** adds `webViewTracing` to Network & Performance
Options.
- **WebView page:** adds an "Automatic Trace Propagation" section:
  - Swift and Objective-C (SentryObjC) setup
- how the SDK keeps the injected trace current for links and reloads,
and why back/forward cache restores keep their trace
- the `enableSwizzling` requirement, and that manual calls keep their
own hosts
- a warning that the option reaches every `WKWebView`, including ones
created by other SDKs
- **Cross-links:** the snapshot alert and the SwiftUI `WebView(url:)`
note now point to the automatic option, which also covers
`WebView(url:)`.

Resolves getsentry/sentry-cocoa#9475 on the docs side.

⚠️ Please merge only after the Cocoa SDK release that ships
getsentry/sentry-cocoa#9538. The page assumes that release is `9.34.0`;
update the version if it ships in a different one.

## 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
- [x] 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)

## EXTRA RESOURCES

- [Sentry Docs contributor guide](https://docs.sentry.io/contributing/)
@vercel

vercel Bot commented Nov 17, 2026

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated
sentry-docs Ready Ready Preview Nov 17, 2026 8:31am UTC
1 Skipped Deployment
Project Deployment Actions Updated
develop-docs Ignored Ignored Nov 17, 2026 8:31am UTC

Request Review

@github-actions github-actions Bot added the sdk-develop-docs PRs touching develop-docs/sdk label Nov 17, 2026
@cursor

cursor Bot commented Nov 17, 2026

Copy link
Copy Markdown
Contributor

Getting ready to monitor this change · Rollout details

Status Service Environment
⏳ Getting ready to monitor this change

@github-actions github-actions Bot added the Priority: Needs Triage The PR description is missing valid priority information label Nov 17, 2026
@github-actions

Copy link
Copy Markdown
Contributor

Please update the IS YOUR CHANGE URGENT? section of the PR description:

  • Select exactly one option.
  • If you selected an urgent or other deadline, provide the date as YYYY-MM-DD.

This information helps the Docs team prioritize your review.

@codeowner-assignment
codeowner-assignment Bot requested review from a team, 0xadam-brown, NinjaLikesCheez, alwx, antonis, itaybre and romtsn and removed request for a team November 17, 2026 08:31
@adinauer
adinauer merged commit 42d8d27 into java-v9 Nov 17, 2026
24 checks passed

@cursor cursor Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Cursor Bugbot has reviewed your changes and found 1 potential issue.

Fix All in Cursor

❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.

Reviewed by Cursor Bugbot for commit d2895e9. Configure here.

Comment thread app/globals.css
@import '@radix-ui/themes/tokens/colors/yellow.css';
@import '@radix-ui/themes/tokens/base.css';
@import '@radix-ui/themes/components.css';
@import '@radix-ui/themes/utilities.css';

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Radix overlays missing alpha scales

Medium Severity

The Radix Themes import list adds only the semantic color scales in use and omits the black and white alpha scales. Those tokens back overlays, shadows, and scrims, so dropdowns, dialogs, and elevated surfaces can render with transparent or missing chrome.

Fix in Cursor Fix in Web

Reviewed by Cursor Bugbot for commit d2895e9. Configure here.

This branch was successfully deployed

1 active deployment
Production – sentry-docs — d2895e9b Deployed Nov 17, 2026 by vercel[bot]
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Priority: Needs Triage The PR description is missing valid priority information sdk-develop-docs PRs touching develop-docs/sdk

Projects

None yet

Development

Successfully merging this pull request may close these issues.