deps(dotnet): Bump Sentry and Sentry.NLog#35
Conversation
Bumps Sentry from 6.0.0 to 6.1.0 Bumps Sentry.NLog from 6.0.0 to 6.1.0 --- updated-dependencies: - dependency-name: Sentry dependency-version: 6.1.0 dependency-type: direct:production update-type: version-update:semver-minor - dependency-name: Sentry.NLog dependency-version: 6.1.0 dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>
AI AnalysisTechnical Summary: This pull request updates the Key Updates and Features:
This summary was automatically generated by AI to help with triage and may not be 100% accurate. Suggested Labels: enhancement |
karlspace
left a comment
There was a problem hiding this comment.
✅ Review: Sentry & Sentry.NLog 6.0.0 → 6.1.0
Bewertung: Unbedenklich — Minor-Update
Beide Pakete werden konsistent von 6.0.0 auf 6.1.0 angehoben. Minor-Releases bringen in der Regel neue Features bei voller Abwärtskompatibilität mit.
Änderungen geprüft:
Directory.Packages.props: Sentry6.0.0→6.1.0Directory.Packages.props: Sentry.NLog6.0.0→6.1.0
Schön, dass beide Sentry-Pakete synchron aktualisiert werden — das vermeidet potenzielle Versionskonflikte im Sentry-Ökosystem.
Hinweis zum CI-Status: Der Build-Fehler ist ein bekanntes, systemisches Problem (fehlende SNK-Datei) und hat nichts mit dieser Änderung zu tun.
Sieht gut aus, danke! 👍
karlspace
left a comment
There was a problem hiding this comment.
📝 Korrektur zum CI-Hinweis
Mein vorheriger Hinweis zum Build-Fehler war ungenau — Entschuldigung!
Der Build-Fehler ist erwartetes Verhalten: Die SNK-Datei für Assembly-Signing wird über das Secret DOTNET_SIGNKEY_BASE64 bereitgestellt. GitHub stellt Dependabot-PRs aus Sicherheitsgründen keine Repository-Secrets zur Verfügung. Nach dem Merge auf main wird der Build erfolgreich durchlaufen.
Approval bleibt bestehen. ✅
|
🎉 This PR is included in version 3.0.3 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
Updated Sentry from 6.0.0 to 6.1.0.
Release notes
Sourced from Sentry's releases.
6.1.0
Features
SentryThreadbyMainto allow indication whether the thread is considered the current main thread (#4807)Fixes
EnvironmentandRelease(#4883)Dependencies
6.1.0-alpha.2
BREAKING CHANGES
AddCountertoEmitCounterRecordDistributiontoEmitDistributionRecordGaugetoEmitGaugeFeatures
Fixes
SetBeforeSendLogcallback (#4834)decimal) for Trace-connected Metrics (#4834)6.1.0-alpha.1
Features
SentryThreadbyMainto allow indication whether the thread is considered the current main thread (#4807)Dependencies
Commits viewable in compare view.
Updated Sentry.NLog from 6.0.0 to 6.1.0.
Release notes
Sourced from Sentry.NLog's releases.
6.1.0
Features
SentryThreadbyMainto allow indication whether the thread is considered the current main thread (#4807)Fixes
EnvironmentandRelease(#4883)Dependencies
6.1.0-alpha.2
BREAKING CHANGES
AddCountertoEmitCounterRecordDistributiontoEmitDistributionRecordGaugetoEmitGaugeFeatures
Fixes
SetBeforeSendLogcallback (#4834)decimal) for Trace-connected Metrics (#4834)6.1.0-alpha.1
Features
SentryThreadbyMainto allow indication whether the thread is considered the current main thread (#4807)Dependencies
Commits viewable in compare view.
You can trigger a rebase of this PR by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill 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 versionwill 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 dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)