fix(deps): update dependency io.sentry:sentry to v8.17.0

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
io.sentry:sentry	8.14.0 -> 8.17.0

---

Warning

Some dependencies could not be looked up. Check the Dependency Dashboard for more information.

---

Release Notes

getsentry/sentry-java (io.sentry:sentry)

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)
  • changelog
  • diff

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

• Bump Gradle from v8.14.1 to v8.14.2 (#​4473)
  • changelog
  • diff

---

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 is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

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

---

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

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud