dep: bump sentry-sidekiq from 5.3.1 to 5.4.1
Bumps sentry-sidekiq from 5.3.1 to 5.4.1.
Changelog
Sourced from sentry-sidekiq's changelog.
5.4.1
Bug Fixes
- Fix missing
spec.files
insentry-ruby.gemspec
- Fixes #1856
5.4.0
Features
Expose
:values
inExceptionInterface
, so that it can be accessed inbefore_send
underevent.exception.values
#1843Add top level
Sentry.close
API #1844
- Cleans up SDK state and sets it to uninitialized
- No-ops all SDK APIs and also disables the transport layer, so nothing will be sent to Sentry after closing the SDK
Handle exception with large stacktrace without dropping entire item #1807
Capture Rails runner's exceptions before exiting #1820
Add
Sentry.with_exception_captured
helper #1814Usage:
Sentry.with_exception_captured do 1/1 #=> 1 will be returned end Sentry.with_exception_captured do 1/0 #=> ZeroDivisionError will be reported and re-raised end
Prepare for Rails 7.1's error reporter API change #1834
Set
sentry.error_event_id
in request env if the middleware captures errors #1849If the SDK's Rack middleware captures an error, the reported event's id will be stored in the request env. For example:
env["sentry.error_event_id"] #=> "507bd4c1a07e4355bb70bcd7afe8ab17"
Users can display this information on the error page via a middleware as proposed in #1846
Bug Fixes
... (truncated)
Commits
-
460dd6d
release: 5.4.1 -
09308ab
Fix missingspec.files
insentry-ruby.gemspec
(#1857) -
7ff81bf
Merge branch 'release/5.4.0' -
abbc62f
release: 5.4.0 -
3e854ac
Prepare CHANGELOG for 5.4.0 release -
b30722e
Add exited status to SessionFlusher and rescue ThreadError (#1851) -
3323159
Bump terser from 4.8.0 to 4.8.1 in /sentry-rails/examples/rails-6.0 (#1852) -
6118b66
Bump terser from 4.8.0 to 4.8.1 in /sentry-raven/examples/rails-6.0 (#1850) -
3326fe0
Revert "CHANGELOG" -
d9265c3
CHANGELOG - Additional commits viewable in compare view
Dependabot commands
You can trigger Dependabot actions by commenting on this MR
-
@dependabot-bot rebase
will rebase this MR -
@dependabot-bot recreate
will recreate this MR rewriting all the manual changes and resolving conflicts
Allure report
allure-report-publisher
generated test report!
rspec:
+------------------------------------------------------------------+
| behaviors summary |
+-------------+--------+--------+---------+-------+-------+--------+
| | passed | failed | skipped | flaky | total | result |
+-------------+--------+--------+---------+-------+-------+--------+
| system | 10 | 0 | 0 | 0 | 10 | ✅ |
| jobs | 14 | 0 | 0 | 0 | 14 | ✅ |
| services | 174 | 0 | 0 | 0 | 174 | ✅ |
| controllers | 25 | 0 | 0 | 0 | 25 | ✅ |
| models | 3 | 0 | 0 | 0 | 3 | ✅ |
| tasks | 8 | 0 | 0 | 0 | 8 | ✅ |
+-------------+--------+--------+---------+-------+-------+--------+
| Total | 234 | 0 | 0 | 0 | 234 | ✅ |
+-------------+--------+--------+---------+-------+-------+--------+