All notable changes to this project will be documented in this file.
The format is based on Keep a Changelog, and this project adheres to Semantic Versioning.
0.3.5 - 2025-02-21
- Allows reporting
app.version
by optionally settingconfig :tower_bugsnag, app_version: ...
(#43)
0.3.4 - 2025-02-13
- Allow use with Tower 0.8.x
- Updates
tower
dependency from{:tower, "~> 0.7.1"}
to{:tower, "~> 0.7.1 or ~> 0.8.0"}
.
0.3.3 - 2024-11-20
- Supports reporting any Tower messages. E.g.
Tower.report_message(:info, ...)
will be reported as BugSnag error of severity "info". - Includes information about the Device in the error report. Will be shown in the Device tab in the BugSnag UI.
0.3.2 - 2024-11-19
- Include in report whether exception was handled or unhandled
0.3.1 - 2024-11-19
- Properly format reported throw value
- Updates
tower
dependency from{:tower, "~> 0.6.0"}
to{:tower, "~> 0.7.1"}
.
0.3.0 - 2024-10-24
- Change config name from
:environment
to:release_stage
(prefers use of BugSnag specific nomenclature)
- Properly report common
:gen_server
abnormal exits
0.2.0 - 2024-10-04
-
No longer necessary to call
Tower.attach()
in your applicationstart
. It is done automatically. -
Updates
tower
dependency from{:tower, "~> 0.5.0"}
to{:tower, "~> 0.6.0"}
.
0.1.3 - 2024-10-03
- Corrects reported
tower_bugsnag
notifier version in payloads
0.1.2 - 2024-10-03
- Passes along
Tower.Event.metadata.user_id
to BugSnag reportuser.id
. - Passes along
Tower.Event.metadata
to BugSnag reportmetaData
. - Reports
user-agent
HTTP header if available.
0.1.1 - 2024-10-02
- Includes request data if available
- Don't crash on
Tower.handle_message
despite BugSnag not supporting messages.
- Reports exceptions
- Reports throws
- Reports abnormal exits