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]

2.0.0

BREAKING CHANGES:

• The object passed to the async callback is now a JSON-compatible hash, not a Raven::Event. This fixes many bugs with backend job processors like DelayedJob. [@nateberkopec, #547]
• Several deprecated accessors have been removed [@nateberkopec, #543]
• You can no longer pass an object which cannot be called to should_capture [@nateberkopec, #542]

ENHANCEMENTS:

• Rack::Timeout exceptions are now fingerprinted by URL, making them more useful [@nateberkopec, #538]
• Added an HTTP header processor by default. We now scrub Authorization headers correctly. You can use config.sanitize_http_headers to add a list of HTTP headers you don't want sent to Sentry (e.g. ["Via", "Referer", "User-Agent", "Server", "From"]) [@nateberkopec]

FIXES:

• User/Event IP addresses are now set more accurately. This will fix many issues with local proxy setups (nginx, etc). [@nateberkopec, #546]
• We now generate a real UUID in the correct format for Event IDs [@nateberkopec, #549]
• If async sending fails, we retry with sync sending. [@nateberkopec, #548]
• Changed truncation approach - event messages and HTTP bodies now limited to the same amount of characters they're limited to at the Sentry server [@nateberkopec, #536]

OTHER:

• Codebase cleaned up with Rubocop [@nateberkopec, #544]

1.2.3

• ENHANCEMENT: Send the current environment to Sentry [@dcramer, #530]
• BUGFIX: Fix all warnings emitted by Ruby verbose mode [@nateberkopec]
• BUGFIX: Fix compat with log4r [@nateberkopec, #535]