build(deps): bump io.sentry:sentry-bom from 8.0.0 to 8.1.0

[dependabot]

Bumps io.sentry:sentry-bom from 8.0.0 to 8.1.0.

Release notes

Sourced from io.sentry:sentry-bom's releases.

8.1.0

Features

• Add options.ignoredErrors to filter out errors that match a certain String or Regex (#4083)
  • The matching is attempted on event.message, event.formatted, and {event.throwable.class.name}: {event.throwable.message}
  • Can be set in sentry.properties, e.g. ignored-errors=Some error,Another .*
  • Can be set in environment variables, e.g. SENTRY_IGNORED_ERRORS=Some error,Another .*
  • For Spring Boot, it can be set in application.properties, e.g. sentry.ignored-errors=Some error,Another .*
• Log OpenTelemetry related Sentry config (#4122)

Fixes

• Avoid logging an error when a float is passed in the manifest (#4031)
• Add request details to transactions created through OpenTelemetry (#4098)
  • We now add HTTP request method and URL where Sentry expects it to display it in Sentry UI
• Remove java.lang.ClassNotFoundException debug logs when searching for OpenTelemetry marker classes (#4091)
  • There was up to three of these, one for io.sentry.opentelemetry.agent.AgentMarker, io.sentry.opentelemetry.agent.AgentlessMarker and io.sentry.opentelemetry.agent.AgentlessSpringMarker.
  • These were not indicators of something being wrong but rather the SDK looking at what is available at runtime to configure itself accordingly.
• Do not instrument File I/O operations if tracing is disabled (#4051)
• Do not instrument User Interaction multiple times (#4051)
• Speed up view traversal to find touched target in UserInteractionIntegration (#4051)
• Reduce IPC/Binder calls performed by the SDK (#4058)

Behavioural Changes

• Reduce the number of broadcasts the SDK is subscribed for (#4052)
  • Drop TempSensorBreadcrumbsIntegration
  • Drop PhoneStateBreadcrumbsIntegration
  • Reduce number of broadcasts in SystemEventsBreadcrumbsIntegration

Current list of the broadcast events can be found here. If you'd like to subscribe for more events, consider overriding the SystemEventsBreadcrumbsIntegration as follows:

SentryAndroid.init(context) { options ->
    options.integrations.removeAll { it is SystemEventsBreadcrumbsIntegration }
    options.integrations.add(SystemEventsBreadcrumbsIntegration(context, SystemEventsBreadcrumbsIntegration.getDefaultActions() + listOf(/* your custom actions */)))
}

If you would like to keep some of the default broadcast events as breadcrumbs, consider opening a GitHub issue.

• Set mechanism type to suppressed for suppressed exceptions (#4125)
  • This helps to distinguish an exceptions cause from any suppressed exceptions in the Sentry UI

Dependencies

• Bump Spring Boot to 3.4.2 (#4081)
• Bump Native SDK from v0.7.14 to v0.7.19 (#4076)
  • changelog
  • diff

Changelog

Sourced from io.sentry:sentry-bom's changelog.

8.1.0

Features

• Add options.ignoredErrors to filter out errors that match a certain String or Regex (#4083)
  • The matching is attempted on event.message, event.formatted, and {event.throwable.class.name}: {event.throwable.message}
  • Can be set in sentry.properties, e.g. ignored-errors=Some error,Another .*
  • Can be set in environment variables, e.g. SENTRY_IGNORED_ERRORS=Some error,Another .*
  • For Spring Boot, it can be set in application.properties, e.g. sentry.ignored-errors=Some error,Another .*
• Log OpenTelemetry related Sentry config (#4122)

Fixes

• Avoid logging an error when a float is passed in the manifest (#4031)
• Add request details to transactions created through OpenTelemetry (#4098)
  • We now add HTTP request method and URL where Sentry expects it to display it in Sentry UI
• Remove java.lang.ClassNotFoundException debug logs when searching for OpenTelemetry marker classes (#4091)
  • There was up to three of these, one for io.sentry.opentelemetry.agent.AgentMarker, io.sentry.opentelemetry.agent.AgentlessMarker and io.sentry.opentelemetry.agent.AgentlessSpringMarker.
  • These were not indicators of something being wrong but rather the SDK looking at what is available at runtime to configure itself accordingly.
• Do not instrument File I/O operations if tracing is disabled (#4051)
• Do not instrument User Interaction multiple times (#4051)
• Speed up view traversal to find touched target in UserInteractionIntegration (#4051)
• Reduce IPC/Binder calls performed by the SDK (#4058)

Behavioural Changes

• Reduce the number of broadcasts the SDK is subscribed for (#4052)
  • Drop TempSensorBreadcrumbsIntegration
  • Drop PhoneStateBreadcrumbsIntegration
  • Reduce number of broadcasts in SystemEventsBreadcrumbsIntegration

Current list of the broadcast events can be found here. If you'd like to subscribe for more events, consider overriding the SystemEventsBreadcrumbsIntegration as follows:

SentryAndroid.init(context) { options ->
    options.integrations.removeAll { it is SystemEventsBreadcrumbsIntegration }
    options.integrations.add(SystemEventsBreadcrumbsIntegration(context, SystemEventsBreadcrumbsIntegration.getDefaultActions() + listOf(/* your custom actions */)))
}

If you would like to keep some of the default broadcast events as breadcrumbs, consider opening a GitHub issue.

• Set mechanism type to suppressed for suppressed exceptions (#4125)
  • This helps to distinguish an exceptions cause from any suppressed exceptions in the Sentry UI

Dependencies

• Bump Spring Boot to 3.4.2 (#4081)
• Bump Native SDK from v0.7.14 to v0.7.19 (#4076)
  • changelog
  • diff

Commits

• c322afe release: 8.1.0
• 2748875 Re-apply 7.x.x changes (#4124)
• a9719c7 chore(deps): update Native SDK to v0.7.19 (#4076)
• b68011a Log debug messages giving info about OpenTelemetry related config settings (#...
• 2fc1ed7 Set mechanism type to suppressed for suppressed exceptions (#4125)
• 880dc4f Add JavaDoc to `SentryOptions.ignoredTransactions,ignoredSpanOrigins,ignoredC...
• 1683fbb Bump Spring Boot to 3.4.2 (#4081)
• 29a4185 Add request details to transactions created through OpenTelemetry (#4098)
• 5c403ff Add options.ignoredErrors accepting String and Regex (#4083)
• a136d5b Remove date range for LICENSE (#4096)
• 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)

[coderabbitai]

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.

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 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.
  • Generate unit testing code for this file.
  • 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 generate unit testing code for this file.
  • @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 generate unit testing code.
  • @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.

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 docstrings to generate docstrings for this PR. (Beta)
• @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.