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

0.31.1

The Sentry SDK team is happy to announce the immediate availability of Sentry Go SDK v0.31.1.

Bug Fixes

• Correct wrong module name for sentry-go/logrus (#950)

0.31.0

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 the User 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 to go get the integration you want to use. For example, if you want to use the echo integration, you'll need to run go get github.com/getsentry/sentry-go/echo (#919).

Features

• Add the ability to override hub in context for integrations that use custom context. (#931)

• Add HubProvider Hook for sentrylogrus, 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:

hook, err := sentrylogrus.New(nil, sentry.ClientOptions{})
if err != nil {
    log.Fatalf("Failed to initialize Sentry hook: %v", err)
}
// Set a custom HubProvider to generate a new hub for each goroutine or log entry
hook.SetHubProvider(func() *sentry.Hub {
client, _ := sentry.NewClient(sentry.ClientOptions{})
return sentry.NewHub(client, sentry.NewScope())
})
logrus.AddHook(hook)

Bug Fixes

• Add support for closing worker goroutines started by the HTTPTranport to prevent goroutine leaks. (#894)

client, _ := sentry.NewClient()
defer client.Close()

... (truncated)

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

0.31.1

The Sentry SDK team is happy to announce the immediate availability of Sentry Go SDK v0.31.1.

Bug Fixes

• Correct wrong module name for sentry-go/logrus (#950)

0.31.0

The Sentry SDK team is happy to announce the immediate availability of Sentry Go SDK v0.31.0.

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 the User 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 to go get the integration you want to use. For example, if you want to use the echo integration, you'll need to run go get github.com/getsentry/sentry-go/echo (#919).

Features

Add the ability to override hub in context for integrations that use custom context. (#931)

• Add HubProvider Hook for sentrylogrus, 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:

hook, err := sentrylogrus.New(nil, sentry.ClientOptions{})
if err != nil {
    log.Fatalf("Failed to initialize Sentry hook: %v", err)
}
// Set a custom HubProvider to generate a new hub for each goroutine or log entry
hook.SetHubProvider(func() *sentry.Hub {
client, _ := sentry.NewClient(sentry.ClientOptions{})
return sentry.NewHub(client, sentry.NewScope())
})
logrus.AddHook(hook)

Bug Fixes

• Add support for closing worker goroutines started by the HTTPTranport to prevent goroutine leaks. (#894)

</tr></table> 

... (truncated)

• 454d469 Fix lint CI
• 82b1d7a release: 0.31.1
• 08c2b0f Prepare 0.31.1 (#951)
• e0b4d38 Rename sentry-go/logrus module (#950)
• 96cc6a8 Merge branch 'release/0.31.0'
• 17ceb6c Bump golangci-lint
• 9f9f465 release: 0.31.0
• 934eca5 Prepare 0.31.0 (#948)
• 066c69e Add HubProvider functionality to the logrus integration (#936)
• 486c78c Bump golang.org/x/net to 0.33.0 (#947)
• Additional commits viewable in compare view

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 show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @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)