Bump sentry-ruby from 5.8.0 to 5.10.0
Bumps sentry-ruby from 5.8.0 to 5.10.0.
Changelog
Sourced from sentry-ruby's changelog.
5.10.0
Features
- Move
http.queryto span data in net/http integration #2039- Validate
releaseis aStringduring configuration #2040- Allow JRuby Java exceptions to be captured #2043
- Improved error handling around
traces_sample_rate/profiles_sample_rate#2036Bug Fixes
- Support Rails 7.1's show exception check #2049
- Fix uninitialzed race condition in Redis integration #2057
- Fixes #2054
- Ignore low-level Puma exceptions by default #2055
- Use allowlist to filter
ActiveSupportbreadcrumbs' data #2048- ErrorHandler should cleanup the scope (#2059)
5.9.0
Features
Add new boolean option
config.enable_tracingto simplify enabling performance tracing #2005
config.enable_tracing = truewill settraces_sample_rateto1.0if not set alreadyconfig.enable_tracing = falsewill turn off tracing even iftraces_sample_rate/traces_sampleris setconfig.enable_tracing = nil(default) will keep the current behaviourAllow ignoring
excluded_exceptionswhen manually capturing exceptions #2007Users can now ignore the SDK's
excluded_exceptionsby passingignore_exclusionshint when usingSentry.capture_exception.# assume ignored_exception.class is included in config.excluded_exception Sentry.capture_exception(ignored_exception) # won't be sent to Sentry Sentry.capture_exception(ignored_exception, hint: { ignore_exclusions: true }) # will be sent to SentrySupport capturing low-level errors propagated to Puma #2026
Add
spectoBacktrace::APP_DIRS_PATTERN#2029Forward all
baggageheader items that are prefixed withsentry-#2025Add
stackprofbased profiler #2024The SDK now supports sending profiles taken by the
stackprofgem and viewing them in the Profiling section.To use it, first add
stackprofto yourGemfileand make sure it is loaded beforesentry-ruby.# Gemfilegem 'stackprof'
... (truncated)
Commits
eb826b6release: 5.10.0856391dUpdate changelog header (#2061)3131c7dErrorHandler should cleanup the scope (#2059)5054dbeUse allowlist to filter ActiveSupport breadcrumbs' data (#2048)ec07eb7Cleanup development dependencies (#2050)6196cecFix uninitialized race condition in Redis integration (#2057)75aa456Ignore low-level Puma exceptions by default (#2055)11ecd25handle sample rate type incompatibilities (#2036)a231150Allow java exceptions as capture type in JRuby (#2043) (#2044)91308d3Drop back to global CoC (#2053)- 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 rebasewill rebase this PR -
@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it -
@dependabot mergewill merge this PR after your CI passes on it -
@dependabot squash and mergewill squash and merge this PR after your CI passes on it -
@dependabot cancel mergewill cancel a previously requested merge and block automerging -
@dependabot reopenwill reopen this PR if it is closed -
@dependabot closewill close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually -
@dependabot ignore this major versionwill 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 versionwill 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 dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)