build(deps): update module github.com/getsentry/sentry-go to v0.23.0
This MR contains the following updates:
| Package | Type | Update | Change |
|---|---|---|---|
| github.com/getsentry/sentry-go | require | minor | v0.18.0 -> v0.23.0 |
MR created with the help of gitlab-org/frontend/renovate-gitlab-bot
Release Notes
getsentry/sentry-go
v0.23.0: 0.23.0
The Sentry SDK team is happy to announce the immediate availability of Sentry Go SDK v0.23.0.
Features
-
Initial support for Cron Monitoring (#661)
This is how the basic usage of the feature looks like:
// 🟡 Notify Sentry your job is running: checkinId := sentry.CaptureCheckIn( &sentry.CheckIn{ MonitorSlug: "<monitor-slug>", Status: sentry.CheckInStatusInProgress, }, nil, ) // Execute your scheduled task here... // 🟢 Notify Sentry your job has completed successfully: sentry.CaptureCheckIn( &sentry.CheckIn{ ID: *checkinId, MonitorSlug: "<monitor-slug>", Status: sentry.CheckInStatusOK, }, nil, )A full example of using Crons Monitoring is available here.
More documentation on configuring and using Crons can be found here.
-
Add support for Event Attachments (#670)
It's now possible to add file/binary payloads to Sentry events:
sentry.ConfigureScope(func(scope *sentry.Scope) { scope.AddAttachment(&Attachment{ Filename: "report.html", ContentType: "text/html", Payload: []byte("<h1>Look, HTML</h1>"), }) })The attachment will then be accessible on the Issue Details page.
-
Add sampling decision to trace envelope header (#666)
-
Expose SpanFromContext function (#672)
Bug fixes
- Make
Span.Finisha no-op when the span is already finished (#660)
v0.22.0: 0.22.0
The Sentry SDK team is happy to announce the immediate availability of Sentry Go SDK v0.22.0.
This release contains initial profiling support, as well as a few bug fixes and improvements.
Features
-
Initial (alpha) support for profiling (#626)
Profiling is disabled by default. To enable it, configure both
TracesSampleRateandProfilesSampleRatewhen initializing the SDK:err := sentry.Init(sentry.ClientOptions{ Dsn: "__DSN__", EnableTracing: true, TracesSampleRate: 1.0, // The sampling rate for profiling is relative to TracesSampleRate. In this case, we'll capture profiles for 100% of transactions. ProfilesSampleRate: 1.0, })More documentation on profiling and current limitations can be found here.
-
Add transactions/tracing support go the Gin integration (#644)
Bug fixes
- Always set a valid source on transactions (#637)
- Clone scope.Context in more places to avoid panics on concurrent reads and writes (#638)
- Fixes #570
- Fix frames recognized as not being in-app still showing as in-app (#647)
v0.21.0: 0.21.0
The Sentry SDK team is happy to announce the immediate availability of Sentry Go SDK v0.21.0.
Note: this release includes one breaking change and some deprecations, which are listed below.
Breaking Changes
This change does not apply if you use https://sentry.io
- Remove support for the
/storeendpoint (#631)- This change requires a self-hosted version of Sentry 20.6.0 or higher. If you are using a version of self-hosted Sentry (aka on-premise) older than 20.6.0, then you will need to upgrade your instance.
Features
- Rename four span option functions (#611, #624)
TransctionSource->WithTransactionSourceSpanSampled->WithSpanSampledOpName->WithOpNameTransactionName->WithTransactionName- Old functions
TransctionSource,SpanSampled,OpName, andTransactionNameare still available but are now deprecated and will be removed in a future release.
- Make
client.EventFromMessageandclient.EventFromExceptionmethods public (#607) - Add
client.SetExceptionmethod (#607)- This allows to set or add errors to an existing
Event.
- This allows to set or add errors to an existing
Bug Fixes
- Protect from panics while doing concurrent reads/writes to Span data fields (#609)
- [otel] Improve detection of Sentry-related spans (#632, #636)
- Fixes cases when HTTP spans containing requests to Sentry were captured by Sentry (#627)
Misc
- Drop testing in (legacy) GOPATH mode (#618)
- Remove outdated documentation from https://pkg.go.dev/github.com/getsentry/sentry-go (#623)
v0.20.0: 0.20.0
The Sentry SDK team is happy to announce the immediate availability of Sentry Go SDK v0.20.0.
Note: this release has some breaking changes, which are listed below.
Breaking Changes
-
Remove the following methods:
Scope.SetTransaction(),Scope.Transaction()(#605)Span.Name should be used instead to access the transaction's name.
For example, the following
TracesSamplerfunction should be now written as follows:Before:
TracesSampler: func(ctx sentry.SamplingContext) float64 { hub := sentry.GetHubFromContext(ctx.Span.Context()) if hub.Scope().Transaction() == "GET /health" { return 0 } return 1 },After:
TracesSampler: func(ctx sentry.SamplingContext) float64 { if ctx.Span.Name == "GET /health" { return 0 } return 1 },
Features
- Add
Span.SetContext()method (#599)- It is recommended to use it instead of
hub.Scope().SetContextwhen setting or updating context on transactions.
- It is recommended to use it instead of
- Add
DebugMetainterface toEventand extendFramestructure with more fields (#606)- More about DebugMeta interface here.
Bug Fixes
- [otel] Fix missing OpenTelemetry context on some events (#599, #605)
- Fixes (#596).
- [otel] Better handling for HTTP span attributes (#610)
Misc
- Bump minimum versions:
github.com/kataras/iris/v12to 12.2.0,github.com/labstack/echo/v4to v4.10.0 (#595) - Bump
google.golang.org/protobufminimum required version to 1.29.1 (#604)- This fixes a potential denial of service issue (CVE-2023-24535).
- Exclude the
otelmodule when building in GOPATH mode (#615)
v0.19.0: 0.19.0
The Sentry SDK team is happy to announce the immediate availability of Sentry Go SDK v0.19.0.
Features
Bug Fixes
- [otel] Use the correct "trace" context when sending a Sentry error (#580)
Misc
- Drop support for Go 1.17, add support for Go 1.20 (#563)
- According to our policy, we're officially supporting the last three minor releases of Go.
- Switch repository license to MIT (#583)
- More about Sentry licensing here.
- Bump
golang.org/x/textminimum required version to 0.3.8 (#586)- This fixes CVE-2022-32149 vulnerability.
Configuration
- If you want to rebase/retry this MR, check this box
This MR has been generated by Renovate Bot.