All Versions
21
Latest Version
Avg Release Cycle
81 days
Latest Release
83 days ago

Changelog History
Page 1

  • v0.14.1

    July 06, 2020

    ๐Ÿ›  Fixed

    • Implement Jason.Encoder for RingBuffer (#294)
  • v0.14.0

    March 12, 2020

    ๐Ÿ”„ Changed

    • 0๏ธโƒฃ Breadcrumbs on by default
  • v0.13.1

    February 06, 2020

    ๐Ÿ›  Fixed

    • Safely sanitize invalid binaries when encoding JSON for notices.
    • ๐Ÿ›  Fixes for Elixir 1.10 release (#259)
  • v0.13.0

    October 02, 2019

    โž• Added

    • Introducing Breadcrumbs (#235)! After enabling in the config with breadcrumbs_enabled: true, just call Honeybadger.add_breadcrumb/2 anywhere in your code and if an error is reported in that process, the breadcrumb event will be passed along with the Notice.

    ๐Ÿ”„ Changed

    • ๐Ÿ“‡ Renamed Notifier to honeybadger-elixir and added language
  • v0.12.1

    June 12, 2019

    ๐Ÿ›  Fixed

    • ๐Ÿ‘ป Call Exception.blame/3 after normalizing string errors, which prevents reporint all string messages as Erlang errors. (#225)
  • v0.12.0

    May 30, 2019

    โž• Added

    • โž• Added :revision configuration option
    • ๐Ÿ‘ป Automatically call Exception.blame/3 to record additional information in the exception
  • v0.11.0

    February 28, 2019

    โฌ†๏ธ 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
  • v0.10.3

    July 02, 2018

    ๐Ÿ›  Fixed

    • Prevent crashes reporting :badmatch when fetching the current stacktrace from a dead process.
    • โšก๏ธ Updated dependencies.
  • v0.10.2

    July 02, 2018

    ๐Ÿ›  Fixed

    • ๐Ÿ›  Fix crashes caused by presence of structs in the context.
  • v0.10.1

    June 27, 2018

    ๐Ÿ”„ Changed

    • ๐Ÿ– Handle fetching peer info when using Plug 1.6. This is implemented in a backward compatible manner, so versions < 1.6 will continue to work.

    ๐Ÿ›  Fixed

    • Fetch peer information for multiple plug versions
    • โฌ†๏ธ Bump phoenix from 1.3.2 to 1.3.3
    • โฌ†๏ธ Bump hackney from 1.12.1 to 1.13.0