search

waifu-motivator / waifu-motivator-plugin

OSS Waifu Motivator Plugin for JetBrains IDEs to help boost your motivation while coding!
https://plugins.jetbrains.com/plugin/13381-waifu-motivator
MIT License
341 stars 15 forks source link

chore(deps): bump io.sentry:sentry from 6.18.1 to 6.25.1 #545

Closed dependabot[bot] closed 1 year ago

dependabot[bot] commented 1 year ago

Bumps io.sentry:sentry from 6.18.1 to 6.25.1.

Release notes

Sourced from io.sentry:sentry's releases.

6.25.1

Fixes

  • Allow removing integrations in SentryAndroid.init (#2826)
  • Fix concurrent access to frameMetrics listener (#2823)

Dependencies

6.25.0

Features

  • Add manifest AutoInit to integrations list (#2795)
  • Tracing headers (sentry-trace and baggage) are now attached and passed through even if performance is disabled (#2788)

Fixes

  • Set environment from SentryOptions if none persisted in ANRv2 (#2809)
  • Remove code that set tracesSampleRate to 0.0 for Spring Boot if not set (#2800)
    • This used to enable performance but not send any transactions by default.
    • Performance is now disabled by default.
  • Fix slow/frozen frames were not reported with transactions (#2811)

Dependencies

6.24.0

Features

  • Add debouncing mechanism and before-capture callbacks for screenshots and view hierarchies (#2773)
  • Improve ANRv2 implementation (#2792)
    • Add a proguard rule to keep ApplicationNotResponding class from obfuscation
    • Add a new option setReportHistoricalAnrs; when enabled, it will report all of the ANRs from the getHistoricalExitReasons list. By default, the SDK only reports and enriches the latest ANR and only this one counts towards ANR rate. Worth noting that this option is mainly useful when updating the SDK to the version where ANRv2 has been introduced, to report all ANRs happened prior to the SDK update. After that, the SDK will always pick up the latest ANR from the historical exit reasons list on next app restart, so there should be no historical ANRs to report. These ANRs are reported with the HistoricalAppExitInfo mechanism.
    • Add a new option setAttachAnrThreadDump to send ANR thread dump from the system as an attachment. This is only useful as additional information, because the SDK attempts to parse the thread dump into proper threads with stacktraces by default.

... (truncated)

Changelog

Sourced from io.sentry:sentry's changelog.

6.25.1

Fixes

  • Allow removing integrations in SentryAndroid.init (#2826)
  • Fix concurrent access to frameMetrics listener (#2823)

Dependencies

6.25.0

Features

  • Add manifest AutoInit to integrations list (#2795)
  • Tracing headers (sentry-trace and baggage) are now attached and passed through even if performance is disabled (#2788)

Fixes

  • Set environment from SentryOptions if none persisted in ANRv2 (#2809)
  • Remove code that set tracesSampleRate to 0.0 for Spring Boot if not set (#2800)
    • This used to enable performance but not send any transactions by default.
    • Performance is now disabled by default.
  • Fix slow/frozen frames were not reported with transactions (#2811)

Dependencies

6.24.0

Features

  • Add debouncing mechanism and before-capture callbacks for screenshots and view hierarchies (#2773)
  • Improve ANRv2 implementation (#2792)
    • Add a proguard rule to keep ApplicationNotResponding class from obfuscation
    • Add a new option setReportHistoricalAnrs; when enabled, it will report all of the ANRs from the getHistoricalExitReasons list. By default, the SDK only reports and enriches the latest ANR and only this one counts towards ANR rate. Worth noting that this option is mainly useful when updating the SDK to the version where ANRv2 has been introduced, to report all ANRs happened prior to the SDK update. After that, the SDK will always pick up the latest ANR from the historical exit reasons list on next app restart, so there should be no historical ANRs to report.

... (truncated)

Commits


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 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)
dependabot[bot] commented 1 year ago

Superseded by #546.