github-starred/vikunja
2
0
Fork 0
mirror of https://github.com/go-vikunja/vikunja.git synced 2025-12-05 19:16:51 -06:00
Code Issues 219 Packages Projects Releases 2 Wiki Activity

[PR #1699] [CLOSED] fix(deps): update module github.com/getsentry/sentry-go to v0.36.2 - autoclosed #1688

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

📋 Pull Request Information

Original PR: https://github.com/go-vikunja/vikunja/pull/1699
Author: @renovate[bot]
Created: 10/21/2025
Status: ❌ Closed

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

📝 Commits (1)

  • 1dd446f fix(deps): update module github.com/getsentry/sentry-go to v0.36.2

📊 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 v0.36.1 -> v0.36.2 age confidence

Release Notes

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

v0.36.2: 0.36.2

Compare Source

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

Bug Fixes
  • Fix context propagation for logs to ensure logger instances correctly inherit span and hub information from their creation context (#​1118)
    • Logs now properly propagate trace context from the logger's original context, even when emitted in a different context
    • The logger will first check the emission context, then fall back to its creation context, and finally to the current hub

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/1699 **Author:** [@renovate[bot]](https://github.com/apps/renovate) **Created:** 10/21/2025 **Status:** ❌ Closed **Base:** `main` ← **Head:** `renovate/github.com-getsentry-sentry-go-0.x` --- ### 📝 Commits (1) - [`1dd446f`](https://github.com/go-vikunja/vikunja/commit/1dd446fc369e3b7dd4b0a67ff106d52f1fc28f56) fix(deps): update module github.com/getsentry/sentry-go to v0.36.2 ### 📊 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](https://redirect.github.com/getsentry/sentry-go) | `v0.36.1` -> `v0.36.2` | [![age](https://developer.mend.io/api/mc/badges/age/go/github.com%2fgetsentry%2fsentry-go/v0.36.2?slim=true)](https://docs.renovatebot.com/merge-confidence/) | [![confidence](https://developer.mend.io/api/mc/badges/confidence/go/github.com%2fgetsentry%2fsentry-go/v0.36.1/v0.36.2?slim=true)](https://docs.renovatebot.com/merge-confidence/) | --- ### Release Notes <details> <summary>getsentry/sentry-go (github.com/getsentry/sentry-go)</summary> ### [`v0.36.2`](https://redirect.github.com/getsentry/sentry-go/releases/tag/v0.36.2): 0.36.2 [Compare Source](https://redirect.github.com/getsentry/sentry-go/compare/v0.36.1...v0.36.2) The Sentry SDK team is happy to announce the immediate availability of Sentry Go SDK v0.36.2. ##### Bug Fixes - Fix context propagation for logs to ensure logger instances correctly inherit span and hub information from their creation context ([#&#8203;1118](https://redirect.github.com/getsentry/sentry-go/pull/1118)) - Logs now properly propagate trace context from the logger's original context, even when emitted in a different context - The logger will first check the emission context, then fall back to its creation context, and finally to the current hub </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:eyJjcmVhdGVkSW5WZXIiOiI0MS4xNTYuMSIsInVwZGF0ZWRJblZlciI6IjQxLjE1OS40IiwidGFyZ2V0QnJhbmNoIjoibWFpbiIsImxhYmVscyI6WyJkZXBlbmRlbmNpZXMiXX0=--> --- <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:25:29 -05:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
area/api
area/caldav
area/filters
area/frontend
area/gantt
area/internal-code
area/typesense
bug
changes requested
confirmed
dependencies
enhancement
good first issue
help wanted
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#1688
No description provided.
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?