Skip to content

Conversation

@renovate
Copy link
Contributor

@renovate renovate bot commented Jan 5, 2026

Note: This PR body was truncated due to platform limits.

This PR contains the following updates:

Package Change Age Confidence
org.liquibase.ext:liquibase-hibernate6 (source) 4.31.14.33.0 age confidence
org.springdoc:springdoc-openapi-maven-plugin (source) 1.41.5 age confidence
org.jacoco:jacoco-maven-plugin (source) 0.8.130.8.14 age confidence
com.langfuse:langfuse-java (source) 0.0.60.1.2 age confidence
io.sentry:sentry-spring-boot-starter-jakarta 8.2.08.29.0 age confidence
org.keycloak:keycloak-admin-client (source) 26.0.426.0.8 age confidence
org.openapitools:jackson-databind-nullable 0.2.60.2.8 age confidence
com.squareup.okhttp3:logging-interceptor (source) 5.0.0-alpha.145.3.2 age confidence
org.openapitools:openapi-generator 7.11.07.18.0 age confidence
org.openapitools:openapi-generator-maven-plugin 7.11.07.18.0 age confidence
com.slack.api:bolt (source) 1.45.31.46.0 age confidence
io.nats:jnats 2.20.52.24.1 age confidence
io.hypersistence:hypersistence-utils-hibernate-63 3.9.23.14.1 age confidence
net.bytebuddy:byte-buddy-agent 1.17.51.18.3 age confidence
net.bytebuddy:byte-buddy 1.17.51.18.3 age confidence
org.postgresql:postgresql (source) 42.7.742.7.8 age confidence
org.codehaus.plexus:plexus-utils (source) 3.0.243.6.0 age confidence
org.springdoc:springdoc-openapi-starter-webmvc-ui (source) 2.8.52.8.15 age confidence
com.auth0:java-jwt 4.4.04.5.0 age confidence

📦 This PR was auto-generated by Renovate.

Review the changes, ensure CI passes, then merge.


Release Notes

liquibase/liquibase-hibernate (org.liquibase.ext:liquibase-hibernate6)

v4.33.0

Compare Source

Changes
🐛 Bug Fixes 🛠
🤖 Security Driver and Other Updates

Full Changelog: liquibase/liquibase-hibernate@v4.32.0...4.32.1

v4.32.0

Compare Source

Changes
🚀 New Features
🐛 Bug Fixes 🛠
🤖 Security Driver and Other Updates
11 changes

Full Changelog: liquibase/liquibase-hibernate@v4.31.1...4.31.2

springdoc/springdoc-openapi-maven-plugin (org.springdoc:springdoc-openapi-maven-plugin)

v1.5

Compare Source

jacoco/jacoco (org.jacoco:jacoco-maven-plugin)

v0.8.14: 0.8.14

Compare Source

