github-starred/vikunja
2
0
Fork 0
mirror of https://github.com/go-vikunja/vikunja.git synced 2026-05-24 03:31:36 -05:00
Code Issues 690 Packages Projects Releases 11 Wiki Activity

[PR #1659] [MERGED] fix(deps): update module github.com/getsentry/sentry-go/echo to v0.36.0 #1654

New Issue
Closed
opened 2025-11-01 21:24:44 -05:00 by GiteaMirror · 0 comments
GiteaMirror commented 2025-11-01 21:24:44 -05:00
Owner
Copy Link

📋 Pull Request Information

Original PR: https://github.com/go-vikunja/vikunja/pull/1659
Author: @renovate[bot]
Created: 10/14/2025
Status: ✅ Merged
Merged: 10/14/2025
Merged by: @kolaente

Base: main ← Head: renovate/github.com-getsentry-sentry-go-echo-0.x

📝 Commits (1)

  • 164b75b fix(deps): update module github.com/getsentry/sentry-go/echo to v0.36.0

📊 Changes

2 files changed (+3 additions, -1 deletions)

View changed files

📝 go.mod (+1 -1)
📝 go.sum (+2 -0)

📄 Description

This PR contains the following updates:

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

Release Notes

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

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 - At any time (no schedule defined), 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.

🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/go-vikunja/vikunja/pull/1659 **Author:** [@renovate[bot]](https://github.com/apps/renovate) **Created:** 10/14/2025 **Status:** ✅ Merged **Merged:** 10/14/2025 **Merged by:** [@kolaente](https://github.com/kolaente) **Base:** `main` ← **Head:** `renovate/github.com-getsentry-sentry-go-echo-0.x` --- ### 📝 Commits (1) - [`164b75b`](https://github.com/go-vikunja/vikunja/commit/164b75b8dc89b47170aaf7cea82ddf22ac4cb12c) fix(deps): update module github.com/getsentry/sentry-go/echo to v0.36.0 ### 📊 Changes **2 files changed** (+3 additions, -1 deletions) <details> <summary>View changed files</summary> 📝 `go.mod` (+1 -1) 📝 `go.sum` (+2 -0) </details> ### 📄 Description This PR contains the following updates: | Package | Change | Age | Confidence | |---|---|---|---| | [github.com/getsentry/sentry-go/echo](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%2fecho/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%2fecho/v0.35.3/v0.36.0?slim=true)](https://docs.renovatebot.com/merge-confidence/) | --- ### Release Notes <details> <summary>getsentry/sentry-go (github.com/getsentry/sentry-go/echo)</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 ([#&#8203;1106](https://redirect.github.com/getsentry/sentry-go/pull/1106))) - The changes to error handling ([#&#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 ([#&#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 ([#&#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 ([#&#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 ([#&#8203;1103](https://redirect.github.com/getsentry/sentry-go/pull/1103)) </details> --- ### Configuration 📅 **Schedule**: Branch creation - At any time (no schedule defined), 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/go-vikunja/vikunja). <!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiI0MS4xNDMuMSIsInVwZGF0ZWRJblZlciI6IjQxLjE0My4xIiwidGFyZ2V0QnJhbmNoIjoibWFpbiIsImxhYmVscyI6WyJkZXBlbmRlbmNpZXMiXX0=--> --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
GiteaMirror added the pull-request label 2025-11-01 21:24:44 -05:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
area/api
area/attachments
area/auth
area/avatars
area/backup-restore
area/caldav
area/calendar-view
area/comments
area/config
area/database
area/desktop
area/docker
area/email
area/favorites
area/filters
area/frontend
area/gantt
area/i18n
area/import-export
area/internal-code
area/kanban
area/labels
area/list-view
area/mobile
area/notifications
area/permissions
area/projects
area/pwa
area/recurring-tasks
area/reminders
area/search
area/shortcuts
area/subtasks
area/sync
area/table-view
area/task-editor
area/task-metadata
area/task-relations
area/teams
area/theming
area/time-tracking
area/typesense
area/views
area/webhooks
bug
changes requested
concern/accessibility
concern/performance
concern/regression
concern/ux
confirmed
db/mysql
dependencies
enhancement
good first issue
help wanted
integration/inbound
integration/outbound
kind/bug
kind/feature
needs reproduction
pull-request
Mirrored from GitHub Pull Request
 question
security
support
upstream issue
waiting for reply
wontfix
No Label pull-request
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/vikunja#1654
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?