Bump io.sentry:sentry from 8.3.0 to 8.18.0

[dependabot]

Bumps io.sentry:sentry from 8.3.0 to 8.18.0.

Release notes

Sourced from io.sentry:sentry's releases.

8.18.0

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.

8.17.0

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

... (truncated)

Changelog

Sourced from io.sentry:sentry's changelog.

8.18.0

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.

8.17.0

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

... (truncated)

Commits

• 3da09d8 release: 8.18.0
• eac12f4 Remove indirection for integrations and packages via VersionInfoHolder (#4578)
• 5b05195 Report OpenTelemetry Agentless SDK and integration (#4570)
• dea75aa E2E tests for OpenTelemetry based console sample (#4563)
• 34f4b72 Do not use Sentry logging API if logs are disabled for JUL (#4574)
• 6c58c54 Do not use Sentry logging API in Log4j2 if logs are disabled (#4573)
• d1fd194 Add Ktor client integration (#4527)
• 70671a5 Add Compose user feedback button (#4559)
• 485c1a6 Add end to end tests for our console sample (#4552)
• 0d667ec Add autoTransactionDeadlineTimeoutMillis option (#4555)
• Additional commits viewable in compare view

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)

[Clarkcj12]

🎉 Snyk checks have passed. No issues have been found so far.

✅ security/snyk check is complete. No issues have been found. (View Details)

[dependabot]

Superseded by #70.