Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update module github.com/getsentry/sentry-go to v0.31.1 #768

Merged
merged 1 commit into from
Jan 10, 2025

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Jan 3, 2025

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
github.com/getsentry/sentry-go v0.30.0 -> v0.31.1 age adoption passing confidence

⚠️ Warning

These modules are almost certainly going to break everything. They do every time they update. If you update even one repo's OTEL modules, go will then pull in new versions due to MVS which will cause your repo to break. All otel pull requests need to be merged basically at the same time, and after all of the modules have been updated to be compatible with each other.


Release Notes

getsentry/sentry-go (github.com/getsentry/sentry-go)

v0.31.1: 0.31.1

Compare Source

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)

v0.31.0: 0.31.0

Compare 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 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()

Worker can be also closed by calling Close() method on the HTTPTransport instance. Close should be called after Flush and before terminating the program otherwise some events may be lost.

transport := sentry.NewHTTPTransport()
defer transport.Close()
Misc

Configuration

📅 Schedule: Branch creation - "before 4pm on friday" in timezone Europe/London, Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@DavidS-ovm DavidS-ovm merged commit f732102 into main Jan 10, 2025
8 of 10 checks passed
@DavidS-ovm DavidS-ovm deleted the renovate/opentelemetry-go branch January 10, 2025 10:00
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant