Bump github.com/getsentry/sentry-go from 0.31.1 to 0.33.0

[dependabot]

Bumps github.com/getsentry/sentry-go from 0.31.1 to 0.33.0.

Release notes

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

0.33.0

The Sentry SDK team is happy to announce the immediate availability of Sentry Go SDK v0.33.0.

Breaking Changes

• Rename the internal Logger to DebugLogger. This feature was only used when you set Debug: True in your sentry.Init() call. If you haven't used the Logger directly, no changes are necessary. (#1012)

Features

• Add support for Structured Logging. (#1010)

  logger := sentry.NewLogger(ctx)
  logger.Info(ctx, "Hello, Logs!")

  You can learn more about Sentry Logs on our docs and the examples.

• Add new attributes APIs, which are currently only exposed on logs. (#1007)

Bug Fixes

• Do not push a new scope on StartSpan. (#1013)
• Fix an issue where the propagated smapling decision wasn't used. (#995)
• [Otel] Prefer httpRoute over httpTarget for span descriptions. (#1002)

Misc

• Update github.com/stretchr/testify to v1.8.4. (#988)

0.32.0

The Sentry SDK team is happy to announce the immediate availability of Sentry Go SDK v0.32.0.

Breaking Changes

• Bump the minimum Go version to 1.22. The supported versions are 1.22, 1.23 and 1.24. (#967)
• Setting any values on span.Extra has no effect anymore. Use SetData(name string, value interface{}) instead. (#864)

Features

• Add a MockTransport and MockScope. (#972)

Bug Fixes

• Fix writing *http.Request in the Logrus JSONFormatter. (#955)

Misc

• Transaction data attributes are now seralized as trace context data attributes, allowing you to query these attributes in the Trace Explorer.

Changelog

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

0.33.0

The Sentry SDK team is happy to announce the immediate availability of Sentry Go SDK v0.33.0.

Breaking Changes

• Rename the internal Logger to DebugLogger. This feature was only used when you set Debug: True in your sentry.Init() call. If you haven't used the Logger directly, no changes are necessary. (#1012)

Features

• Add support for Structured Logging. (#1010)

  logger := sentry.NewLogger(ctx)
  logger.Info(ctx, "Hello, Logs!")

  You can learn more about Sentry Logs on our docs and the examples.

• Add new attributes APIs, which are currently only exposed on logs. (#1007)

Bug Fixes

• Do not push a new scope on StartSpan. (#1013)
• Fix an issue where the propagated smapling decision wasn't used. (#995)
• [Otel] Prefer httpRoute over httpTarget for span descriptions. (#1002)

Misc

• Update github.com/stretchr/testify to v1.8.4. (#988)

0.32.0

The Sentry SDK team is happy to announce the immediate availability of Sentry Go SDK v0.32.0.

Breaking Changes

• Bump the minimum Go version to 1.22. The supported versions are 1.22, 1.23 and 1.24. (#967)
• Setting any values on span.Extra has no effect anymore. Use SetData(name string, value interface{}) instead. (#864)

Features

• Add a MockTransport and MockScope. (#972)

Bug Fixes

• Fix writing *http.Request in the Logrus JSONFormatter. (#955)

Misc

... (truncated)

Commits

• 03a4deb release: 0.33.0
• 34ba180 Prepare 0.33.0 (#1016)
• c340089 Add initial logger implementation (#1010)
• 00a135a Do not push a new scope on StartSpan (#1013)
• 64de096 Rename Logger to DebugLogger (#1012)
• 523e1b4 Bump github.com/stretchr/testify on otel submodule (#1011)
• bf20c9f Prefer http route over http target for span description (#1002)
• 021ccc1 Add attributes API (#1007)
• c7d162c Update github.com/stretchr/testify to v1.8.4 (#988)
• a309f56 build(deps): bump actions/create-github-app-token from 1.11.5 to 1.12.0 (#987)
• 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 show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @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)

[openshift-ci]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: dependabot[bot]
Once this PR has been reviewed and has the lgtm label, please assign vladbologa for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[openshift-ci]

Hi @dependabot[bot]. Thanks for your PR.

I'm waiting for a stackrox member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.