Bump github.com/getsentry/sentry-go from 0.17.0 to 0.23.0 in /user-service

[dependabot]

Bumps github.com/getsentry/sentry-go from 0.17.0 to 0.23.0.

Release notes

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

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.

... (truncated)

Changelog

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

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>"),
    })
  })

... (truncated)

Commits

• 9ece4d3 release: 0.23.0
• 51688f4 doc: Prepare 0.23.0 release (#680)
• 491f1fd fix(test): Increase Flush timeout for TestKeepAlive test (#681)
• dde4d36 feat: Expose SpanFromContext (#672)
• b551438 fix(crons): Pass correct event types, fix checkin_margin field, add example (...
• 4f72145 feat: Attachments support (#670)
• 4b3a135 feat(crons): initial cron support (#661)
• b6dfea7 Add the sampling decision to the trace envelope header (#666)
• 6db2fc7 fix(tracing): Make Span.Finish a no-op when the span is already finished (#660)
• 1b2ac13 fix: Increase flush timeout in TestHTTPTransport (#663)
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

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

[dependabot]

Superseded by #394.