0.15.0

• fix: Scope values should not override Event values (#446)
• feat: Make maximum amount of spans configurable (#460)
• feat: Add a method to start a transaction (#482)
• feat: Extend User interface by adding Data, Name and Segment (#483)
• feat: Add ClientOptions.SendDefaultPII (#485)

0.14.0

• feat: Add function to continue from trace string (#434)
• feat: Add max-depth options (#428)
• [breaking] ref: Use a Context type mapping to a map[string]interface{} for all event contexts (#444)
• [breaking] ref: Replace deprecated ioutil pkg with os & io (#454)
• ref: Optimize stacktrace.go from size and speed (#467)
• ci: Test against go1.19 and go1.18, drop go1.16 and go1.15 support (#432, #477)
• deps: Dependency update to fix CVEs (#462, #464, #477)

NOTE: This version drops support for Go 1.16 and Go 1.15. The currently supported Go versions are the last 3 stable releases: 1.19, 1.18 and 1.17.

v0.13.0

• ref: Change DSN ProjectID to be a string (#420)
• fix: When extracting PCs from stack frames, try the PC field (#393)
• build: Bump gin-gonic/gin from v1.4.0 to v1.7.7 (#412)
• build: Bump Go version in go.mod (#410)
• ci: Bump golangci-lint version in GH workflow (#419)
• ci: Update GraphQL config with appropriate permissions (#417)
• ci: Add craft release automation (#422)

v0.12.0

• feat: Automatic Release detection (#363, #369, #386, #400)
• fix: Do not change Hub.lastEventID for transactions (#379)
• fix: Do not clear LastEventID when events are dropped (#382)
• Updates to documentation (#366, #385)

NOTE:
This version drops support for Go 1.14, however no changes have been made that would make the SDK not work with Go 1.14. The currently supported Go versions are the last 3 stable releases: 1.15, 1.16 and 1.17.
There are two behavior changes related to LastEventID, both of which were intended to align the behavior of the Sentry Go SDK with other Sentry SDKs.
The new automatic release detection feature makes it easier to use Sentry and separate events per release without requiring extra work from users. We intend to improve this functionality in a future release by utilizing information that will be available in runtime starting with Go 1.18. The tracking issue is #401.

v0.11.0

• feat(transports): Category-based Rate Limiting (#354)
• feat(transports): Report User-Agent identifying SDK (#357)
• fix(scope): Include event processors in clone (#349)
• Improvements to go doc documentation (#344, #350, #351)
• Miscellaneous changes to our testing infrastructure with GitHub Actions
  (57123a40, #128, #338, #345, #346, #352, #353, #355)

NOTE:
This version drops support for Go 1.13. The currently supported Go versions are the last 3 stable releases: 1.14, 1.15 and 1.16.
Users of the tracing functionality (StartSpan, etc) should upgrade to this version to benefit from separate rate limits for errors and transactions.
There are no breaking changes and upgrading should be a smooth experience for all users.

v0.10.0

• feat: Debug connection reuse (#323)
• fix: Send root span data as Event.Extra (#329)
• fix: Do not double sample transactions (#328)
• fix: Do not override trace context of transactions (#327)
• fix: Drain and close API response bodies (#322)
• ci: Run tests against Go tip (#319)
• ci: Move away from Travis in favor of GitHub Actions (#314) (#321)

v0.9.0

• feat: Initial tracing and performance monitoring support (#285)
• doc: Revamp sentryhttp documentation (#304)
• fix: Hub.PopScope never empties the scope stack (#300)
• ref: Report Event.Timestamp in local time (#299)
• ref: Report Breadcrumb.Timestamp in local time (#299)

NOTE:
This version introduces support for Sentry's Performance Monitoring.
The new tracing capabilities are beta, and we plan to expand them on future versions. Feedback is welcome, please open new issues on GitHub.
The sentryhttp package got better API docs, an updated usage example and support for creating automatic transactions as part of Performance Monitoring.

v0.8.0

• build: Bump required version of Iris (#296)
• fix: avoid unnecessary allocation in Client.processEvent (#293)
• doc: Remove deprecation of sentryhttp.HandleFunc (#284)
• ref: Update sentryhttp example (#283)
• doc: Improve documentation of sentryhttp package (#282)
• doc: Clarify SampleRate documentation (#279)
• fix: Remove RawStacktrace (#278)
• docs: Add example of custom HTTP transport
• ci: Test against go1.15, drop go1.12 support (#271)

NOTE:
This version comes with a few updates. Some examples and documentation have been
improved. We've bumped the supported version of the Iris framework to avoid
LGPL-licensed modules in the module dependency graph.
The Exception.RawStacktrace and Thread.RawStacktrace fields have been
removed to conform to Sentry's ingestion protocol, only Exception.Stacktrace
and Thread.Stacktrace should appear in user code.

v0.7.0

• feat: Include original error when event cannot be encoded as JSON (#258)
• feat: Use Hub from request context when available (#217, #259)
• feat: Extract stack frames from golang.org/x/xerrors (#262)
• feat: Make Environment Integration preserve existing context data (#261)
• feat: Recover and RecoverWithContext with arbitrary types (#268)
• feat: Report bad usage of CaptureMessage and CaptureEvent (#269)
• feat: Send debug logging to stderr by default (#266)
• feat: Several improvements to documentation (#223, #245, #250, #265)
• feat: Example of Recover followed by panic (#241, #247)
• feat: Add Transactions and Spans (to support OpenTelemetry Sentry Exporter) (#235, #243, #254)
• fix: Set either Frame.Filename or Frame.AbsPath (#233)
• fix: Clone requestBody to new Scope (#244)
• fix: Synchronize access and mutation of Hub.lastEventID (#264)
• fix: Avoid repeated syscalls in prepareEvent (#256)
• fix: Do not allocate new RNG for every event (#256)
• fix: Remove stale replace directive in go.mod (#255)
• fix(http): Deprecate HandleFunc, remove duplication (#260)

NOTE:
This version comes packed with several fixes and improvements and no breaking
changes.
Notably, there is a change in how the SDK reports file names in stack traces
that should resolve any ambiguity when looking at stack traces and using the
Suspect Commits feature.
We recommend all users to upgrade.

v0.6.1

• fix: Use NewEvent to init Event struct (#220)

NOTE:
A change introduced in v0.6.0 with the intent of avoiding allocations made a
pattern used in official examples break in certain circumstances (attempting
to write to a nil map).
This release reverts the change such that maps in the Event struct are always
allocated.