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]

2.1.4

• FIX: Remove contexts key, because it was disabling browser auto-tagging [#587, @nateberkopec]

2.1.2

FIX: sys_command not falling back to Windows commands properly, logging output [@jmalves, @nateberkopec]

2.1.1

FIX: Message params should accept nil [@jmalves, #570]

2.1.0

ENHANCEMENTS:

• Your client version is now included in all Events. [@nateberkopec, #559]
• OS and Ruby runtime information now included in all Events. [@nateberkopec, #560]
• Transport errors (like Sentry 4XX errors) now raise Sentry::Error, not Faraday errors. [@nateberkopec, #565]
• Sidekiq integration is streamlined and improved. Supports Sidekiq 3.x and up. [@nateberkopec, #555]

FIXES:

• Heroku release detection is improved and more accurate. You must heroku labs:enable runtime-dyno-metadata for it to work. [@nateberkopec, #566]

2.0.2

• FIX: Don't set up Rack-Timeout middleware. [@janraasch, #558]

2.0.1

• FIX: UUIDs were being rejected by Sentry as being too long [@nateberkopec]