)

Document the Flutter v9-to-v10 migration with a dedicated full guide and
a companion interactive checklist, matching the JavaScript migration
experience. The guide covers platform requirements, removed APIs, and
telemetry behavior changes for v10.

Closes getsentry/sentry-dart#4023

## 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: Codex <noreply@openai.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 last bucket from the trailing-slash work in #19639 and #19675, which
covered only the user docs.

`develop-docs/` renders at **develop.sentry.dev** from the same Next
config, so the same rule applies — a link without a trailing slash is
served a 308 before the page loads:

```
https://develop.sentry.dev/backend/application-domains   -> 308
https://develop.sentry.dev/backend/application-domains/  -> 200
```

**240 links across 39 files**, produced by `pnpm
lint:trailing-slash:fix` from #19666. No hand edits.

### Verification

- Every changed file differs from master **only by added `/`
characters** — no slash removed, no external URL altered, no other
content touched
- A sample of 25 rewritten destinations all return **200** on
develop.sentry.dev
- `pnpm lint:trailing-slash` is now clean for `develop-docs/`

The 23 violations the linter still reports are drift in `docs/`, fixed
separately in #19811.

> Note: `AGENTS.md` describes `develop-docs/` as a submodule, but it
isn't one — `git submodule status` is empty and the directory has direct
commits in this repo. Worth correcting in that file at some point,
though I've left it out of this PR.

## 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 <noreply@anthropic.com>

Part of a series limiting crons `max_runtime` to 7 days (10080 minutes), down from 28 days, so in-progress check-ins stop changing after a bounded time.

Document the new limit where `max_runtime` is defined, and note in the SDK developer docs that monitor upserts clamp larger values.

Co-authored-by: sentry-api-schema-updater[bot] <271575301+sentry-api-schema-updater[bot]@users.noreply.github.com>

## DESCRIBE YOUR PR

The Python options page lists `functions_to_trace` as `list[str]` and
says each entry is a string with the function's fully qualified name.
The SDK actually expects `Sequence[Dict[str, str]]` and reads
`function["qualified_name"]` from each entry ([`client.py` @
2.71.0](https://github.com/getsentry/sentry-python/blob/2.71.0/sentry_sdk/client.py#L545-L547),
[`consts.py`](https://github.com/getsentry/sentry-python/blob/2.71.0/sentry_sdk/consts.py#L1356)).
If you pass plain strings, `sentry_sdk.init()` fails with `TypeError:
string indices must be integers`.

This changes the type to `list[dict[str, str]]` and describes the
`qualified_name` key. That matches the example already on the [custom
instrumentation
page](https://docs.sentry.io/platforms/python/tracing/instrumentation/custom-instrumentation/#define-span-creation-in-a-central-place).

## 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 **Ivana Kellyer**.
<!-- junior-request-attribution:end -->

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

--

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

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

Co-authored-by: sentry-junior[bot] <264270552+sentry-junior[bot]@users.noreply.github.com>
Co-authored-by: Ivana Kellyer <ivana.kellyer@sentry.io>

## DESCRIBE YOUR PR

The .NET metrics options say that setting `EnableMetrics` to `false`
disables the `SentrySdk.Metrics` APIs. That stopped being true in 6.10.0
([getsentry/sentry-dotnet#5509](getsentry/sentry-dotnet#5509)).
The option is now `[Obsolete]`, its getter always returns `true`, and
its setter does nothing ([`SentryOptions.cs` L640–657 @
6.12.0](https://github.com/getsentry/sentry-dotnet/blob/6.12.0/src/Sentry/SentryOptions.cs#L640-L657)).
Users who follow the current docs to opt out still send every metric.

This updates the description to say the option is ignored and points to
`SetBeforeSendMetric` (returning `null`) as the way to drop metrics.
That matches the SDK's own obsolete message.

## 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 **Ivana Kellyer**.
<!-- junior-request-attribution:end -->

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

--

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

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

Co-authored-by: sentry-junior[bot] <264270552+sentry-junior[bot]@users.noreply.github.com>
Co-authored-by: Ivana Kellyer <ivana.kellyer@sentry.io>

…tes (#19770)

The Statsig integration only records boolean gate evaluations, so
[experiment group assignments
](https://docs.statsig.com/experiments/overview)never reach Sentry.

Adding it to the integration would mean either encoding experiments as
fake boolean flags or waiting until the product renders non-boolean flag
values. Until then, this documents a small listener that records the
assigned group as a tag (for errors) and an attribute (for spans, logs,
and metrics).

Refs getsentry/sentry-javascript#22170

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>

…19820)

## DESCRIBE YOUR PR

The .NET logs docs say `EnableLogs = true` is required to use the
`SentrySdk.Logger` APIs. That stopped being true in 6.10.0
([getsentry/sentry-dotnet#5512](getsentry/sentry-dotnet#5512)).
The option now only controls logs captured by the logging integrations
(`Microsoft.Extensions.Logging`, Serilog, NLog, log4net). Logs created
directly through `SentrySdk.Logger` "are always sent"
([`SentryOptions.cs` L610–620 @
6.12.0](https://github.com/getsentry/sentry-dotnet/blob/6.12.0/src/Sentry/SentryOptions.cs#L610-L620)).

This removes the claim everywhere it appears in the .NET logs docs:
- **Options:** the plain .NET `EnableLogs` description now says it
controls integration-captured logs, not `SentrySdk.Logger`.
- **Options:** the `Microsoft.Extensions.Logging` filter note no longer
says `EnableLogs = true` "keeps the `SentrySdk.Logger` APIs available."
- **Setup:** the intro explains that `SentrySdk.Logger` needs no extra
configuration, and integrations need `EnableLogs = true`.
- **Setup (plain .NET):** the `SentrySdk.Init` snippet no longer sets
`EnableLogs`, and the note says you only need it with a logging
integration.
- **Setup (ASP.NET Core, AWS Lambda, Azure Functions, Blazor, MAUI):**
the note no longer says `EnableLogs` enables `SentrySdk.Logger`; it
enables the `Microsoft.Extensions.Logging` integration.
- **Usage:** the intro no longer says the feature must be enabled before
using `SentrySdk.Logger`.

Integration-based setup snippets still set `EnableLogs = true`, since
every integration path still requires it.

## 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 Junior system actor `event`.
<!-- junior-request-attribution:end -->

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

--

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

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

---------

Co-authored-by: sentry-junior[bot] <264270552+sentry-junior[bot]@users.noreply.github.com>
Co-authored-by: Ricardo Oliveira <ricardo.oliveira@sentry.io>

The Unreal SDK now propagates the `baggage` header together with
`sentry-trace`. Transactions and spans have a new `GetTraceHeaders()`
method for outgoing requests, and `ContinueTrace()` uses the incoming
`baggage` headers.

Updates the Unreal trace propagation page to match:

- Restructures it like the Unity and Android pages: extract incoming
tracing information, inject it into outgoing requests, and verify.
- Shows how to read `sentry-trace` and `baggage` from an HTTP response
and pass them to `ContinueTrace()`, including the `nullptr` check and
when it applies.
- Replaces `GetTrace()` with `GetTraceHeaders()` for outgoing requests.
- Notes the macOS and iOS limitation: only the sample rate and sample
rand are carried over from the incoming `baggage`.

## Related Items
- getsentry/sentry-unreal#1612
- getsentry/sentry-cocoa#8277

Co-authored-by: sentry-api-schema-updater[bot] <271575301+sentry-api-schema-updater[bot]@users.noreply.github.com>