Skip to content
This repository was archived by the owner on Aug 21, 2025. It is now read-only.

Conversation

dependabot[bot]
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Aug 13, 2025

Bumps io.sentry:sentry-spring-boot-starter-jakarta from 8.17.0 to 8.19.1.

Release notes

Sourced from io.sentry:sentry-spring-boot-starter-jakarta's releases.

8.19.1

Fixes

  • Do not store No-Op scopes onto OpenTelemetry Context when wrapping (#4631)
    • In 8.18.0 and 8.19.0 the SDK could break when initialized too late.

8.19.0

Features

  • Add a isEnableSystemEventBreadcrumbsExtras option to disable reporting system events extras for breadcrumbs (#4625)

Improvements

  • Session Replay: Use main thread looper to schedule replay capture (#4542)
  • Use single LifecycleObserver and multi-cast it to the integrations interested in lifecycle states (#4567)
  • Add sentry.origin attribute to logs (#4618)
    • This helps identify which integration captured a log event
  • Prewarm SentryExecutorService for better performance at runtime (#4606)

Fixes

  • Cache network capabilities and status to reduce IPC calls (#4560)
  • Deduplicate battery breadcrumbs (#4561)
  • Remove unused method in ManifestMetadataReader (#4585)
  • Have single NetworkCallback registered at a time to reduce IPC calls (#4562)
  • Do not register for SystemEvents and NetworkCallbacks immediately when launched with non-foreground importance (#4579)
  • Limit ProGuard keep rules for native methods within sentry-android-ndk to the io.sentry.** namespace. (#4427)
    • If you relied on the Sentry SDK to keep native method names for JNI compatibility within your namespace, please review your ProGuard rules and ensure the configuration still works. Especially when you're not consuming any of the default Android proguard rules (proguard-android.txt or proguard-android-optimize.txt) the following config should be present:
    -keepclasseswithmembernames class * {
      native <methods>;
    }
    
  • Fix abstract method error in SentrySupportSQLiteDatabase (#4597)
  • Ensure frame metrics listeners are registered/unregistered on the main thread (#4582)
  • Do not report cached events as lost (#4575)
    • Previously events were recorded as lost early despite being retried later through the cache
  • Move and flush unfinished previous session on init (#4624)
    • This removes the need for unnecessary blocking our background queue for 15 seconds in the case of a background app start
  • Switch to compileOnly dependency for compose-ui-material (#4630)
    • This fixes StackOverflowError when using OSS Licenses plugin

Dependencies

8.18.0

Features

... (truncated)

Changelog

Sourced from io.sentry:sentry-spring-boot-starter-jakarta's changelog.

8.19.1

Fixes

  • Do not store No-Op scopes onto OpenTelemetry Context when wrapping (#4631)
    • In 8.18.0 and 8.19.0 the SDK could break when initialized too late.

8.19.0

Features

  • Add a isEnableSystemEventBreadcrumbsExtras option to disable reporting system events extras for breadcrumbs (#4625)

Improvements

  • Session Replay: Use main thread looper to schedule replay capture (#4542)
  • Use single LifecycleObserver and multi-cast it to the integrations interested in lifecycle states (#4567)
  • Add sentry.origin attribute to logs (#4618)
    • This helps identify which integration captured a log event
  • Prewarm SentryExecutorService for better performance at runtime (#4606)

Fixes

  • Cache network capabilities and status to reduce IPC calls (#4560)
  • Deduplicate battery breadcrumbs (#4561)
  • Remove unused method in ManifestMetadataReader (#4585)
  • Have single NetworkCallback registered at a time to reduce IPC calls (#4562)
  • Do not register for SystemEvents and NetworkCallbacks immediately when launched with non-foreground importance (#4579)
  • Limit ProGuard keep rules for native methods within sentry-android-ndk to the io.sentry.** namespace. (#4427)
    • If you relied on the Sentry SDK to keep native method names for JNI compatibility within your namespace, please review your ProGuard rules and ensure the configuration still works. Especially when you're not consuming any of the default Android proguard rules (proguard-android.txt or proguard-android-optimize.txt) the following config should be present:
    -keepclasseswithmembernames class * {
      native <methods>;
    }
    
  • Fix abstract method error in SentrySupportSQLiteDatabase (#4597)
  • Ensure frame metrics listeners are registered/unregistered on the main thread (#4582)
  • Do not report cached events as lost (#4575)
    • Previously events were recorded as lost early despite being retried later through the cache
  • Move and flush unfinished previous session on init (#4624)
    • This removes the need for unnecessary blocking our background queue for 15 seconds in the case of a background app start
  • Switch to compileOnly dependency for compose-ui-material (#4630)
    • This fixes StackOverflowError when using OSS Licenses plugin

Dependencies

... (truncated)

Commits
  • 3a18a9e release: 8.19.1
  • 90fa855 Do not store No-Op scopes onto OpenTelemetry Context when wrapping (#4631)
  • 1cdca11 Fix agent JAR lookup (#4633)
  • d5ff4e5 Merge branch 'release/8.19.0'
  • b160f57 release: 8.19.0
  • 73a2923 chore(breadcrumbs): Add an option to disable reporting system events extras f...
  • 5625283 fix(sessions): Move and flush unfinished previous session on init (#4624)
  • 7f16a2c fix(compose): Switch to compileOnly dependency for compose-ui-material (#4630)
  • 4d4e343 chore: update scripts/update-sentry-native-ndk.sh to 0.10.0 (#4623)
  • 33a1039 build(deps): bump gradle/actions from 4.4.1 to 4.4.2 (#4629)
  • Additional commits viewable in compare view

Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot merge will merge this PR after your CI passes on it
  • @dependabot squash and merge will squash and merge this PR after your CI passes on it
  • @dependabot cancel merge will cancel a previously requested merge and block automerging
  • @dependabot reopen will reopen this PR if it is closed
  • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
  • @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

Bumps [io.sentry:sentry-spring-boot-starter-jakarta](https://github.com/getsentry/sentry-java) from 8.17.0 to 8.19.1.
- [Release notes](https://github.com/getsentry/sentry-java/releases)
- [Changelog](https://github.com/getsentry/sentry-java/blob/main/CHANGELOG.md)
- [Commits](getsentry/sentry-java@8.17.0...8.19.1)

---
updated-dependencies:
- dependency-name: io.sentry:sentry-spring-boot-starter-jakarta
  dependency-version: 8.19.1
  dependency-type: direct:production
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <[email protected]>
@dependabot dependabot bot added the dependencies Pull requests that update a dependency file label Aug 13, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
dependencies Pull requests that update a dependency file
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants