Skip to content

Update all dependencies - autoclosed#165

Closed
renovate[bot] wants to merge 1 commit intomasterfrom
renovate/all
Closed

Update all dependencies - autoclosed#165
renovate[bot] wants to merge 1 commit intomasterfrom
renovate/all

Conversation

@renovate
Copy link
Contributor

@renovate renovate bot commented Feb 11, 2025

This PR contains the following updates:

Package Type Update Change Age Confidence
actions/checkout action major v4 -> v5 age confidence
actions/setup-java action major v4 -> v5 age confidence
gradle (source) major 8.12.1 -> 9.0.0 age confidence
com.eternalcode:eternalcode-commons-shared dependencies minor 1.2.0 -> 1.3.1 age confidence
org.apache.commons:commons-lang3 (source) dependencies minor 3.17.0 -> 3.18.0 age confidence
org.mockito:mockito-junit-jupiter dependencies minor 5.15.2 -> 5.19.0 age confidence
org.mockito:mockito-core dependencies minor 5.15.2 -> 5.19.0 age confidence
com.squareup.okhttp3:okhttp (source) dependencies major 4.12.0 -> 5.1.0 age confidence
com.squareup.okhttp3:mockwebserver (source) dependencies major 4.12.0 -> 5.1.0 age confidence
org.junit.jupiter:junit-jupiter-engine (source) dependencies minor 5.11.4 -> 5.13.4 age confidence
org.junit.jupiter:junit-jupiter-api (source) dependencies minor 5.11.4 -> 5.13.4 age confidence
com.google.code.gson:gson dependencies minor 2.12.1 -> 2.13.2 age confidence
org.mariadb.jdbc:mariadb-java-client (source) dependencies patch 3.5.1 -> 3.5.6 age confidence
com.zaxxer:HikariCP dependencies major 6.2.1 -> 7.0.2 age confidence
io.sentry:sentry dependencies minor 8.1.0 -> 8.21.1 age confidence
ch.qos.logback:logback-classic (source, changelog) dependencies patch 1.5.16 -> 1.5.18 age confidence
net.dzikoysk:cdn dependencies patch 1.14.6 -> 1.14.9 age confidence
net.dv8tion:JDA dependencies minor 5.3.0 -> 5.6.1 age confidence

Release Notes

actions/checkout (actions/checkout)

v5

Compare Source

actions/setup-java (actions/setup-java)

v5

Compare Source

gradle/gradle (gradle)

v9.0.0: 9.0.0

Compare Source

The Gradle team is excited to announce Gradle 9.0.0.

Here are the highlights of this release:

  • Configuration Cache is the recommended execution mode
  • Gradle requires JVM 17 or higher to run
  • Build scripts use Kotlin 2.2 and Groovy 4.0
  • Improved Kotlin DSL script compilation avoidance

Read the Release Notes

We would like to thank the following community members for their contributions to this release of Gradle:
Aaron Matthis,
Adam E,
Adam S,
Björn Kautler,
Daniel Lacasse,
Eng Zer Jun,
EunHyunsu,
FlorianMichael,
Francisco Prieto,
Gaëtan Muller,
Jake Wharton,
Kengo TODA,
Kent Kaseda,
Madalin Valceleanu,
Marc Philipp,
Mark S. Lewis,
Matthew Haughton,
Mycroft Wong,
Na Minhyeok,
Nelson Osacky,
Olivier "Oli" Dagenais,
ploober,
Radai Rosenblatt,
Róbert Papp,
Sebastian Schuberth,
Victor Merkulov.

Upgrade instructions

Switch your build to use Gradle 9.0.0 by updating your wrapper:

./gradlew wrapper --gradle-version=9.0.0 && ./gradlew wrapper

See the Gradle 9.0.0 upgrade guide to learn about deprecations, breaking changes and other considerations when upgrading.

For Java, Groovy, Kotlin and Android compatibility, see the full compatibility notes.

Reporting problems

If you find a problem with this release, please file a bug on GitHub Issues adhering to our issue guidelines.
If you're not sure you're encountering a bug, please use the forum.

We hope you will build happiness with Gradle, and we look forward to your feedback via Twitter or on GitHub.

v8.14.3: 8.14.3

Compare Source

The Gradle team is excited to announce Gradle 8.14.3.

This is a patch release for 8.14. We recommend using 8.14.3 instead of 8.14.

Here are the highlights of this release:

  • Java 24 support
  • GraalVM Native Image toolchain selection
  • Enhancements to test reporting
  • Build Authoring improvements

