Skip to content
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

[Tech] Bump io.sentry:sentry-log4j2 from 7.0.0 to 7.5.0 in /backend #3000

Merged

Conversation

dependabot[bot]
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Mar 1, 2024

Bumps io.sentry:sentry-log4j2 from 7.0.0 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

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)

@dependabot dependabot bot added dependencies Pull requests that update a dependency file tech. enhancement technical ehancement labels Mar 1, 2024
Copy link
Contributor

coderabbitai bot commented Mar 1, 2024

Important

Auto Review Skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

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

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>.
    • Generate unit-tests 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 tests 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 generate interesting stats about this repository and render them as a table.
    • @coderabbitai show all the console.log statements in this repository.
    • @coderabbitai read src/utils.ts and generate unit tests.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

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 as PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger a review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai help to get help.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

CodeRabbit Configration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • The JSON schema for the configuration file is available here.
  • 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/coderabbit-overrides.v2.json

CodeRabbit Discord Community

Join our Discord Community to get help, request features, and share feedback.

Bumps [io.sentry:sentry-log4j2](https://github.com/getsentry/sentry-java) from 7.0.0 to 7.5.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@7.0.0...7.5.0)

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

Signed-off-by: dependabot[bot] <[email protected]>
@louptheron louptheron force-pushed the dependabot/gradle/backend/io.sentry-sentry-log4j2-7.5.0 branch from 3c70b36 to 452f7fe Compare March 26, 2024 09:09
Copy link

sonarcloud bot commented Mar 26, 2024

Quality Gate Passed Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
No data about Coverage
0.0% Duplication on New Code

See analysis details on SonarCloud

@louptheron louptheron merged commit b012d41 into master Mar 26, 2024
26 checks passed
@louptheron louptheron deleted the dependabot/gradle/backend/io.sentry-sentry-log4j2-7.5.0 branch March 26, 2024 09:22
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 tech. enhancement technical ehancement
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant