Bump github.com/getsentry/sentry-go from 0.10.0 to 0.14.0

[dependabot]

Bumps github.com/getsentry/sentry-go from 0.10.0 to 0.14.0.

Release notes

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

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.

Changelog

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

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

Commits

• e7611f7 release: 0.14.0
• 82cd3e4 ci: Change changelogPolicy to auto (#478)
• 23801d7 deps: Update all dependencies, add go1.19, drop go1.16, prepare changelog
• 58adf6c ref: Replace deprecated ioutil pkg with os & io
• ce36dbb misc: Tweak readme, assume new users are using go modules
• 64b90ef ref: Minor code cleanup and ExtractStacktrace benchmarks (#469)
• 5e27377 ref: Optimize stacktrace from size and speed (#467)
• 33f7b69 Dependency update to fix CVEs (#464)
• 576cf05 deps: Update dependencies to resolve a few CVEs (#462)
• 26ea603 readme: drop forum for discussions (#449)
• 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)

[dependabot]

Superseded by #174.