Skip to content

Conversation

@renovate
Copy link
Contributor

@renovate renovate bot commented Oct 14, 2025

This PR contains the following updates:

Package Change Age Confidence
github.com/getsentry/sentry-go v0.35.3 -> v0.36.0 age confidence

Warning

Some dependencies could not be looked up. Check the Dependency Dashboard for more information.


Release Notes

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

v0.36.0: 0.36.0

Compare Source

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

Breaking Changes
  • Behavioral change for the MaxBreadcrumbs client option. Removed the hard limit of 100 breadcrumbs, allowing users to set a larger limit and also changed the default limit from 30 to 100 (#​1106))

  • The changes to error handling (#​1075) will affect issue grouping. It is expected that any wrapped and complex errors will be grouped under a new issue group.

Features
  • Add support for improved issue grouping with enhanced error chain handling (#​1075)

    The SDK now provides better handling of complex error scenarios, particularly when dealing with multiple related errors or error chains. This feature automatically detects and properly structures errors created with Go's errors.Join() function and other multi-error patterns.

    // Multiple errors are now properly grouped and displayed in Sentry
    err1 := errors.New("err1")
    err2 := errors.New("err2") 
    combinedErr := errors.Join(err1, err2)
    
    // When captured, these will be shown as related exceptions in Sentry
    sentry.CaptureException(combinedErr)
  • Add TraceIgnoreStatusCodes option to allow filtering of HTTP transactions based on status codes (#​1089)

    • Configure which HTTP status codes should not be traced by providing single codes or ranges
    • Example: TraceIgnoreStatusCodes: [][]int{{404}, {500, 599}} ignores 404 and server errors 500-599
Bug Fixes
  • Fix logs being incorrectly filtered by BeforeSend callback (#​1109)
    • Logs now bypass the processEvent method and are sent directly to the transport
    • This ensures logs are only filtered by BeforeSendLog, not by the error/message BeforeSend callback
Misc
  • Add support for Go 1.25 and drop support for Go 1.22 (#​1103)

Configuration

📅 Schedule: Branch creation - "on tuesday" (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.


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

This PR was generated by Mend Renovate. View the repository job log.

@renovate renovate bot added dependencies Pull requests that update a dependency file renovatebot labels Oct 14, 2025
@renovate renovate bot requested a review from a team as a code owner October 14, 2025 13:12
@renovate renovate bot requested a review from songy23 October 14, 2025 13:12
@renovate renovate bot added dependencies Pull requests that update a dependency file renovatebot labels Oct 14, 2025
@github-actions github-actions bot requested a review from AbhiPrasad October 14, 2025 13:12
@songy23 songy23 merged commit e68cd60 into main Oct 14, 2025
185 checks passed
@songy23 songy23 deleted the renovate/github.com-getsentry-sentry-go-0.x branch October 14, 2025 13:55
@github-actions github-actions bot added this to the next release milestone Oct 14, 2025
ChrsMark pushed a commit to ChrsMark/opentelemetry-collector-contrib that referenced this pull request Oct 20, 2025
…ry#43540)

This PR contains the following updates:

| Package | Change | Age | Confidence |
|---|---|---|---|
|
[github.com/getsentry/sentry-go](https://redirect.github.com/getsentry/sentry-go)
| `v0.35.3` -> `v0.36.0` |
[![age](https://developer.mend.io/api/mc/badges/age/go/github.com%2fgetsentry%2fsentry-go/v0.36.0?slim=true)](https://docs.renovatebot.com/merge-confidence/)
|
[![confidence](https://developer.mend.io/api/mc/badges/confidence/go/github.com%2fgetsentry%2fsentry-go/v0.35.3/v0.36.0?slim=true)](https://docs.renovatebot.com/merge-confidence/)
|

---

> [!WARNING]
> Some dependencies could not be looked up. Check the Dependency
Dashboard for more information.

---

### Release Notes

<details>
<summary>getsentry/sentry-go (github.com/getsentry/sentry-go)</summary>

###
[`v0.36.0`](https://redirect.github.com/getsentry/sentry-go/releases/tag/v0.36.0):
0.36.0

[Compare
Source](https://redirect.github.com/getsentry/sentry-go/compare/v0.35.3...v0.36.0)

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

##### Breaking Changes

- Behavioral change for the `MaxBreadcrumbs` client option. Removed the
hard limit of 100 breadcrumbs, allowing users to set a larger limit and
also changed the default limit from 30 to 100
([#&open-telemetry#8203;1106](https://redirect.github.com/getsentry/sentry-go/pull/1106)))

- The changes to error handling
([#&open-telemetry#8203;1075](https://redirect.github.com/getsentry/sentry-go/pull/1075))
will affect issue grouping. It is expected that any wrapped and complex
errors will be grouped under a new issue group.

##### Features

- Add support for improved issue grouping with enhanced error chain
handling
([#&open-telemetry#8203;1075](https://redirect.github.com/getsentry/sentry-go/pull/1075))

The SDK now provides better handling of complex error scenarios,
particularly when dealing with multiple related errors or error chains.
This feature automatically detects and properly structures errors
created with Go's `errors.Join()` function and other multi-error
patterns.

  ```go
  // Multiple errors are now properly grouped and displayed in Sentry
  err1 := errors.New("err1")
  err2 := errors.New("err2") 
  combinedErr := errors.Join(err1, err2)

  // When captured, these will be shown as related exceptions in Sentry
  sentry.CaptureException(combinedErr)
  ```

- Add `TraceIgnoreStatusCodes` option to allow filtering of HTTP
transactions based on status codes
([#&open-telemetry#8203;1089](https://redirect.github.com/getsentry/sentry-go/pull/1089))
- Configure which HTTP status codes should not be traced by providing
single codes or ranges
- Example: `TraceIgnoreStatusCodes: [][]int{{404}, {500, 599}}` ignores
404 and server errors 500-599

##### Bug Fixes

- Fix logs being incorrectly filtered by `BeforeSend` callback
([#&open-telemetry#8203;1109](https://redirect.github.com/getsentry/sentry-go/pull/1109))
- Logs now bypass the `processEvent` method and are sent directly to the
transport
- This ensures logs are only filtered by `BeforeSendLog`, not by the
error/message `BeforeSend` callback

##### Misc

- Add support for Go 1.25 and drop support for Go 1.22
([#&open-telemetry#8203;1103](https://redirect.github.com/getsentry/sentry-go/pull/1103))

</details>

---

### Configuration

📅 **Schedule**: Branch creation - "on tuesday" (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.

---

- [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check
this box

---

This PR was generated by [Mend Renovate](https://mend.io/renovate/).
View the [repository job
log](https://developer.mend.io/github/open-telemetry/opentelemetry-collector-contrib).

<!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiI0MS4xNDMuMSIsInVwZGF0ZWRJblZlciI6IjQxLjE0My4xIiwidGFyZ2V0QnJhbmNoIjoibWFpbiIsImxhYmVscyI6WyJkZXBlbmRlbmNpZXMiLCJyZW5vdmF0ZWJvdCJdfQ==-->

---------

Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
Co-authored-by: otelbot <[email protected]>
Co-authored-by: Yang Song <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Pull requests that update a dependency file exporter/sentry renovatebot

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants