Skip to content

chore(deps): update Java SDK to v8.65.0 - #2946

Open
github-actions[bot] wants to merge 1 commit into
mainfrom
deps/modules/sentry-java
Open

github-actions[bot] wants to merge 1 commit into
mainfrom
deps/modules/sentry-java

Conversation

@github-actions

Copy link
Copy Markdown
Contributor

Bumps modules/sentry-java from 8.64.0 to 8.65.0.

Auto-generated by a dependency updater.

Changelog

8.65.0

Features

  • Session Replay: Add Sentry.replay().pauseTouchTracking() and resumeTouchTracking() to stop recording touches on sensitive screens, such as a custom PIN pad, while the screen recording continues. Touch tracking stays paused until resumeTouchTracking() is called, also for new replays and after resume() (#6546)

Performance

  • Most SDK log calls no longer allocate when debug is off (#6600)

Behavioral Changes

  • Nav3: Returning to an Activity or Fragment with its own SentryNavEffect within the app (e.g., closing the Activity that covered it, swiping back to its ViewPager2 page, or dismissing a dialog over it) now starts a new navigation transaction for the current destination if the previous one finished, so spans produced upon return can now be consistently captured (#6482)
  • Nav3: ui.load transactions are bound to IScope in preference to Nav3 transactions when transitioning between Activities, matching Nav2 behavior (API 29+) (#6484)

Fixes

  • Session Replay: Fix Compose masking for Jetpack Compose 1.13. If the SDK can't walk the Compose tree of a screen, it now masks the whole Compose view instead of recording it unmasked (#6626)
  • Session Replay: Send Ktor client network request start and end times in milliseconds, so the requests line up with the replay (#6619)
  • Nav3: Stop attributing errors and spans from an Activity or ViewPager2 page without a SentryNavEffect to the most recently visited Nav3 root (#6483)
  • Android: Count deep sleep in breadcrumb, screenshot and view hierarchy debounce windows, so the first low-memory or battery breadcrumb after a long Doze is no longer dropped (#6590)
  • Android: Mark transactions and spans that finish after their deadline as deadline_exceeded, so ui.load transactions with TTID, TTFD or app start values that are hours long after a device sleep no longer report ok (#6599)
  • Android: Register network callbacks on API 24–25 when AndroidConnectionStatusProvider is created with a custom Handler, instead of failing because the Handler overload needs API 26 (#6634)

Dependencies

  • Bump OpenTelemetry (#6602)

    • OpenTelemetry to 1.67.0 (was 1.63.0)
    • OpenTelemetry Instrumentation to 2.33.1 (was 2.29.0)
    • OpenTelemetry Instrumentation Alpha to 2.33.1-alpha (was 2.29.0-alpha)
    • OpenTelemetry Semantic Conventions to 1.44.0 (was 1.42.0)
    • OpenTelemetry Semantic Conventions Alpha to 1.44.0-alpha (was 1.42.0-alpha)
    • OpenTelemetry 1.67 creates no-op spans when no SpanProcessor is configured. If you construct the OpenTelemetry SDK manually while using sentry-opentelemetry-otlp classes directly, configure a span processor. Without one, Sentry cannot inspect outgoing request URLs and may inject sentry-trace and baggage headers into destinations excluded by tracePropagationTargets. Standard OTLP exporter, Sentry Java agent, and agentless setups already configure one.
  • Keep the interrupt of the thread that calls Sentry.init when it is interrupted while the SDK waits for cached events to be sent after a startup crash (#6568)

  • On Android, the main thread may hang or trigger an ANR if the system is slow to register network or telephony callbacks during SDK initialization or when the app returns to the foreground. Fixed in 8.64.0 (#6537).

  • On Android, the main thread may hang or trigger an ANR if the system is slow to register network or telephony callbacks during SDK initialization or when the app returns to the foreground. Fixed in 8.64.0 (#6537).

  • On Android, the main thread may hang or trigger an ANR if the system is slow to register network or telephony callbacks during SDK initialization or when the app returns to the foreground. Fixed in 8.64.0 (#6537).

  • On Android, the main thread may hang or trigger an ANR if the system is slow to register network or telephony callbacks during SDK initialization or when the app returns to the foreground. Fixed in 8.64.0 (#6537).

  • On Android, the main thread may hang or trigger an ANR if the system is slow to register network or telephony callbacks during SDK initialization or when the app returns to the foreground. Fixed in 8.64.0 (#6537).

Full CHANGELOG.md diff
 -5,6 +5,40 
 > - Java 8 support will be dropped. SDK 9.0.0 requires Java 11+. See [#6469](https://github-redirect.dependabot.com/getsentry/sentry-java/issues/6469).
 > - The Android `minSdk` will be raised from 21 to 24. See [#5508](https://github-redirect.dependabot.com/getsentry/sentry-java/issues/5508).
 
+## 8.65.0
+
+### Features
+
+- Session Replay: Add `Sentry.replay().pauseTouchTracking()` and `resumeTouchTracking()` to stop recording touches on sensitive screens, such as a custom PIN pad, while the screen recording continues. Touch tracking stays paused until `resumeTouchTracking()` is called, also for new replays and after `resume()` ([#6546](https://github-redirect.dependabot.com/getsentry/sentry-java/pull/6546))
+
+### Performance
+
+- Most SDK log calls no longer allocate when `debug` is off ([#6600](https://github-redirect.dependabot.com/getsentry/sentry-java/pull/6600))
+
+### Behavioral Changes
+
+- Nav3: Returning to an Activity or Fragment with its own `SentryNavEffect` within the app (e.g., closing the Activity that covered it, swiping back to its ViewPager2 page, or dismissing a dialog over it) now starts a new navigation transaction for the current destination if the previous one finished, so spans produced upon return can now be consistently captured ([#6482](https://github-redirect.dependabot.com/getsentry/sentry-java/pull/6482))
+- Nav3: `ui.load` transactions are bound to `IScope` in preference to Nav3 transactions when transitioning between Activities, matching Nav2 behavior (API 29+) ([#6484](https://github-redirect.dependabot.com/getsentry/sentry-java/pull/6484))
+
+### Fixes
+
+- Session Replay: Fix Compose masking for Jetpack Compose 1.13. If the SDK can't walk the Compose tree of a screen, it now masks the whole Compose view instead of recording it unmasked ([#6626](https://github-redirect.dependabot.com/getsentry/sentry-java/pull/6626))
+- Session Replay: Send Ktor client network request start and end times in milliseconds, so the requests line up with the replay ([#6619](https://github-redirect.dependabot.com/getsentry/sentry-java/pull/6619))
+- Nav3: Stop attributing errors and spans from an Activity or ViewPager2 page without a `SentryNavEffect` to the most recently visited Nav3 root ([#6483](https://github-redirect.dependabot.com/getsentry/sentry-java/pull/6483))
+- Android: Count deep sleep in breadcrumb, screenshot and view hierarchy debounce windows, so the first low-memory or battery breadcrumb after a long Doze is no longer dropped ([#6590](https://github-redirect.dependabot.com/getsentry/sentry-java/pull/6590))
+- Android: Mark transactions and spans that finish after their deadline as `deadline_exceeded`, so `ui.load` transactions with TTID, TTFD or app start values that are hours long after a device sleep no longer report `ok` ([#6599](https://github-redirect.dependabot.com/getsentry/sentry-java/pull/6599))
+- Android: Register network callbacks on API 24–25 when `AndroidConnectionStatusProvider` is created with a custom `Handler`, instead of failing because the `Handler` overload needs API 26 ([#6634](https://github-redirect.dependabot.com/getsentry/sentry-java/pull/6634))
+
+### Dependencies
+
+- Bump OpenTelemetry ([#6602](https://github-redirect.dependabot.com/getsentry/sentry-java/pull/6602))
+  - OpenTelemetry to 1.67.0 (was 1.63.0)
+  - OpenTelemetry Instrumentation to 2.33.1 (was 2.29.0)
+  - OpenTelemetry Instrumentation Alpha to 2.33.1-alpha (was 2.29.0-alpha)
+  - OpenTelemetry Semantic Conventions to 1.44.0 (was 1.42.0)
+  - OpenTelemetry Semantic Conventions Alpha to 1.44.0-alpha (was 1.42.0-alpha)
+  - OpenTelemetry 1.67 creates no-op spans when no `SpanProcessor` is configured. If you construct the OpenTelemetry SDK manually while using `sentry-opentelemetry-otlp` classes directly, configure a span processor. Without one, Sentry cannot inspect outgoing request URLs and may inject `sentry-trace` and `baggage` headers into destinations excluded by `tracePropagationTargets`. Standard OTLP exporter, Sentry Java agent, and agentless setups already configure one.
+
 ## 8.64.0
 
 ### Breaking Changes
 -34,6 +68,7 
 
 ### Fixes
 
+- Keep the interrupt of the thread that calls `Sentry.init` when it is interrupted while the SDK waits for cached events to be sent after a startup crash ([#6568](https://github-redirect.dependabot.com/getsentry/sentry-java/pull/6568))
 - Capture scroll breadcrumbs for `LazyColumn`, `LazyRow`, lazy grids, and `Pager` on Jetpack Compose foundation 1.10+ ([#6548](https://github-redirect.dependabot.com/getsentry/sentry-java/pull/6548))
 - Prevent the main thread from potentially hanging during app start or when returning to the foreground if Android is slow to register the SDK's network or telephony listeners. `Sentry.init`, Session Replay, and capturing events no longer wait for that registration ([#6537](https://github-redirect.dependabot.com/getsentry/sentry-java/pull/6537))
 - Add opt-in support for matching GraphQL ignored error types against classification specifications via `sentry.graphql.enable-specification-error-type-filtering` ([#6092](https://github-redirect.dependabot.com/getsentry/sentry-java/pull/6092))
 -89,7 +124,7 
 
 ### Known Issues
 
-- On Android, the main thread may hang or trigger an ANR if the system is slow to register network or telephony callbacks during SDK initialization or when the app returns to the foreground. Fixed by [#6537](https://github-redirect.dependabot.com/getsentry/sentry-java/pull/6537).
+- On Android, the main thread may hang or trigger an ANR if the system is slow to register network or telephony callbacks during SDK initialization or when the app returns to the foreground. Fixed in `8.64.0` ([#6537](https://github-redirect.dependabot.com/getsentry/sentry-java/pull/6537)).
 
 ## 8.62.0
 
 -106,7 +141,7 
 
 ### Known Issues
 
-- On Android, the main thread may hang or trigger an ANR if the system is slow to register network or telephony callbacks during SDK initialization or when the app returns to the foreground. Fixed by [#6537](https://github-redirect.dependabot.com/getsentry/sentry-java/pull/6537).
+- On Android, the main thread may hang or trigger an ANR if the system is slow to register network or telephony callbacks during SDK initialization or when the app returns to the foreground. Fixed in `8.64.0` ([#6537](https://github-redirect.dependabot.com/getsentry/sentry-java/pull/6537)).
 
 ## 8.61.1
 
 -137,7 +172,7 
 
 ### Known Issues
 
-- On Android, the main thread may hang or trigger an ANR if the system is slow to register network or telephony callbacks during SDK initialization or when the app returns to the foreground. Fixed by [#6537](https://github-redirect.dependabot.com/getsentry/sentry-java/pull/6537).
+- On Android, the main thread may hang or trigger an ANR if the system is slow to register network or telephony callbacks during SDK initialization or when the app returns to the foreground. Fixed in `8.64.0` ([#6537](https://github-redirect.dependabot.com/getsentry/sentry-java/pull/6537)).
 
 ## 8.61.0
 
 -171,7 +206,7 
 
 ### Known Issues
 
-- On Android, the main thread may hang or trigger an ANR if the system is slow to register network or telephony callbacks during SDK initialization or when the app returns to the foreground. Fixed by [#6537](https://github-redirect.dependabot.com/getsentry/sentry-java/pull/6537).
+- On Android, the main thread may hang or trigger an ANR if the system is slow to register network or telephony callbacks during SDK initialization or when the app returns to the foreground. Fixed in `8.64.0` ([#6537](https://github-redirect.dependabot.com/getsentry/sentry-java/pull/6537)).
 
 ## 8.60.0
 
 -190,7 +225,7 
 
 ### Known Issues
 
-- On Android, the main thread may hang or trigger an ANR if the system is slow to register network or telephony callbacks during SDK initialization or when the app returns to the foreground. Fixed by [#6537](https://github-redirect.dependabot.com/getsentry/sentry-java/pull/6537).
+- On Android, the main thread may hang or trigger an ANR if the system is slow to register network or telephony callbacks during SDK initialization or when the app returns to the foreground. Fixed in `8.64.0` ([#6537](https://github-redirect.dependabot.com/getsentry/sentry-java/pull/6537)).
 
 ## 8.59.0
 

@bruno-garcia
bruno-garcia force-pushed the deps/modules/sentry-java branch from 81d8e6f to cfabb8c Compare November 18, 2026 03:01
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant