Update module github.com/getsentry/sentry-go to v0.31.1 #511
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
v0.30.0
->v0.31.1
Release Notes
getsentry/sentry-go (github.com/getsentry/sentry-go)
v0.31.1
: 0.31.1Compare Source
The Sentry SDK team is happy to announce the immediate availability of Sentry Go SDK v0.31.1.
Bug Fixes
sentry-go/logrus
(#950)v0.31.0
: 0.31.0Compare Source
Breaking Changes
Remove support for metrics. Read more about the end of the Metrics beta here. (#914)
Remove support for profiling. (#915)
Remove
Segment
field from theUser
struct. This field is no longer used in the Sentry product. (#928)Every integration is now a separate module, reducing the binary size and number of dependencies. Once you update
sentry-go
to latest version, you'll need togo get
the integration you want to use. For example, if you want to use theecho
integration, you'll need to rungo get github.com/getsentry/sentry-go/echo
(#919).Features
Add the ability to override
hub
incontext
for integrations that use custom context. (#931)HubProvider
Hook forsentrylogrus
, enabling dynamic Sentry hub allocation for each log entry or goroutine. (#936)This change enhances compatibility with Sentry's recommendation of using separate hubs per goroutine. To ensure a separate Sentry hub for each goroutine, configure the
HubProvider
like this:Bug Fixes
HTTPTranport
to prevent goroutine leaks. (#894)Worker can be also closed by calling
Close()
method on theHTTPTransport
instance.Close
should be called afterFlush
and before terminating the program otherwise some events may be lost.Misc
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.