ref!: remove hub API

[giortzisg]

Description

This removes the hub API along with any final migrations to the scopes context model.

Issues

Changelog Entry Instructions

To add a custom changelog entry, uncomment the section above. Supports:

• Single entry: just write text
• Multiple entries: use bullet points
• Nested bullets: indent 4+ spaces

For more details: custom changelog entries

Reminders

• Add GH Issue ID & Linear ID
• PR title should use conventional commit style (feat:, fix:, ref:, meta:)
• For external contributors: CONTRIBUTING.md, Sentry SDK development docs, Discord community

---

_{Stack created with GitHub Stacks CLI • Give Feedback 💬}

Changelog Entry

• Remove the Hub API. Scopes and clients are now carried on context.Context, so users need to pass the request or job context to Sentry functions instead of using a hub. See the migration guide for every replacement.
  • CaptureException, CaptureMessage, CaptureEvent, CaptureCheckIn, AddBreadcrumb, Recover and WithMonitor now take a context as their first argument. Hints and levels are passed as options, such as sentry.WithEventHint(hint) and sentry.WithLevel(level).
  • Use ctx, scope := sentry.WithScope(ctx) to isolate data for a request or job, instead of cloning a hub or calling PushScope. Use sentry.GlobalScope() for application-wide data, instead of ConfigureScope.
  • Use sentry.ScopeFromContext(ctx) and sentry.ClientFromContext(ctx) to read the current scope and client, and sentry.ContextWithScope and sentry.ContextWithClient to attach your own, instead of NewHub and SetHubOnContext.
  • In Gin, Echo, Iris, Fiber and FastHTTP handlers, call the integration's GetContext(c) and pass the result to Sentry functions. GetHubFromContext, SetHubOnContext and GetSpanFromContext are removed.
  • Use sentry.ContinueFromHeaders(trace, baggage) to continue a trace and sentry.SpanFromContext(ctx) to read the active span. ContinueTrace, ContinueFromTrace, Scope.GetSpan and Scope.SetSpan are removed.
  • EventModifier and the Client.EventFromMessage, EventFromException and EventFromCheckIn helpers are removed. Use BeforeSend or an event processor to modify events.
  • Tags and a level set directly on an event are no longer overwritten by the scope.
  • sentry.AddBreadcrumb and sentry.LastEventID need a context that carries a scope. On a bare context such as context.Background() the breadcrumb is dropped and the ID is empty. Users should create a scope with sentry.WithScope first.
  • A context that carries neither a scope nor a span, such as context.Background(), no longer propagates a trace. GetTraceparent, GetTraceparentW3C and GetBaggage return an empty string for it, outgoing HTTP and gRPC requests made with it carry no trace headers, and each event, log and metric captured with it gets its own trace ID. Requests handled by the middleware and contexts from sentry.WithScope are unaffected.

// Before: isolate a request
hub := sentry.CurrentHub().Clone()
hub.Scope().SetTag("route", "checkout")
ctx := sentry.SetHubOnContext(r.Context(), hub)
hub.CaptureException(err)

// After: isolate a request
ctx, scope := sentry.WithScope(r.Context())
scope.SetTag("route", "checkout")
sentry.CaptureException(ctx, err)

// Before: use your own client
hub := sentry.NewHub(client, sentry.NewScope())
ctx := sentry.SetHubOnContext(r.Context(), hub)

// After: use your own client
ctx := sentry.ContextWithClient(r.Context(), client)

// Before, in a Gin handler
sentrygin.GetHubFromContext(c).CaptureException(err)

// After, in a Gin handler
sentry.CaptureException(sentrygin.GetContext(c), err)

[cursor]

Cursor Bugbot has reviewed your changes and found 1 potential issue.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

^{Reviewed by Cursor Bugbot for commit 1b0d8cb. Configure here.}

[szokeasaurusrex]

🧼 🗑️ 🔥