New Features

  • JaCoCo now officially supports Java 25 (GitHub #​1950).
  • Experimental support for Java 26 class files (GitHub #​1870).
  • Branches added by the Kotlin compiler for default argument number 33 or higher are filtered out during generation of report (GitHub #​1655).
  • Part of bytecode generated by the Kotlin compiler for elvis operator that follows safe call operator is filtered out during generation of report (GitHub #​1814, #​1954).
  • Part of bytecode generated by the Kotlin compiler for more cases of chained safe call operators is filtered out during generation of report (GitHub #​1956).
  • Part of bytecode generated by the Kotlin compiler for invocations of suspendCoroutineUninterceptedOrReturn intrinsic is filtered out during generation of report (GitHub #​1929).
  • Part of bytecode generated by the Kotlin compiler for suspending lambdas with parameters is filtered out during generation of report (GitHub #​1945).
  • Part of bytecode generated by the Kotlin compiler for suspending functions and lambdas with suspension points that return inline value class is filtered out during generation of report (GitHub #​1871).
  • Part of bytecode generated by the Kotlin Compose compiler plugin for pausable composition is filtered out during generation of report (GitHub #​1911).
  • Methods generated by the Kotlin serialization compiler plugin are filtered out (GitHub #​1885, #​1970, #​1971).

Fixed bugs

  • Fixed handling of implicit else clause of when with String subject in Kotlin (GitHub #​1813, #​1940).
  • Fixed handling of implicit default clause of switch by String in Java when compiled by ECJ (GitHub #​1813, #​1940).
    Fixed handling of exceptions in chains of safe call operators in Kotlin (GitHub #​1819).

Non-functional Changes

  • JaCoCo now depends on ASM 9.9 (GitHub #​1965).
getsentry/sentry-java (io.sentry:sentry-spring-boot-starter-jakarta)

v8.29.0

Compare Source

Fixes
  • Support serialization of primitive arrays (boolean[], byte[], short[], char[], int[], long[], float[], double[]) (#​4968)
  • Session Replay: Improve network body parsing and truncation handling (#​4958)
Internal
  • Support metric envelope item type (#​4956)

v8.28.0

Compare Source

Features
  • Android: Flush logs when app enters background (#​4951)
  • Add option to capture additional OkHttp network request/response details in session replays (#​4919)
    • Depends on SentryOkHttpInterceptor to intercept the request and extract request/response bodies
    • To enable, add url regexes via the io.sentry.session-replay.network-detail-allow-urls metadata tag in AndroidManifest (code sample)
      • Or you can manually specify SentryReplayOptions via SentryAndroid#init:
        (Make sure you disable the auto init via manifest meta-data: io.sentry.auto-init=false)
Kotlin
SentryAndroid.init(
    this,
    options -> {
      // options.dsn = "https://[email protected]/0"
      // options.sessionReplay.sessionSampleRate = 1.0
      // options.sessionReplay.onErrorSampleRate = 1.0
      // ..

      options.sessionReplay.networkDetailAllowUrls = listOf(".*")
      options.sessionReplay.networkDetailDenyUrls = listOf(".*deny.*")
      options.sessionReplay.networkRequestHeaders = listOf("Authorization", "X-Custom-Header", "X-Test-Request")
      options.sessionReplay.networkResponseHeaders = listOf("X-Response-Time", "X-Cache-Status", "X-Test-Response")
    });
Java
SentryAndroid.init(
    this,
    options -> {
        options.getSessionReplay().setNetworkDetailAllowUrls(Arrays.asList(".*"));
        options.getSessionReplay().setNetworkDetailDenyUrls(Arrays.asList(".*deny.*"));
        options.getSessionReplay().setNetworkRequestHeaders(
            Arrays.asList("Authorization", "X-Custom-Header", "X-Test-Request"));
        options.getSessionReplay().setNetworkResponseHeaders(
            Arrays.asList("X-Response-Time", "X-Cache-Status", "X-Test-Response"));
    });
Improvements
  • Avoid forking rootScopes for Reactor if current thread has NoOpScopes (#​4793)
    • This reduces the SDKs overhead by avoiding unnecessary scope forks
Fixes
  • Fix missing thread stacks for ANRv1 events (#​4918)
  • Fix handling of unparseable mime-type on request filter (#​4939)
Internal
  • Support span envelope item type (#​4935)
Dependencies

v8.27.1

Compare Source

Fixes
  • Do not log if sentry.properties in rundir has not been found (#​4929)

v8.27.0

Compare Source

Features
  • Implement OpenFeature Integration that tracks Feature Flag evaluations (#​4910)
    • To make use of it, add the sentry-openfeature dependency and register the the hook using: openFeatureApiInstance.addHooks(new SentryOpenFeatureHook());
  • Implement LaunchDarkly Integrations that track Feature Flag evaluations (#​4917)
    • For Android, please add sentry-launchdarkly-android as a dependency and register the SentryLaunchDarklyAndroidHook
    • For Server / JVM, please add sentry-launchdarkly-server as a dependency and register the SentryLaunchDarklyServerHook
  • Detect oversized events and reduce their size (#​4903)
    • You can opt into this new behaviour by setting enableEventSizeLimiting to true (sentry.enable-event-size-limiting=true for Spring Boot application.properties)
    • You may optionally register an onOversizedEvent callback to implement custom logic that is executed in case an oversized event is detected
      • This is executed first and if event size was reduced sufficiently, no further truncation is performed
    • In case we detect an oversized event, we first drop breadcrumbs and if that isn't sufficient we also drop stack frames in order to get an events size down
Improvements
  • Do not send manual log origin (#​4897)
Dependencies

v8.26.0

Compare Source

Features
  • Add feature flags API (#​4812) and (#​4831)
    • You may now keep track of your feature flag evaluations and have them show up in Sentry.
    • Top level API (Sentry.addFeatureFlag("my-feature-flag", true);) writes to scopes and the current span (if there is one)
    • It is also possible to use API on IScope, IScopes, ISpan and ITransaction directly
    • Feature flag evaluations tracked on scope(s) will be added to any errors reported to Sentry.
      • The SDK keeps the latest 100 evaluations from scope(s), replacing old entries as new evaluations are added.
    • For feature flag evaluations tracked on spans:
      • Only 10 evaluations are tracked per span, existing flags are updated but new ones exceeding the limit are ignored
      • Spans do not inherit evaluations from their parent
  • Drop log events once buffer hits hard limit (#​4889)
    • If we have 1000 log events queued up, we drop any new logs coming in to prevent OOM
  • Remove vendored code and upgrade to async profiler 4.2 (#​4856)
    • This adds support for JDK 23+
Fixes
  • Removed SentryExecutorService limit for delayed scheduled tasks (#​4846)
  • Fix visual artifacts for the Canvas strategy on some devices (#​4861)
  • [Config] Trim whitespace on properties path (#​4880)
  • Only set DefaultReplayBreadcrumbConverter if replay is available (#​4888)
  • Session Replay: Cache connection status instead of using blocking calls (#​4891)
  • Fix log count in client reports (#​4869)
  • Fix profilerId propagation (#​4833)
  • Fix profiling init for Spring and Spring Boot w Agent auto-init (#​4815)
  • Copy active span on scope clone (#​4878)
Improvements
  • Fallback to distinct-id as user.id logging attribute when user is not set (#​4847)
  • Report Timber.tag() as timber.tag log attribute (#​4845)
  • Session Replay: Add screenshot strategy serialization to RRWeb events (#​4851)
  • Report discarded log bytes (#​4871)
  • Log why a properties file was not loaded (#​4879)
Dependencies

v8.25.0

Compare Source

Fixes
  • [ANR] Removed AndroidTransactionProfiler lock (#​4817)
  • Avoid ExecutorService for DefaultCompositePerformanceCollector timeout (#​4841)
    • This avoids infinite data collection for never stopped transactions, leading to OOMs
  • Fix wrong .super() call in SentryTimberTree (#​4844)
Improvements
  • [ANR] Defer some class availability checks (#​4825)
  • Collect PerformanceCollectionData only for sampled transactions (#​4834)
    • Breaking change: Transactions with a deferred sampling decision (sampled == null) won't be collecting any performance data anymore (CPU, RAM, slow/frozen frames).
Dependencies

v8.24.0

Compare Source

Features
  • Attach MDC properties to logs as attributes (#​4786)
    • MDC properties set using supported logging frameworks (Logback, Log4j2, java.util.Logging) are now attached to structured logs as attributes.
    • The attribute reflected on the log is mdc.<key>, where <key> is the original key in the MDC.
    • This means that you will be able to filter/aggregate logs in the product based on these properties.
    • Only properties with keys matching the configured contextTags are sent as log attributes.
      • You can configure which properties are sent using options.setContextTags if initalizing manually, or by specifying a comma-separated list of keys with a context-tags entry in sentry.properties or sentry.context-tags in application.properties.
      • Note that keys containing spaces are not supported.
  • Add experimental Sentry Android Distribution module for integrating with Sentry Build Distribution to check for and install updates (#​4804)
  • Allow passing a different Handler to SystemEventsBreadcrumbsIntegration and AndroidConnectionStatusProvider so their callbacks are deliver to that handler (#​4808)
  • Session Replay: Add new experimental Canvas Capture Strategy (#​4777)
    • A new screenshot capture strategy that uses Android's Canvas API for more accurate and reliable text and image masking
    • Any .drawText() or .drawBitmap() calls are replaced by rectangles, ensuring no text or images are present in the resulting output
    • Note: If this strategy is used, all text and images will be masked, regardless of any masking configuration
    • To enable this feature, set the screenshotStrategy, either via code:
      SentryAndroid.init(context) { options ->
        options.sessionReplay.screenshotStrategy = ScreenshotStrategyType.CANVAS
      }
      or AndroidManifest.xml:
      <application>
        <meta-data android:name="io.sentry.session-replay.screenshot-strategy" android:value="canvas" />
      </application>
Fixes
  • Avoid StrictMode warnings (#​4724)
  • Use logger from options for JVM profiler (#​4771)
  • Session Replay: Avoid deadlock when pausing replay if no connection (#​4788)
  • Session Replay: Fix capturing roots with no windows (#​4805)
  • Session Replay: Fix java.lang.IllegalArgumentException: width and height must be > 0 (#​4805)
  • Handle NoOpScopes in Context when starting a span through OpenTelemetry (#​4823)
    • This fixes "java.lang.IllegalArgumentException: The DSN is required" when combining WebFlux and OpenTelemetry
  • Session Replay: Do not use recycled screenshots for masking (#​4790)
    • This fixes native crashes seen in Canvas.<init>/ScreenshotRecorder.capture
  • Session Replay: Ensure bitmaps are recycled properly (#​4820)
Miscellaneous
  • Mark SentryClient(SentryOptions) constructor as not internal (#​4787)
Dependencies

v8.23.0

Compare Source

Features
  • Add session replay id to Sentry Logs (#​4740)
  • Add support for continuous profiling of JVM applications on macOS and Linux (#​4556)
    • Sentry continuous profiling on the JVM is using async-profiler under the hood.
    • By default this feature is disabled. Set a profile sample rate and chose a lifecycle (see below) to enable it.
    • Add the sentry-async-profiler dependency to your project
    • Set a sample rate for profiles, e.g. 1.0 to send all of them. You may use options.setProfileSessionSampleRate(1.0) in code or profile-session-sample-rate=1.0 in sentry.properties
    • Set a profile lifecycle via options.setProfileLifecycle(ProfileLifecycle.TRACE) in code or profile-lifecycle=TRACE in sentry.properties
      • By default the lifecycle is set to MANUAL, meaning you have to explicitly call Sentry.startProfiler() and Sentry.stopProfiler()
      • You may change it to TRACE which will create a profile for each transaction
    • To automatically upload Profiles for each transaction in a Spring Boot application
      • set sentry.profile-session-sample-rate=1.0 and sentry.profile-lifecycle=TRACE in application.properties
      • or set sentry.profile-session-sample-rate: 1.0 and sentry.profile-lifecycle: TRACE in application.yml
    • Profiling can also be combined with our OpenTelemetry integration
Fixes
  • Start performance collection on AppStart continuous profiling (#​4752)
  • Preserve modifiers in SentryTraced (#​4757)
Improvements
  • Handle RejectedExecutionException everywhere (#​4747)
  • Mark SentryEnvelope as not internal (#​4748)

v8.22.0

Compare Source

Features
Improvements
  • Remove internal API status from get/setDistinctId (#​4708)
  • Remove ApiStatus.Experimental annotation from check-in API (#​4721)
Fixes
  • Session Replay: Fix NoSuchElementException in BufferCaptureStrategy (#​4717)
  • Session Replay: Fix continue recording in Session mode after Buffer is triggered (#​4719)
Dependencies

v8.21.1

Compare Source

Fixes
  • Use Kotlin stdlib 1.9.24 dependency instead of 2.2.0 for all Android modules (#​4707)
    • This fixes compile time issues if your app is using Kotlin < 2.x

v8.21.0

Compare Source

Fixes
  • Only set log template for logging integrations if formatted message differs from template (#​4682)
Features
  • Add support for Spring Boot 4 and Spring 7 (#​4601)
    • NOTE: Our sentry-opentelemetry-agentless-spring is not working yet for Spring Boot 4. Please use sentry-opentelemetry-agent until OpenTelemetry has support for Spring Boot 4.
  • Replace UUIDGenerator implementation with Apache licensed code (#​4662)
  • Replace Random implementation with MIT licensed code (#​4664)
  • Add support for vars attribute in SentryStackFrame (#​4686)
    • Breaking change: The type of the vars attribute has been changed from Map<String, String> to Map<String, Object>.

v8.20.0

Compare Source

Fixes
  • Do not use named capturing groups for regular expressions (#​4652)
    • This fixes a crash on Android versions below 8.0 (API level 26)
Features
  • Add onDiscard to enable users to track the type and amount of data discarded before reaching Sentry (#​4612)
    • Stub for setting the callback on Sentry.init:
      Sentry.init(options -> {
        ...
        options.setOnDiscard(
         (reason, category, number) -> {
           // Your logic to process discarded data
         });
      });

v8.19.1

Compare Source

[!Warning]
Android: This release is incompatible with API levels below 26. We recommend using SDK version 8.20.0 or higher instead.

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.

v8.19.0

Compare Source

[!Warning]
Android: This release is incompatible with API levels below 26. We recommend using SDK version 8.20.0 or higher instead.

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

v8.18.0

Compare Source

Features
  • Add SentryUserFeedbackButton Composable (#​4559)
    • Also added Sentry.showUserFeedbackDialog static method
  • Add deadlineTimeout option (#​4555)
  • Add Ktor client integration (#​4527)
    • To use the integration, add a dependency on io.sentry:sentry-ktor-client, then install the SentryKtorClientPlugin on your HttpClient,
      e.g.:
      val client =
        HttpClient(Java) {
          install(io.sentry.ktorClient.SentryKtorClientPlugin) {
            captureFailedRequests = true
            failedRequestTargets = listOf(".*")
            failedRequestStatusCodes = listOf(HttpStatusCodeRange(500, 599))
          }
        }
Fixes
  • Allow multiple UncaughtExceptionHandlerIntegrations to be active at the same time (#​4462)
  • Prevent repeated scroll target determination during a single scroll gesture (#​4557)
    • This should reduce the number of ANRs seen in SentryGestureListener
  • Do not use Sentry logging API in JUL if logs are disabled (#​4574)
    • This was causing Sentry SDK to log warnings: "Sentry Log is disabled and this 'logger' call is a no-op."
  • Do not use Sentry logging API in Log4j2 if logs are disabled (#​4573)
    • This was causing Sentry SDK to log warnings: "Sentry Log is disabled and this 'logger' call is a no-op."
  • SDKs send queue is no longer shutdown immediately on re-init (#​4564)
    • This means we're no longer losing events that have been enqueued right before SDK re-init.
  • Reduce scope forking when using OpenTelemetry (#​4565)
    • Sentry.withScope now has the correct current scope passed to the callback. Previously our OpenTelemetry integration forked scopes an additional.
    • Overall the SDK is now forking scopes a bit less often.

v8.17.0

Compare Source

Features
  • Send Timber logs through Sentry Logs (#​4490)
    • Enable the Logs feature in your SentryOptions or with the io.sentry.logs.enabled manifest option and the SDK will automatically send Timber logs to Sentry, if the TimberIntegration is enabled.
    • The SDK will automatically detect Timber and use it to send logs to Sentry.
  • Send logcat through Sentry Logs (#​4487)
    • Enable the Logs feature in your SentryOptions or with the io.sentry.logs.enabled manifest option and the SDK will automatically send logcat logs to Sentry, if the Sentry Android Gradle plugin is applied.
    • To set the logcat level check the Logcat integration documentation.
  • Read build tool info from sentry-debug-meta.properties and attach it to events (#​4314)
Dependencies
  • Bump OpenTelemetry (#​4532)
    • opentelemetry-sdk to 1.51.0
    • opentelemetry-instrumentation to 2.17.0
    • opentelemetry-javaagent to 2.17.0
    • opentelemetry-semconv to 1.34.0
    • We are now configuring OpenTelemetry to still behave the same way it did before for span names it generates in GraphQL auto instrumentation (#​4537)
  • Bump Gradle from v8.14.2 to v8.14.3 (#​4540)
Fixes
  • Use Spring Boot Starter 3 in sentry-spring-boot-starter-jakarta (#​4545)
    • While refactoring our dependency management, we accidentally added Spring Boot 2 and Spring Boot Starter 2 as dependencies of sentry-spring-boot-starter-jakarta, which is intended for Spring Boot 3.
    • Now, the correct dependencies (Spring Boot 3 and Spring Boot Starter 3) are being added.

v8.16.0

Compare Source

Features
  • Send JUL logs to Sentry as logs (#​4518)
    • You need to enable the logs feature, either in sentry.properties:
      logs.enabled=true
    • Or, if you manually initialize Sentry, you may also enable logs on Sentry.init:
      Sentry.init(options -> {
        ...
        options.getLogs().setEnabled(true);
      });
    • It is also possible to set the minimumLevel in logging.properties, meaning any log message >= the configured level will be sent to Sentry and show up under Logs:
      io.sentry.jul.SentryHandler.minimumLevel=CONFIG
  • Send Log4j2 logs to Sentry as logs (#​4517)
    • You need to enable the logs feature either in sentry.properties:
      logs.enabled=true
    • If you manually initialize Sentry, you may also enable logs on Sentry.init:
      Sentry.init(options -> {
        ...
        options.getLogs().setEnabled(true);
      });
    • It is also possible to set the minimumLevel in log4j2.xml, meaning any log message >= the configured level will be sent to Sentry and show up under Logs:
      <Sentry name="Sentry"
          dsn="your DSN"
          minimumBreadcrumbLevel="DEBUG"
          minimumEventLevel="WARN"
          minimumLevel="DEBUG"
      />

v8.15.1

Compare Source

Fixes
  • Enabling Sentry Logs through Logback in Spring Boot config did not work in 3.15.0 (#​4523)

v8.15.0

Compare Source

Features
  • Add chipset to device context (#​4512)
Fixes
  • No longer send out empty log envelopes (#​4497)
  • Session Replay: Expand fix for crash on devices to all Unisoc/Spreadtrum chipsets (#​4510)
  • Log parameter objects are now turned into String via toString (#​4515)
    • One of the two SentryLogEventAttributeValue constructors did not convert the value previously.
  • Logs are now flushed on shutdown (#​4503)
  • User Feedback: Do not redefine system attributes for SentryUserFeedbackButton, but reference them instead (#​4519)
Features
  • Send Logback logs to Sentry as logs (#​4502)
    • You need to enable the logs feature and can also set the minimumLevel for log events:
      <appender name="sentry" class="io.sentry.logback.SentryAppender">
        <options>
          <!-- NOTE: Replace the test DSN below with YOUR OWN DSN to see the events from this app in your Sentry project/dashboard -->
          <dsn>https://502f25099c204a2fbf4cb16edc5975d1@&#8203;o447951.ingest.sentry.io/5428563</dsn>
          <logs>
            <enabled>true</enabled>
          </logs>
        </options>
        <!-- Demonstrates how to modify the minimum values -->
        <!-- Default for Events is ERROR -->
        <minimumEventLevel>WARN</minimumEventLevel>
        <!-- Default for Breadcrumbs is INFO -->
        <minimumBreadcrumbLevel>DEBUG</minimumBreadcrumbLevel>
        <!-- Default for Log Events is INFO -->
        <minimumLevel>INFO</minimumLevel>
      </appender>
    • For Spring Boot you may also enable it in application.properties / application.yml:
      sentry.logs.enabled=true
      sentry.logging.minimum-level=error
    • If you manually initialize Sentry, you may also enable logs on Sentry.init:
      Sentry.init(options -> {
        ...
        options.getLogs().setEnabled(true);
      });
    • Enabling via sentry.properties is also possible:
      logs.enabled=true
  • Automatically use SentryOptions.Logs.BeforeSendLogCallback Spring beans (#​4509)
Dependencies

v8.14.0

Compare Source

Fixes
  • Fix Session Replay masking for newer versions of Jetpack Compose (1.8+) (#​4485)
Features
  • Add New User Feedback Widget (#​4450)
    • This widget is a custom button that can be used to show the user feedback form
  • Add New User Feedback form (#​4384)
    • We now introduce SentryUserFeedbackDialog, which extends AlertDialog, inheriting the show() and cancel() methods, among others.
      To use it, just instantiate it and call show() on the instance (Sentry must be previously initialized).
      For customization options, please check the User Feedback documentation.
      import io.sentry.android.core.SentryUserFeedbackDialog;
      
      new SentryUserFeedbackDialog.Builder(context).create().show();
      import io.sentry.android.core.SentryUserFeedbackDialog
      
      SentryUserFeedbackDialog.Builder(context).create().show()
  • Add user.id, user.name and user.email to log attributes (#​4486)
  • User name attribute has been deprecated, please use username instead (#​4486)
  • Add device (device.brand, device.model and device.family) and OS (os.name and os.version) attributes to logs (#​4493)
  • Serialize preContext and postContext in SentryStackFrame (#​4482)
Internal
  • User Feedback now uses SentryUser.username instead of SentryUser.name (#​4494)

v8.13.3

Compare Source

Fixes
  • Send UI Profiling app start chunk when it finishes (#​4423)
  • Republish Javadoc #​4457
  • Finalize OkHttpEvent even if no active span in SentryOkHttpInterceptor #​4469
  • Session Replay: Do not capture current replay for cached events from the past (#​4474)
  • Session Replay: Correctly capture Dialogs and non full-sized windows (#​4354)
  • Session Replay: Fix inconsistent segment_id (#​4471)
  • Session Replay: Fix crash on devices with the Unisoc/Spreadtrum T606 chipset (#​4477)

v8.13.2

Compare Source

Fixes
  • Don't apply Spring Boot plugin in sentry-spring-boot-jakarta (#​4456)
    • The jar for `

Configuration

📅 Schedule: Branch creation - "before 9am on Monday" in timezone Europe/Berlin, Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate renovate bot added the application-server Spring Boot server: APIs, business logic, database label Jan 5, 2026
@renovate renovate bot requested a review from a team as a code owner January 5, 2026 04:56
@renovate renovate bot added dependencies Package updates, version bumps, lock file changes application-server Spring Boot server: APIs, business logic, database labels Jan 5, 2026
@renovate renovate bot enabled auto-merge (squash) January 5, 2026 04:56
@renovate renovate bot added the dependencies Package updates, version bumps, lock file changes label Jan 5, 2026
@coderabbitai
Copy link
Contributor

coderabbitai bot commented Jan 5, 2026

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.


Comment @coderabbitai help to get the list of available commands and usage tips.

@github-actions github-actions bot added size:M This PR changes 30-99 lines, ignoring generated files. bug Something isn't working labels Jan 5, 2026
@renovate renovate bot force-pushed the renovate/java-dependencies branch from d013cb3 to b1005e0 Compare January 12, 2026 16:38
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

application-server Spring Boot server: APIs, business logic, database bug Something isn't working dependencies Package updates, version bumps, lock file changes size:M This PR changes 30-99 lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant