From 786a72e6646bd2bbad4a3b272f0de687ae007f81 Mon Sep 17 00:00:00 2001 From: Alexander Dinauer Date: Wed, 23 Sep 2026 16:51:32 +0200 Subject: [PATCH] docs: Warn about sendDefaultPii removal Make the upcoming removal visible in the data collection changelog entry so customers know to migrate before the next major SDK version. Co-Authored-By: Claude --- CHANGELOG.md | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/CHANGELOG.md b/CHANGELOG.md index e59606e335c..26aa987e7cf 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -6,7 +6,11 @@ - Add `LocalSentrySpan` to `sentry-compose` so apps can provide a parent `ISpan` to a composable subtree and have nested `SentryTraced` spans attach to it ([#6112]https://github.com/getsentry/sentry-java/pull/6112) - Add `dataCollection`, a fine-grained replacement for `sendDefaultPii`, for controlling data collected automatically by SDK integrations ([#5759](https://github.com/getsentry/sentry-java/pull/5759)) - - `sendDefaultPii` remains supported for backwards compatibility. When `dataCollection` is not configured, the SDK preserves the existing `sendDefaultPii` behavior. + + > [!WARNING] + > `sendDefaultPii` will be removed in the next major SDK version. Migrate to `dataCollection` before upgrading. + + - Until then, when `dataCollection` is not configured, the SDK preserves the existing `sendDefaultPii` behavior. - Configuring any `dataCollection` option makes it the source of truth. `sendDefaultPii` is then ignored, and omitted `dataCollection` options use the defaults below. - The Logback appender is a compatibility exception. When an encoder is configured, `sendDefaultPii=true` continues to include the original message template and parameters. To opt in independently of `sendDefaultPii`, set `true` on the Sentry appender in `logback.xml` or `logback-spring.xml`. - Data explicitly supplied through APIs such as `Sentry.setUser`, scopes, event processors, or `beforeSend` is not affected.