This release enhances the composition of Sentry reports to reveal more details about errors. In particular, it does a better job of revealing information that was always redacted as unsafe in previous versions.

Some examples of data that is now included, that wasn't previously:

• the underlying errors behind barriers and assertion failures
• some Go runtime errors (e.g. context canceled, os.PathError, etc)
• custom error types that have a safe formatter function even though they don't report safe strings via the SafeDetails interface
• the tree structure of secondary errors

See PR #94 for details and an example.