Bump github.com/getsentry/sentry-go from 0.9.0 to 0.13.0

[dependabot[bot]]

Bumps github.com/getsentry/sentry-go from 0.9.0 to 0.13.0.

Release notes

Sourced from github.com/getsentry/sentry-go's releases.

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)

Changelog

Sourced from github.com/getsentry/sentry-go's changelog.

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: 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)

Commits

• 88bad6b release: 0.13.0
• 661c7b2 misc: v0.13.0 changelog (#421)
• 84bdf72 ci: Add craft release automation (#422)
• b1bb14d ref: Change DSN ProjectID to be a string (#420)
• 8c2dbee ci: Bump golangci-lint version in GH workflow (#419)
• 00808a3 build: Bump gin-gonic/gin from v1.4.0 to v1.7.7 (#412)
• c40f30a misc: Update deprecated linters and fix code for remaining rules (#418)
• e79cca5 ci: Update GraphQL config with appropriate permissions (#417)
• 5c2f2a7 fix: When extracting PCs from stack frames, try the PC field (#393)
• dc2eb25 build: Bump Go version in go.mod (#410)
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)