brave / go-sync

Brave sync server v2
Mozilla Public License 2.0
185 stars 44 forks source link

Update module github.com/getsentry/sentry-go to v0.28.0 #276

Closed renovate[bot] closed 2 months ago

renovate[bot] commented 2 months ago

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
github.com/getsentry/sentry-go v0.27.0 -> v0.28.0 age adoption passing confidence

Release Notes

getsentry/sentry-go (github.com/getsentry/sentry-go) ### [`v0.28.0`](https://togithub.com/getsentry/sentry-go/releases/tag/v0.28.0): 0.28.0 [Compare Source](https://togithub.com/getsentry/sentry-go/compare/v0.27.0...v0.28.0) The Sentry SDK team is happy to announce the immediate availability of Sentry Go SDK v0.28.0. ##### Features - Add a `Fiber` performance tracing & error reporting integration ([#​795](https://togithub.com/getsentry/sentry-go/pull/795)) - Add performance tracing to the `Echo` integration ([#​722](https://togithub.com/getsentry/sentry-go/pull/722)) - Add performance tracing to the `FastHTTP` integration ([#​732](https://togithub.com/getsentry/sentry-go/pull/723)) - Add performance tracing to the `Iris` integration ([#​809](https://togithub.com/getsentry/sentry-go/pull/809)) - Add performance tracing to the `Negroni` integration ([#​808](https://togithub.com/getsentry/sentry-go/pull/808)) - Add `FailureIssueThreshold` & `RecoveryThreshold` to `MonitorConfig` ([#​775](https://togithub.com/getsentry/sentry-go/pull/775)) - Use `errors.Unwrap()` to create exception groups ([#​792](https://togithub.com/getsentry/sentry-go/pull/792)) - Add support for matching on strings for `ClientOptions.IgnoreErrors` & `ClientOptions.IgnoreTransactions` ([#​819](https://togithub.com/getsentry/sentry-go/pull/819)) - Add `http.request.method` attribute for performance span data ([#​786](https://togithub.com/getsentry/sentry-go/pull/786)) - Accept `interface{}` for span data values ([#​784](https://togithub.com/getsentry/sentry-go/pull/784)) ##### Fixes - Fix missing stack trace for parsing error in `logrusentry` ([#​689](https://togithub.com/getsentry/sentry-go/pull/689))

Configuration

📅 Schedule: Branch creation - " 0-4 * 3" (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

â™» Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

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



This PR has been generated by Mend Renovate. View repository job log here.

renovate[bot] commented 2 months ago

ℹ Artifact update notice

File name: go.mod

In order to perform the update(s) described in the table above, Renovate ran the go get command, which resulted in the following additional change(s):

Details: Package Change
golang.org/x/crypto v0.17.0 -> v0.19.0
golang.org/x/sys v0.16.0 -> v0.18.0
github-actions[bot] commented 2 months ago

[puLL-Merge] - getsentry/sentry-go@otel/v0.27.0..otel/v0.28.0

Here is my review of the PR:

Description

This PR makes several changes and additions to the Sentry Go SDK:

The motivation seems to be enhancing the SDK's capabilities, especially around performance tracing, error grouping, and metrics. The changes look reasonable and well-scoped.

Changes ### Changes - Multiple integrations: - Add performance tracing instrumentation - Add GetSpan/TransactionFromContext() helper methods - Update README and add examples for tracing - client.go: - Allow strings for IgnoreErrors/IgnoreTransactions matching - Update tests - interfaces.go: - Improve SetException to use errors.Unwrap and add grouping - Add Metrics field to Event struct - metrics.go, metrics_test.go: Add initial implementation for sending metric data - check_in.go: Add new FailureIssueThreshold and RecoveryThreshold fields - Bump Go version matrix to 1.18-1.22 - Update CHANGELOGs, READMEs and links to Go package docs - Update dependencies including Fiber and Iris - Other test additions and improvements The changes are spread across multiple packages but are fairly isolated. The metrics implementation, error grouping improvements, and performance instrumentation make up the bulk of the PR.

Possible Issues

No major issues jump out. A few minor notes:

Security Hotspots

I didn't see any obvious security risks introduced by this change. A few areas that handle untrusted input, but they look to be adequately sanitized:

Let me know if you have any other questions!