Last week we released version 4.0.0 of the honeybadger Ruby gem. This release includes a long-awaited feature which makes it even easier to customize your error reports before they are sent to Honeybadger. We also did some much-needed refactoring, and made a few removals and deprecations for good measure. Don't worry, though—most of the API remains unchanged, so upgrading should be a relatively painless process for most users.
For the past six months or so I've been working an NES emulator in Rust. As you might expect, I've learned a lot about rust, and even more about NES internals. But the experience has also changed the way I look at Ruby. Specifically, it's made me more than a little paranoid about methods that return nil.
Back in August we released source map upload via a new API for minified JavaScript. Now we are happy to announce the release of our Honeybadger Weback Plugin that uploads the source map produced when minifying JavaScript to our API.
We recently shipped version 3.2 of the honeybadger Ruby Gem, which includes a new feature to make it easier to add context to your error reports.
This month we released a new version of our hex package, which includes a major refactor of the internal client logic as well as some new features, improvements, and bug fixes. We're super excited to share the release of honeybadger v0.7 with you! Here are the highlights.
Here at Honeybadger we want to give you a complete picture of your application's health. That's why we include uptime & latency monitoring with all our plans. We've been hard at work making our uptime system even better; making it suitable not only to check web pages, but also APIs. Many of our customers have found Honeybadger Uptime to be a great replacement for NewRelic's alerts, which were recently removed from their more affordable plans.
