« Changelog History


honeybadger v0.11.0 Release Notes

Release Date: 2019-02-28 // about 5 years ago

  • ⬆️ When upgrading to v0.11, users should be aware of a few important changes:

    • You must be on Elixir 1.7+ and Erlang/OTP 21+
    • Due to the deprecation of System.stacktrace/0 and the introduction of __STACKTRACE__, manually calling Honeybadger.notify/3 will no longer include a stacktrace by default. See the issue discussion for more details
    • A stacktrace can be manually provided from within a rescue/catch block via the STACKTRACE macro, e.g. Honeybadger.notify(SomeError, %{my: :context}, __STACKTRACE__)

    🔄 Changed

    • Switch from Erlang's :error_logger to an Elixir 1.7 and Erlang/OTP 21+ Logger backend. This provides more consistent error reporting and enhanced integration with Logger metadata.
    • Stop automatically extracting stacktraces for calls to Honeybadger.notice/3. The generated stacktrace was unreliably and frequently listed the Honeybadger reporter's internals, rather than application code. Manual calls to notice/3 should happen within a rescue/catch block and use the __STACKTRACE__ macro.

    ➕ Added

    • 📇 Use Logger.metadata as the basis for Honeybadger context in all logger generated notices

    🛠 Fixed

    • 🛠 Fix Map.t() isn't a valid dialyzer type (#198)
    • 📜 Try to convert remote IP to string in case of parsing failure