build(deps): update module github.com/getsentry/sentry-go to v0.44.1

GitLab Dependency Botrequested to merge
gitlab-renovate-forks/container-registry:renovate/github.com-getsentry-sentry-go-0.x into master

This MR contains the following updates:

Package Type Update Change
github.com/getsentry/sentry-go require minor v0.42.0 -> v0.44.1

MR created with the help of gitlab-org/frontend/renovate-gitlab-bot

Release Notes

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

v0.44.1: 0.44.1

Compare Source

[!NOTE]
v0.44.0 had to be released as v0.44.1 due to a technical issue.

New Features ✨
  • Add RemoveAttribute api on the scope. by @​giortzisg in #​1224
  • Deprecate Scope.SetExtra, Scope.SetExtras, and Scope.RemoveExtra in favor of Scope.SetAttributes and Scope.RemoveAttribute by @​giortzisg in #​1224
    • The recommended migration path is to use SetAttributes to attach values to logs and metrics. Note that attributes do not appear on error events; if you only capture errors, use SetTag or SetContext instead.
    • Before:
    scope.SetExtra("key.string", "str")
scope.SetExtra("key.int", 42)
    • After (for error events) — use tags and contexts:
    scope.SetTag("key.string", "str")
scope.SetContext("my_data", sentry.Context{"key.int": 42})
    • After (for logs and metrics) — use attributes:
    scope.SetAttributes(
    attribute.String("key.string", "str"),
    attribute.Int("key.int", 42),
)
  • Add support for homogenous arrays by @​giortzisg in #​1203
  • Add support for client reports by @​giortzisg in #​1192
  • Add org id propagation in sentry_baggage by @​giortzisg in #​1210
  • Add OrgID and StrictTraceContinuation client options. by @​giortzisg in #​1210
  • Add the option to set attributes on the scope by @​giortzisg in #​1208
Bug Fixes 🐛
Internal Changes 🔧
Ai
Deps
Other

v0.44.0: 0.44.0

Compare Source

[!NOTE]
v0.44.0 had to be released as v0.44.1 due to a technical issue.

New Features ✨
  • Add RemoveAttribute api on the scope. by @​giortzisg in #​1224
  • Deprecate Scope.SetExtra, Scope.SetExtras, and Scope.RemoveExtra in favor of Scope.SetAttributes and Scope.RemoveAttribute by @​giortzisg in #​1224
    • The recommended migration path is to use SetAttributes to attach values to logs and metrics. Note that attributes do not appear on error events; if you only capture errors, use SetTag or SetContext instead.
    • Before:
    scope.SetExtra("key.string", "str")
scope.SetExtra("key.int", 42)
    • After (for error events) — use tags and contexts:
    scope.SetTag("key.string", "str")
scope.SetContext("my_data", sentry.Context{"key.int": 42})
    • After (for logs and metrics) — use attributes:
    scope.SetAttributes(
    attribute.String("key.string", "str"),
    attribute.Int("key.int", 42),
)
  • Add support for homogenous arrays by @​giortzisg in #​1203
  • Add support for client reports by @​giortzisg in #​1192
  • Add org id propagation in sentry_baggage by @​giortzisg in #​1210
  • Add OrgID and StrictTraceContinuation client options. by @​giortzisg in #​1210
  • Add the option to set attributes on the scope by @​giortzisg in #​1208
Bug Fixes 🐛
Internal Changes 🔧
Ai
Deps
Other

v0.43.0: 0.43.0

Compare Source

Breaking Changes 🛠️
  • Add support for go 1.26 by @​giortzisg in #​1193
    • bump minimum supported go version to 1.24
  • change type signature of attributes for Logs and Metrics. by @​giortzisg in #​1205
    • users are not supposed to modify Attributes directly on the Log/Metric itself, but this is still is a breaking change on the type.
  • Send uint64 overflowing attributes as numbers. by @​giortzisg in #​1198
    • The SDK was converting overflowing uint64 attributes to strings for slog and logrus integrations. To eliminate double types for these attributes, the SDK now sends the overflowing attribute as is, and lets the server handle the overflow appropriately.
    • It is expected that overflowing unsigned integers would now get dropped, instead of converted to strings.
New Features ✨
Bug Fixes 🐛
Internal Changes 🔧
Deps
Other

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 MR becomes conflicted, or you tick the rebase/retry checkbox.

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

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

This MR has been generated by Renovate Bot.

Merge request reports