Skip to content

build: bump io.sentry:sentry from 8.12.0 to 8.15.0 #454

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
wants to merge 1 commit into from

Conversation

dependabot[bot]
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Jun 26, 2025

Bumps io.sentry:sentry from 8.12.0 to 8.15.0.

Release notes

Sourced from io.sentry:sentry's releases.

8.15.0

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

  • Add chipset to device context (#4512)
  • 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://[email protected]/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)

... (truncated)

Changelog

Sourced from io.sentry:sentry's changelog.

8.15.0

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://[email protected]/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:

... (truncated)

Commits
  • 7ba881e release: 8.15.0
  • 8fde83a fix(feedback): Do not redefine system resources (#4519)
  • 1528dfb Automatically use SentryOptions.Logs.BeforeSendLogCallback Spring beans (#4...
  • 8489642 Allow configuration of Sentry Logs for Spring Boot Logback (#4508)
  • 9f37401 Logs are now flushed on shutdown (#4503)
  • ea7b9c1 Log parameter objects are now turned into String via toString (#4515)
  • b93e18d Send Logback logs to Sentry as logs (#4502)
  • bef763e Add git blame ignore revs for spotless ktfmt (#4514)
  • 34e71f7 feat(contexts): Add chipset to device context (#4512)
  • 8b8369f More accurate spotless config (#4499)
  • Additional commits viewable in compare view

Dependabot compatibility score

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)

Bumps [io.sentry:sentry](https://github.com/getsentry/sentry-java) from 8.12.0 to 8.15.0.
- [Release notes](https://github.com/getsentry/sentry-java/releases)
- [Changelog](https://github.com/getsentry/sentry-java/blob/main/CHANGELOG.md)
- [Commits](getsentry/sentry-java@8.12.0...8.15.0)

---
updated-dependencies:
- dependency-name: io.sentry:sentry
  dependency-version: 8.15.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <[email protected]>
@dependabot dependabot bot added dependencies Pull requests that update a dependency file java Pull requests that update Java code labels Jun 26, 2025
@github-project-automation github-project-automation bot moved this to In progress in Development Jun 26, 2025
Copy link
Contributor Author

dependabot bot commented on behalf of github Jun 27, 2025

Superseded by #455.

@dependabot dependabot bot closed this Jun 27, 2025
@dependabot dependabot bot deleted the dependabot/gradle/io.sentry-sentry-8.15.0 branch June 27, 2025 03:55
@github-project-automation github-project-automation bot moved this from In progress to Done in Development Jun 27, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dependencies Pull requests that update a dependency file java Pull requests that update Java code
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants