Bump io.sentry:sentry-log4j2 from 1.7.29 to 7.5.0

[dependabot]

Bumps io.sentry:sentry-log4j2 from 1.7.29 to 7.5.0.

Release notes

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

7.5.0

Features

• Add support for measurements at span level (#3219)
• Add enableScopePersistence option to disable PersistingScopeObserver used for ANR reporting which may increase performance overhead. Defaults to true (#3218)
  • When disabled, the SDK will not enrich ANRv2 events with scope data (e.g. breadcrumbs, user, tags, etc.)
• Configurable defaults for Cron - MonitorConfig (#3195)
• We now display a warning on startup if an incompatible version of Spring Boot is detected (#3233)
  • This should help notice a mismatching Sentry dependency, especially when upgrading a Spring Boot application
• Experimental: Add Metrics API (#3205)

Fixes

• Ensure performance measurement collection is not taken too frequently (#3221)
• Fix old profiles deletion on SDK init (#3216)
• Fix hub restore point in wrappers: SentryWrapper, SentryTaskDecorator and SentryScheduleHook (#3225)
  • We now reset the hub to its previous value on the thread where the Runnable/Callable/Supplier is executed instead of setting it to the hub that was used on the thread where the Runnable/Callable/Supplier was created.
• Fix add missing thread name/id to app start spans (#3226)

7.4.0

Features

• Add new threshold parameters to monitor config (#3181)
• Report process init time as a span for app start performance (#3159)
• (perf-v2): Calculate frame delay on a span level (#3197)
• Resolve spring properties in @​SentryCheckIn annotation (#3194)
• Experimental: Add Spotlight integration (#3166)
  • For more details about Spotlight head over to https://spotlightjs.com/
  • Set options.isEnableSpotlight = true to enable Spotlight

Fixes

• Don't wait on main thread when SDK restarts (#3200)
• Fix Jetpack Compose widgets are not being correctly identified for user interaction tracing (#3209)
• Fix issue title on Android when a wrapping RuntimeException is thrown by the system (#3212)
  • This will change grouping of the issues that were previously titled RuntimeInit$MethodAndArgsCaller to have them split up properly by the original root cause exception

7.3.0

Features

• Added App Start profiling
  • This depends on the new option io.sentry.profiling.enable-app-start, other than the already existing io.sentry.traces.profiling.sample-rate.
  • Sampler functions can check the new isForNextAppStart flag, to adjust startup profiling sampling programmatically. Relevant PRs:
  • Decouple Profiler from Transaction (#3101)
  • Add options and sampling logic (#3121)
  • Add ContentProvider and start profile (#3128)
• Extend internal performance collector APIs (#3102)
• Collect slow and frozen frames for spans using OnFrameMetricsAvailableListener (#3111)
• Interpolate total frame count to match span duration (#3158)

... (truncated)

Changelog

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

7.5.0

Features

• Add support for measurements at span level (#3219)
• Add enableScopePersistence option to disable PersistingScopeObserver used for ANR reporting which may increase performance overhead. Defaults to true (#3218)
  • When disabled, the SDK will not enrich ANRv2 events with scope data (e.g. breadcrumbs, user, tags, etc.)
• Configurable defaults for Cron - MonitorConfig (#3195)
• We now display a warning on startup if an incompatible version of Spring Boot is detected (#3233)
  • This should help notice a mismatching Sentry dependency, especially when upgrading a Spring Boot application
• Experimental: Add Metrics API (#3205)

Fixes

• Ensure performance measurement collection is not taken too frequently (#3221)
• Fix old profiles deletion on SDK init (#3216)
• Fix hub restore point in wrappers: SentryWrapper, SentryTaskDecorator and SentryScheduleHook (#3225)
  • We now reset the hub to its previous value on the thread where the Runnable/Callable/Supplier is executed instead of setting it to the hub that was used on the thread where the Runnable/Callable/Supplier was created.
• Fix add missing thread name/id to app start spans (#3226)

7.4.0

Features

• Add new threshold parameters to monitor config (#3181)
• Report process init time as a span for app start performance (#3159)
• (perf-v2): Calculate frame delay on a span level (#3197)
• Resolve spring properties in @​SentryCheckIn annotation (#3194)
• Experimental: Add Spotlight integration (#3166)
  • For more details about Spotlight head over to https://spotlightjs.com/
  • Set options.isEnableSpotlight = true to enable Spotlight

Fixes

• Don't wait on main thread when SDK restarts (#3200)
• Fix Jetpack Compose widgets are not being correctly identified for user interaction tracing (#3209)
• Fix issue title on Android when a wrapping RuntimeException is thrown by the system (#3212)
  • This will change grouping of the issues that were previously titled RuntimeInit$MethodAndArgsCaller to have them split up properly by the original root cause exception

7.3.0

Features

• Added App Start profiling
  • This depends on the new option io.sentry.profiling.enable-app-start, other than the already existing io.sentry.traces.profiling.sample-rate.
  • Sampler functions can check the new isForNextAppStart flag, to adjust startup profiling sampling programmatically. Relevant PRs:
  • Decouple Profiler from Transaction (#3101)
  • Add options and sampling logic (#3121)
  • Add ContentProvider and start profile (#3128)

... (truncated)

Commits

• c2b79e4 release: 7.5.0
• 01eb25d Update CHANGELOG.md (#3239)
• ff8471a Allow whitespace in metric tag values (#3235)
• c7addb9 Show warning if incompatible spring boot version is detected (#3233)
• a816b3f Defaults for Cron - MonitorConfig (#3195)
• 7275aa8 Add support for measurements at span level (#3219)
• 39e3ed7 Add metrics API (#3205)
• 9578eab Fix add missing thread name/id to app start spans (#3226)
• aa91b8f Fix hub restore in async wrappers (#3225)
• bf82eb3 Ensure performance measurement collection is not taken too frequently (#3221)
• 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)

[dependabot]

Superseded by #317.