Skip to content

Releases: evalphobia/logrus_sentry

v0.8.2

04 Feb 05:42
Compare
Choose a tag to compare
v0.8.2 Pre-release
Pre-release
Add option to add error breadcrumb in sentry log (#81)

v0.8.1

04 Feb 02:40
Compare
Choose a tag to compare
bugfix: wg wait block exit when shutdown w/out error (#82)

v0.8.0

11 Jan 08:23
4034fb1
Compare
Choose a tag to compare
Add error handler for Sentry error (#78)

v0.6.0

05 Jan 15:28
af66214
Compare
Choose a tag to compare

Support sirupsen/logrus@v1.2.0 or above.
https://github.com/sirupsen/logrus/releases/tag/v1.2.0

v0.5.0

29 Nov 14:27
Compare
Choose a tag to compare
Add function name to NewStackTraceFrame call for updating to raven-go…

… v0.1.1 (#66)

v0.4.6

25 May 08:55
Compare
Choose a tag to compare
When errors.Cause returns nil, use the original error value instead (…

…#61)

v0.4.5

21 Feb 14:49
Compare
Choose a tag to compare
Fix grouping and use a useful culprit with new SwitchExceptionTypeAnd…

…Message option (#58)

v0.4.4

19 Feb 12:37
Compare
Choose a tag to compare
Allow switching the exception type and message (#57)

v0.4.3

09 Feb 15:07
Compare
Choose a tag to compare
Allow server_name to be set globally (#56)

v0.4.2

30 Aug 01:35
Compare
Choose a tag to compare
Stacktrace the culprit should be the received error not the cause (#45)

Previously, when stacktrace was enabled, the culprit would be set to
the first error that did not implement Cause (as detected by errors.Cause(err)),
this had the affect of not showing any additional context added to
the error.

This was also inconsistent with the same behaviour when stacktrace was
disabled.

This change attempts to unify that behaviour, as well as to not discard
the context added to the errors.