Read the Release Notes

We would like to thank the following community members for their contributions to this release of Gradle:
Aurimas,
Ben Bader,
Björn Kautler,
chandre92,
Daniel Hammer,
Danish Nawab,
Florian Dreier,
Ivy Chen,
Jendrik Johannes,
jimmy1995-gu,
Madalin Valceleanu,
Na Minhyeok.

Upgrade instructions

Switch your build to use Gradle 8.14.3 by updating your wrapper:

./gradlew wrapper --gradle-version=8.14.3 && ./gradlew wrapper

See the Gradle 8.x upgrade guide to learn about deprecations, breaking changes and other considerations when upgrading.

For Java, Groovy, Kotlin and Android compatibility, see the full compatibility notes.

Reporting problems

If you find a problem with this release, please file a bug on GitHub Issues adhering to our issue guidelines.
If you're not sure you're encountering a bug, please use the forum.

We hope you will build happiness with Gradle, and we look forward to your feedback via Twitter or on GitHub.

v8.14.2

Compare Source

v8.14.1

Compare Source

v8.14

Compare Source

v8.13

Compare Source

mockito/mockito (org.mockito:mockito-junit-jupiter)

v5.19.0

Compare Source

Changelog generated by Shipkit Changelog Gradle Plugin

5.19.0
  • 2025-08-15 - 37 commit(s) by Adrian-Kim, Tim van der Lippe, Tran Ngoc Nhan, dependabot[bot], juyeop
  • feat: Add support for JDK21 Sequenced Collections. (#​3708)
  • Bump actions/checkout from 4 to 5 (#​3707)
  • build: Allow overriding 'Created-By' for reproducible builds (#​3704)
  • Bump org.assertj:assertj-core from 3.27.3 to 3.27.4 (#​3703)
  • Bump androidx.test:runner from 1.6.2 to 1.7.0 (#​3697)
  • Bump org.junit.platform:junit-platform-launcher from 1.13.3 to 1.13.4 (#​3694)
  • Bump com.diffplug.spotless:spotless-plugin-gradle from 7.1.0 to 7.2.1 (#​3693)
  • Bump junit-jupiter from 5.13.3 to 5.13.4 (#​3691)
  • Bump com.gradle.develocity from 4.0.2 to 4.1 (#​3689)
  • Bump com.google.googlejavaformat:google-java-format from 1.27.0 to 1.28.0 (#​3688)
  • Bump com.google.googlejavaformat:google-java-format from 1.25.2 to 1.27.0 (#​3686)
  • Bump com.diffplug.spotless:spotless-plugin-gradle from 7.0.4 to 7.1.0 (#​3685)
  • Bump junit-jupiter from 5.13.2 to 5.13.3 (#​3684)
  • Bump org.shipkit:shipkit-auto-version from 2.1.0 to 2.1.2 (#​3683)
  • Bump com.diffplug.spotless:spotless-plugin-gradle from 7.0.2 to 7.0.4 (#​3682)
  • Only run release after both Java and Android tests have finished
    (#​3681)
  • Bump org.junit.platform:junit-platform-launcher from 1.12.2 to 1.13.3 (#​3680)
  • Bump org.codehaus.groovy:groovy from 3.0.24 to 3.0.25 (#​3679)
  • Bump org.eclipse.platform:org.eclipse.osgi from 3.23.0 to 3.23.100 (#​3678)
  • Can no longer publish snapshot releases (#​3677)
  • Update Gradle to 8.14.2 (#​3676)
  • Bump errorprone from 2.23.0 to 2.39.0 (#​3674)
  • Correct Junit docs link (#​3672)
  • Bump net.ltgt.gradle:gradle-errorprone-plugin from 4.1.0 to 4.3.0 (#​3670)
  • Bump junit-jupiter from 5.13.1 to 5.13.2 (#​3669)
  • Bump bytebuddy from 1.17.5 to 1.17.6 (#​3668)
  • Bump junit-jupiter from 5.12.2 to 5.13.1 (#​3666)
  • Bump org.jetbrains.kotlin:kotlin-stdlib from 2.0.21 to 2.2.0 (#​3665)
  • Bump org.gradle.toolchains.foojay-resolver-convention from 0.9.0 to 1.0.0 (#​3661)
  • Bump org.junit.platform:junit-platform-launcher from 1.11.4 to 1.12.2 (#​3660)
  • Add JDK21 sequenced collections for ReturnsEmptyValues (#​3659)
  • Bump com.gradle.develocity from 3.19.1 to 4.0.2 (#​3658)
  • Bump ru.vyarus:gradle-animalsniffer-plugin from 1.7.2 to 2.0.1 (#​3657)
  • Bump org.eclipse.platform:org.eclipse.osgi from 3.22.0 to 3.23.0 (#​3656)
  • Bump org.codehaus.groovy:groovy from 3.0.23 to 3.0.24 (#​3655)
  • Bump junit-jupiter from 5.11.4 to 5.12.2 (#​3653)
  • Reproducible Build: need to inject JDK distribution details to rebuild (#​3563)

v5.18.0

Compare Source

Changelog generated by Shipkit Changelog Gradle Plugin

5.18.0
  • 2025-05-20 - 5 commit(s) by Eugene Platonov, Patrick Doyle, Tim van der Lippe, dependabot[bot]
  • Make vararg checks Scala friendly (for mockito-scala) (#​3651)
  • For UnfinishedStubbingException, suggest the possibility of another thread (#​3636)
  • UnfinishedStubbingException ought to suggest the possibility of another thread (#​3635)

v5.17.0

Changelog generated by Shipkit Changelog Gradle Plugin

5.17.0
  • 2025-04-04 - 7 commit(s) by Adrian Roos, Andre Kurait, Jan Ouwens, Rafael Winterhalter, Taeik Lim, Thach Le, Tim van der Lippe
  • Fixes #​3631: Fix broken banner image link (#​3632)
  • Banner image is broken (#​3631)
  • Update exception message with mockito-inline (#​3628)
  • Clarify structure of commit messages (#​3626)
  • Fixes #​3622: MockitoExtension fails cleanup when aborted before setup (#​3623)
  • MockitoExtension fails cleanup when aborted before setup (#​3622)
  • Since mockito-inline has been removed, the exception messages with mockito-inline should be modified. (#​3621)
  • Fixes #​3171: Fall back to Throwable Location strategy on Android (#​3619)
  • Fixes #​3615 : broken links to javadoc.io (#​3616)
  • Broken links to javadoc.io (#​3615)
  • Mocks are not working on particular devices after update Android SDK from 33 to 34 (#​3171)

v5.16.1

Compare Source

Changelog generated by Shipkit Changelog Gradle Plugin

5.16.1
  • 2025-03-15 - 3 commit(s) by Adrian Roos, Jérôme Prinet, Rafael Winterhalter
  • Remove Arrays.asList from critical stubbing path in GenericMetadataSu… (#​3610)
  • Rework of injection strategy in the context of modules (#​3608)
  • Adjust inline mocking snippet to allow task relocatability (#​3606)
  • Inline mocking configuration snippet for Gradle should allow task relocatability (#​3605)

v5.16.0

Changelog generated by Shipkit Changelog Gradle Plugin

5.16.0
  • 2025-03-03 - 10 commit(s) by Brice Dutheil, Rafael Winterhalter, TDL, dependabot[bot]
  • Add support for including module-info in Mockito. (#​3597)
  • Bump com.gradle.develocity from 3.19 to 3.19.1 (#​3579)
  • Bump org.assertj:assertj-core from 3.27.2 to 3.27.3 (#​3577)
  • Bump com.diffplug.spotless:spotless-plugin-gradle from 7.0.1 to 7.0.2 (#​3574)
  • Bump com.diffplug.spotless:spotless-plugin-gradle from 6.25.0 to 7.0.1 (#​3571)
  • Bump org.assertj:assertj-core from 3.27.1 to 3.27.2 (#​3569)
  • Tweaks documentation on mockito agent config for maven (#​3568)
  • Adds --info to diagnose closeAndReleaseStagingRepositories issues (#​3567)
  • Refine reflection when calling management factory (#​3566)
  • Avoid warning when dynamic attach is enabled (#​3551)
square/okhttp (com.squareup.okhttp3:okhttp)

v5.1.0

2025-07-07

  • New: Response.peekTrailers(). When we changed Response.trailers() to block instead of
    throwing in 5.0.0, we inadvertently removed the ability for callers to peek the trailers
    (by catching the IllegalStateException if they weren't available). This new API restores that
    capability.

  • Fix: Don't crash on trailers() if the response doesn't have a body. We broke [Retrofit] users
    who read the trailers on the raw() OkHttp response, after its body was decoded.

v5.0.0

2025-07-02

This is our first stable release of OkHttp since 2023. Here's the highlights if you're upgrading
from OkHttp 4.x:

OkHttp is now packaged as separate JVM and Android artifacts. This allows us to offer
platform-specific features and optimizations. If your build system handles [Gradle module metadata],
this change should be automatic.

MockWebServer has a new coordinate and package name. We didn’t like that our old artifact
depends on JUnit 4 so the new one doesn’t. It also has a better API built on immutable values. (We
intend to continue publishing the old okhttp3.mockwebserver artifact so there’s no urgency to
migrate.)

Coordinate Package Name Description
com.squareup.okhttp3:mockwebserver3:5.0.0 mockwebserver3 Core module. No JUnit dependency!
com.squareup.okhttp3:mockwebserver3-junit4:5.0.0 mockwebserver3.junit4 Optional JUnit 4 integration.
com.squareup.okhttp3:mockwebserver3-junit5:5.0.0 mockwebserver3.junit5 Optional JUnit 5 integration.
com.squareup.okhttp3:mockwebserver:5.0.0 okhttp3.mockwebserver Obsolete. Depends on JUnit 4.

OkHttp now supports Happy Eyeballs ([RFC 8305][rfc_8305]) for IPv4+IPv6 networks. It attempts
both IPv6 and IPv4 connections concurrently, keeping whichever connects first.

We’ve improved our Kotlin APIs. You can skip the builder:

val request = Request(
  url = "https://cash.app/".toHttpUrl(),
)

OkHttp now supports [GraalVM].

Here’s what has changed since 5.0.0-alpha.17:

  • Upgrade: [Okio 3.15.0][okio_3_15_0].
  • Upgrade: [Kotlin 2.2.0][kotlin_2_2_0].
  • Fix: Don't crash with a NoSuchMethodError when using OkHttp with the Sentry SDK.
  • Fix: Retain the query data in the old okhttp3.mockwebserver.RecordedRequest.path property. We
    inadvertently changed this behavior when we introduced the mockwebserver3 API.
mariadb-corporation/mariadb-connector-j (org.mariadb.jdbc:mariadb-java-client)

v3.5.6

Compare Source

Full Changelog

Key Enhancements
  • CONJ-1238 - rewriteBatchStatements implementation
  • CONJ-1274 - server prepared statement client failover to client prepared statement
Issues Resolved
  • CONJ-1278 - prepared statement caching enablement correction, same than 2.x
  • CONJ-1279 - metadata table name addition for 12.1 after MDEV-28933
  • CONJ-1280 - permit having multiple command with initSql option
  • CONJ-1276 - Connection#isValid(int timeout) does not obey the passed in timeout if the network is down.

v3.5.5

Compare Source

Full Changelog

Issues Resolved
  • CONJ-1265 - ensure rollback and release savepoint operation to be sent to server, even when there is no transaction in progress
  • CONJ-1270 - forceConnectionTimeZoneToSession doesn't always set the timezone to server

v3.5.4

Compare Source

Full Changelog

Key Enhancements
  • CONJ-1261 - Added caching option for loadCodecs results to improve performance
Issues Resolved
  • CONJ-1234 - Fixed incorrect type definitions in DatabaseMetaData.getTypeInfo()
  • CONJ-1247 - Resolved potential race condition that could cause NullPointerException
  • CONJ-1250 - avoids redundant queries for CallableStatement.getParameterMetaData()
  • CONJ-1251 - Fixed SSL configuration issue where zero SSL settings only functioned without explicit SSL configuration
  • CONJ-1252 - Resolved GSSAPI authentication error when server exchanges begin with 0x01 byte
  • CONJ-1254 - Corrected DatabaseMetadata.getTypeInfo() returning incorrect values for AUTO_INCREMENT, FIXED_PREC_SCALE, and CASE_SENSITIVE fields
  • CONJ-1255 - Fixed getString method on BIT(1) fields to properly honor transformedBitIsBoolean configuration
  • CONJ-1259 - Enhanced metadata compatibility with MariaDB version 12.0
  • CONJ-1260 - Improved performance of DatabaseMetaData.getExportedKeys method
  • CONJ-1256 - Fixed issue to ensure correct catalog name is returned

v3.5.3

Compare Source

Full Changelog

Bugs Fixed
  • CONJ-1226 Fixed issue where dates containing zero day or month resulted in a DateTimeException
  • CONJ-1232 Resolved timestamp string representation incompatibility between versions 2.7 and 3.x
    • see new option oldModeNoPrecisionTimestamp
  • CONJ-1226 Fixed incorrect values returned by ResultSet.getColumnType() for unsigned values
  • CONJ-1241 Corrected regression in 3.x affecting column metadata for unsigned types
  • CONJ-1243 Fixed CallableStatement.getParameterMetadata() returning wrong java.sql.Type for boolean values
  • CONJ-1236 Prevented NPE (Null Pointer Exception) after reconnection failure in high availability configurations
  • CONJ-1237 Fixed issue with incorrect statements.isClosed value after closing connection
  • CONJ-1239 Disabled BULK operations when no parameters are present
  • CONJ-1240 Fixed connectivity issues with databases that only accept TLSv1.3
  • CONJ-1235 Modified redirection option to enable by default only when SSL is enabled

v3.5.2

Compare Source

Full Changelog

Bugs Fixed
  • CONJ-1216 Resolved a performance issue that occurred when batch processing on MySQL and older MariaDB (pre-10.2) servers
  • CONJ-1218 Incorrect behavior where XA connections are closed when regular connections are terminated - this is against specifications
  • CONJ-1217 The trustCertificateKeyStorePassword alias parameter isn’t taken into account
  • CONJ-1221 DatabaseMetadata.getTypeInfo() is missing the data types UUID and VECTOR
  • CONJ-1225 System throws an exception prematurely without checking all available connections
  • CONJ-1228 result-set.getObject() on BLOB type returns Blob in place of byte[]
  • CONJ-660 new disconnectOnExpiredPasswords connection option that controls client behavior when connecting with an expired password.
    When set to true (default), the client disconnects if it detects an expired password.
    When false, the client maintains the connection and allows setting a new password.
  • CONJ-1229 Permit executeQuery commands to not return a result-set
getsentry/sentry-java (io.sentry:sentry)

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 io.sentry:sentry-spring-boot-jakarta is now correctly being built and published to Maven Central.

v8.13.1

Compare Source

Fixes
  • Fix SentryAndroid.init crash if SDK is initialized from a background thread while an Activity is in resumed state (#​4449)
Dependencies

v8.13.0

Compare Source

Features
  • Add debug mode for Session Replay masking (#​4357)
    • Use Sentry.replay().enableDebugMaskingOverlay() to overlay the screen with the Session Replay masks.
    • The masks will be invalidated at most once per frameRate (default 1 fps).
  • Extend Log

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

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.

@coderabbitai
Copy link

coderabbitai bot commented Feb 11, 2025

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.


🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Explain this complex logic.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai explain this code block.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and explain its main purpose.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Join our Discord community for assistance with any issues or questions.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

@renovate renovate bot changed the title Update dependency org.mariadb.jdbc:mariadb-java-client to v3.5.2 Update all dependencies Feb 12, 2025
@renovate renovate bot force-pushed the renovate/all branch 6 times, most recently from 99cabbf to 72b83db Compare February 26, 2025 14:57
@renovate renovate bot force-pushed the renovate/all branch 2 times, most recently from d108924 to 9ab7b69 Compare March 4, 2025 12:43
@renovate renovate bot force-pushed the renovate/all branch 7 times, most recently from 4df7cee to db00a0e Compare March 20, 2025 01:44
@renovate renovate bot force-pushed the renovate/all branch 5 times, most recently from 814bb30 to 6b9b964 Compare March 30, 2025 14:37
@renovate renovate bot force-pushed the renovate/all branch 4 times, most recently from a07f913 to 081f3e4 Compare April 5, 2025 14:35
@renovate renovate bot force-pushed the renovate/all branch 3 times, most recently from c2cf282 to 8a3fc49 Compare April 11, 2025 19:26
@renovate renovate bot force-pushed the renovate/all branch from 0bfc2ae to 2c1a27a Compare May 13, 2025 20:31
@renovate renovate bot force-pushed the renovate/all branch 7 times, most recently from 3483cf8 to f922d82 Compare May 27, 2025 16:39
@renovate renovate bot force-pushed the renovate/all branch 2 times, most recently from 0e1ffd3 to 046a01c Compare May 31, 2025 17:39
@renovate renovate bot force-pushed the renovate/all branch 5 times, most recently from f90fd1b to a53efed Compare June 12, 2025 12:31
@renovate renovate bot force-pushed the renovate/all branch 4 times, most recently from 0cf0f20 to 67a13db Compare June 24, 2025 13:46
@renovate renovate bot force-pushed the renovate/all branch 5 times, most recently from 71593a4 to b414c4c Compare June 30, 2025 18:44
@renovate renovate bot force-pushed the renovate/all branch 5 times, most recently from ebd4b15 to 7a3c8ba Compare July 9, 2025 23:36
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants