Releases: getsentry/sentry-ruby
2.6.1
- BUGFIX: Fix cases where ActionDispatch::RemoteIP would blow up during event creation [@cmoylan, #722]
- BUGFIX: In ActiveJob, don't report exceptions which can be rescued by rescue_from handlers [@bensheldon, #719]
2.6.0
-
FEATURE: raven-ruby now marks itself as the "ruby" logger by default, to match raven-js behavior [@nateberkopec]
-
FEATURE: You may now override the default sanitization parameters [#712, @nateberkopec]
-
FEATURE: Breadcrumb buffers are now publicly accessible [#686, @nateberkopec]
-
FEATURE: We yell at you now if you're using Heroku but don't have runtime-dyno-metadata enabled [#715, @nateberkopec]
-
FEATURE: project_root will always be set, regardless of framework [#716, @nateberkopec]
-
BUGFIX: Request body and message limits now match Sentry server defaults [#714, @nateberkopec]
-
BUGFIX: Sidekiq context now works as expected [#713, @nateberkopec]
-
BUGFIX: Capture exceptions in ActiveJob when not using Sidekiq adapter [#709, #671, @nateberkopec]
2.5.3
- BUGFIX: Deal properly with ASCII_8BIT/BINARY encodings [#689, #696, @nateberkopec]
2.5.2
-
BUGFIX: raven test executable should be available [#691, @nateberkopec]
-
BUGFIX: Fix stack overflow when calling Backtrace#inspect [#690, @nateberkopec]
-
KNOWN ISSUE: Character encoding errors [#689]
2.5.1
-
BUGFIX: Fix case where Pathname objects are on the load path [@nateberkopec]
-
BUGFIX: Fix bad UTF-8 characters in the URL querystring [@nateberkopec]
-
BUGFIX: Fix case where rack-timeout could be required twice [@nateberkopec]
-
REFACTOR: Slightly cleaner character encoding fixing [@nateberkopec, @bf4]
2.5.0
-
FEATURE: Greatly improved performance (2-3x faster capture) [@nateberkopec]
-
FEATURE: Frozen objects are now sanitized [@nateberkopec]
-
BUGFIX: Grabbing Sidekiq context from "wrapped" classes works [@nateberkopec]
-
BUGFIX: Relaxed Faraday dependency [@nateberkopec]
2.4.0
-
FEATURE: Allow customization of the Faraday adapter [#639, @StupidCodeFactory]
-
BUGFIX: Report the SDK name as "raven-ruby", not "sentry-raven" [#641, @bretthoerner]
-
BUGFIX: Sidekiq jobs now clear context/breadcrumbs properly between jobs [#637, @drewish]
-
BUGFIX: Overriding the logger in Rails wasn't working [#638, @eugeneius]
2.3.1
- BUGFIX: Backtrace parser fixed for JRuby 9k [#619, @the-michael-toy]
- BUGFIX: Rake tasks should show the correct task name [#621, @Bugagazavr]
- BUGFIX: Formatted messages work if params are
nil[#625, @miyachik] - BUGFIX: Backtrace logger on failed event send works with custom formatters [#627, @chulkilee]
- BUGFIX: Fix typo that caused Version headers to not be corrected [#628, @nateberkopec]
- BUGFIX: Faraday errors are more descriptive when no server response [#629, @drewish]
- BUGFIX: DelayedJob handler no longer truncates unneccessarily short [#633, @darrennix]
- BUGFIX: Fix several processors not working correctly w/async jobs stored in backends like Redis [#634, @nateberkopec]
2.3.0
- CHANGE: Log levels of some messages have been changed. Raven logger is INFO level by default. [@nateberkopec]
- BUGFIX: Exception messages are now limited to 10,000 bytes. [#617, @mattrobenolt]
2.2.0
- ENHANCEMENT: Sentry server errors now return some information about the response headers. [#585, @rafadc]
- BUGFIX/ENHANCEMENT: Frozen objects are no longer sanitized. This prevents some bugs, but you can now also freeze objects if you don't want them to be sanitized by the SanitizeData processor. [#594, @nateberkopec]
- ENHANCEMENT: The ability to use Raven::Instance alone is greatly improved. You can now call #capture_exception directly on an Instance (#595), give it it's own Logger (#599), and set it's own config which will be used when creating Events (#601). Thanks to
- ENHANCEMENT: You may now provide your own LineCache-like class to Raven. This is useful if you have source code which is not available on disk. [#606, @nateberkopec]
- BUGFIX: Raven no longer emits anything to STDOUT if a system command fails [#596, @nateberkopec]
- ENHANCEMENT: Raven now tells you exactly why it will not send an event in the logs [#602, @nateberkopec]