Repository navigation
Bump Sentry from 5.16.3 to 7.0.0 - #92
Closed
dependabot[bot] wants to merge 1 commit into
Closed
dependabot[bot] wants to merge 1 commit into
dependabot[bot] wants to merge 1 commit into
Conversation
--- updated-dependencies: - dependency-name: Sentry dependency-version: 7.0.0 dependency-type: direct:production update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com>
Contributor
Author
|
Superseded by #94. |
dependabot
Bot
deleted the
dependabot/nuget/src/Gml.Client/Sentry-7.0.0
branch
November 17, 2026 17:59
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Updated Sentry from 5.16.3 to 7.0.0.
Release notes
Sourced from Sentry's releases.
7.0.0
Version 7 of the Sentry SDK for .NET adds support for .NET 11 and gives Sentry a single place to be initialized. It contains breaking changes, so read the upgrade notes below before you upgrade.
Highlights
net11.0alongside .NET 8, 9 and 10, including Android, iOS and Mac Catalyst apps on .NET 11, with support for .NET 11's Android assembly stores and Zstandard-compressed assemblies.Microsoft.Extensions.Logging, Serilog, NLog and log4net integrations now only capture logs, breadcrumbs and events; they no longer start the SDK. Initialize Sentry withSentrySdk.InitorUseSentry, and configure it from theSentrysection ofappsettings.json.UseSentryfor generic host apps. The newSentry.Extensions.Hostingpackage addsUseSentrytoHost.CreateApplicationBuilderandIHostBuilder, for worker services, console apps, Azure Functions (isolated) and Windows services.Upgrading from 6.x
Target frameworks
net9.0-android,net9.0-ios,net9.0-maccatalystandnet9.0-windowsare no longer supported.net11.0-ios27.2andnet11.0-maccatalyst27.2, which need Xcode 27.2 to build.Initializing Sentry
WriteTo.Sentry(...), NLog's Sentry target, log4net'sSentryAppenderandLogging.AddSentry(...)no longer initialize the SDK. Initialize Sentry first withSentrySdk.Init, orUseSentryin ASP.NET Core, MAUI, Blazor WebAssembly and generic host apps, and moveDsn,Release,Environmentand other SDK settings there. A DSN still set on one of these integrations fails with a message explaining what to change (to prevent SDK users being blind-sided by this change).UseSentrystarts Sentry when the host is built, so crashes before that aren't captured. Apps that relied on the Serilog sink, the NLog target or the log4net appender to capture startup crashes can also callSentrySdk.Initat the start ofMain.Logging:Sentryinappsettings.jsonnow only sets log levels:MinimumEventLevel,MinimumBreadcrumbLeveland theLogLevelrules. Move any other key to theSentrysection; the app fails at startup until you do.SentryLoggingOptions,SentrySerilogOptionsandSentryNLogOptionsno longer derive fromSentryOptions. Serilog'sApplySerilogScopeToEvents()is renamedUseSerilog().SentryOptions.FlushTimeout, which defaults to 2 seconds. The NLog target used to wait up to 15.Infoand above as logs. To sendTraceandDebugentries as logs too, lowerMinimumLogLevelonSentryNLogOptions, orminimumLogLevelon the target in XML config.enableLogs="false"still turns logs off, by settingMinimumLogLeveltoOff.Logging.AddSentry()no longer registersIHub,ISentryClientorFunc<IHub>in the service collection;UseSentrydoes. An app that initializes Sentry withSentrySdk.Initand injects them now fails when they're resolved. Switch toUseSentry, or registerHubAdapter.Instancefor each type yourself.UseSentryandLogging.AddSentry(), theLogging.AddSentry()call now does nothing. Move its settings to the host's options, such asSentryAspNetCoreOptions, and remove the call. The exception is an app that callsClearProviders()afterUseSentry. KeepLogging.AddSentry()there, because it adds Sentry's logger providers back.UseSentrycallback now overrideappsettings.json, as they do in ASP.NET Core.Removed and changed APIs
SentryOptions.EnableLogsis removed. WithSentrySdk.Initand the logging integrations, logs are always sent; drop them withSetBeforeSendLog(_ => null). ASP.NET Core, MAUI and Blazor WebAssembly keep the opt-in: setEnableLogson their options or in theSentrysection, as in 6.x.SentryOptions.EnableMetricsis removed. ReturnnullfromSetBeforeSendMetricto drop metrics.Scope.Release,Scope.DistributionandSentryOptions.ApplyDefaultTagsare removed. SetReleaseandDistributiononSentryOptions.DefaultTagsare still applied.SentryOptions.ScopeObserver,EnableScopeSyncandCrashedLastRunare now internal.SentryOptions.Native.EnableAppHangTrackingV2is removed; useEnableAppHangTracking.SentryOptions.Native.AddInAppExclude(string), which had no effect, is removed too.Envelope.FromEvent,Envelope.FromFeedbackandEnvelope.FromTransactiontake theIDiagnosticLoggeras their last parameter.defaultTextMapPropagatorparameter is removed. The propagator should be configured via the OpenTelemetry SDK instead.SentryClientExtensions.GetInternalSentryOptionsis removed. Integrations that need the SDK's diagnostic logger can call the newGetDiagnosticLogger()extension onIHub, inSentry.Extensibility.ILoggerFactory.AddSentry()is removed, and calls to it no longer compile. UseILoggingBuilder.AddSentry()instead, for exampleLoggerFactory.Create(builder => builder.AddSentry()). Unlike the old method, it also sendsILoggerentries as Sentry logs.Changes in behavior
options.TraceIgnoreStatusCodes.Clear().ISentryBuilderoverloads ofUseSentry(including gRPC apps), Blazor WebAssembly or Google Cloud Functions, and don't set an environment, now report the host environment, such asdevelopmentorstaging, instead ofproduction. Update alerts and filters that rely on the old value.sentry.dotnet.aspnetcore, rather than the logging integration that captured them.SENTRY_RELEASEtakes precedence over the release derived from the app package.SentryOptions.DecompressionMethodsnow defaults toGZip | Deflate, leaving out Brotli. To accept Brotli responses again, setoptions.DecompressionMethods |= DecompressionMethods.Brotli.... (truncated)
7.0.0-rc.3
Breaking Changes 🛠
Features ✨
Hangfire
[SentryMonitorSlug]now send their cron schedule and time zone with the check-in, so Sentry creates the monitor if it doesn't exist yet. This is on by default: on upgrade, existing monitors take their schedule and time zone from the recurring job on its next run (other monitor settings are kept). To keep managing schedules in Sentry, opt out withUseSentry(o => o.SendMonitorConfig = false). by @wedamija and @claude in #5665Other
Sentry.Quartz3, an integration for Quartz.NET 3.x (3.6 and later) on .NET Framework 4.6.2+ and .NET 8+ by @wedamija, @michaelmairegger and 3 others in #5668services.AddQuartz(q => q.AddJobListener<SentryJobListener>())orscheduler.ListenerManager.AddJobListener(new SentryJobListener())[SentryMonitorSlug]send a Sentry Crons check-in for every run, with the trigger's cron or interval schedule as the monitor config, so monitors are created and kept up to date automaticallySentry.Quartzthis doesn't run each job in its own scope or capture the exceptions jobs throwSentry.Quartz, an integration for Quartz.NET 4.x by @michaelmairegger, @jamescrosswell and 3 others in #5505services.AddQuartz(q => q.AddSentry())runs each job in its own scope and trace, tagged with its job key, and captures the exceptions jobs throw[SentryMonitorSlug]send a Sentry Crons check-in for every run, with the trigger's cron or interval schedule as the monitor config, so monitors are created and kept up to date automaticallySentryQuartzOptions.ConfigureMonitorOptionscustomizes thresholds or the schedule, andSendMonitorConfig = falsesends check-ins without a scheduleFixes 🐛
Logging
Other
Dependencies ⬆️
Deps
... (truncated)
7.0.0-rc.2
Version 7 of the Sentry SDK for .NET adds support for .NET 11 and gives Sentry a single place to be initialized. It contains breaking changes, so read the upgrade notes below before you upgrade.
Highlights
net11.0alongside .NET 8, 9 and 10, including Android, iOS and Mac Catalyst apps on .NET 11, with support for its new Android assembly store format and Zstandard-compressed assemblies.Microsoft.Extensions.Logging, Serilog, NLog and log4net integrations now only capture logs, breadcrumbs and events; they no longer start the SDK. Initialize Sentry withSentrySdk.InitorUseSentry, and configure it from theSentrysection ofappsettings.json.UseSentryfor generic host apps. The newSentry.Extensions.Hostingpackage addsUseSentrytoHost.CreateApplicationBuilderandIHostBuilder, for worker services, console apps, Azure Functions (isolated) and Windows services. ASP.NET Core apps can callbuilder.UseSentry(...)onWebApplicationBuilderand keep chaining.SentrySdk.WithMonitorandSentrySdk.WithMonitorAsyncrun a job, send its check-ins, and can create the monitor along with its schedule. Hangfire recurring jobs marked with[SentryMonitorSlug]send their cron schedule automatically.Upgrading from 6.x
Target frameworks
net9.0-android,net9.0-ios,net9.0-maccatalystandnet9.0-windowsare no longer supported.Initializing Sentry
WriteTo.Sentry(...), NLog's Sentry target, log4net'sSentryAppenderandLogging.AddSentry(...)no longer initialize the SDK. Initialize Sentry first withSentrySdk.Init, orUseSentryin ASP.NET Core, MAUI, Blazor WebAssembly and generic host apps, and moveDsn,Release,Environmentand other SDK settings there. A DSN still set on one of these integrations fails with a message explaining what to change (to prevent SDK users being blind-sided by this change).Logging:Sentryinappsettings.jsonnow only sets log levels:MinimumEventLevel,MinimumBreadcrumbLeveland theLogLevelrules. Move any other key to theSentrysection; the app fails at startup until you do.SentryLoggingOptions,SentrySerilogOptionsandSentryNLogOptionsno longer derive fromSentryOptions. Serilog'sApplySerilogScopeToEvents()is renamedUseSerilog().SentryOptions.FlushTimeout, which defaults to 2 seconds. The NLog target used to wait up to 15.Logging.AddSentry()no longer registersIHub,ISentryClientorFunc<IHub>in the service collection;UseSentrydoes. An app that initializes Sentry withSentrySdk.Initand injects them now fails when they're resolved. Switch toUseSentry, or registerHubAdapter.Instancefor each type yourself.UseSentryandLogging.AddSentry(), theLogging.AddSentry()call now does nothing. Move its settings to the host's options, such asSentryAspNetCoreOptions, and remove the call.UseSentrycallback now overrideappsettings.json, as they do in ASP.NET Core.Removed and changed APIs
SentryOptions.EnableLogsis removed. WithSentrySdk.Initand the logging integrations, logs are always sent; drop them withSetBeforeSendLog(_ => null). ASP.NET Core, MAUI and Blazor WebAssembly keep the opt-in: setEnableLogson their options or in theSentrysection, as in 6.x.SentryOptions.EnableMetricsis removed. ReturnnullfromSetBeforeSendMetricto drop metrics.Scope.Release,Scope.DistributionandSentryOptions.ApplyDefaultTagsare removed. SetReleaseandDistributiononSentryOptions.DefaultTagsare still applied.SentryOptions.ScopeObserver,EnableScopeSyncandCrashedLastRunare now internal.SentryOptions.Native.EnableAppHangTrackingV2is removed; useEnableAppHangTracking.SentryOptions.Native.AddInAppExclude(string), which had no effect, is removed too.Envelope.FromEvent,Envelope.FromFeedbackandEnvelope.FromTransactiontake theIDiagnosticLoggeras their last parameter.defaultTextMapPropagatorparameter is removed. The propagator should be configured via the OpenTelemetry SDK instead.Sentry.OpenTelemetryandSentry.OpenTelemetry.Exporternow require OpenTelemetry 1.12.0 or later.Changes in behavior
options.TraceIgnoreStatusCodes.Clear().ISentryBuilderoverloads ofUseSentry(including gRPC apps), Blazor WebAssembly or Google Cloud Functions, and don't set an environment, now report the host environment, such asdevelopmentorstaging, instead ofproduction. Update alerts and filters that rely on the old value.sentry.dotnet.aspnetcore, rather than the logging integration that captured them.SENTRY_RELEASEtakes precedence over the release derived from the app package.[SentryMonitorSlug]send their schedule and time zone, which updates existing monitors on the next run. To keep managing schedules in Sentry, opt out withUseSentry(o => o.SendMonitorConfig = false).Breaking Changes 🛠
... (truncated)
6.13.0
Features ✨
Hangfire
[SentryMonitorSlug]now send their cron schedule and time zone with the check-in, so Sentry creates the monitor if it doesn't exist yet. This is on by default: on upgrade, existing monitors take their schedule and time zone from the recurring job on its next run (other monitor settings are kept). To keep managing schedules in Sentry, opt out withUseSentry(o => o.SendMonitorConfig = false). by @wedamija and @claude in #5665Other
Sentry.Quartz3, an integration for Quartz.NET 3.x (3.6 and later) on .NET Framework 4.6.2+ and .NET 8+ by @wedamija, @michaelmairegger and 3 others in #5668services.AddQuartz(q => q.AddJobListener<SentryJobListener>())orscheduler.ListenerManager.AddJobListener(new SentryJobListener())[SentryMonitorSlug]send a Sentry Crons check-in for every run, with the trigger's cron or interval schedule as the monitor config, so monitors are created and kept up to date automaticallySentry.Quartzthis doesn't run each job in its own scope or capture the exceptions jobs throwSentry.Quartz, an integration for Quartz.NET 4.x by @michaelmairegger, @jamescrosswell and 3 others in #5505services.AddQuartz(q => q.AddSentry())runs each job in its own scope and trace, tagged with its job key, and captures the exceptions jobs throw[SentryMonitorSlug]send a Sentry Crons check-in for every run, with the trigger's cron or interval schedule as the monitor config, so monitors are created and kept up to date automaticallySentryQuartzOptions.ConfigureMonitorOptionscustomizes thresholds or the schedule, andSendMonitorConfig = falsesends check-ins without a scheduleFixes 🐛
Maui
Other
Set-Cookie,X-Api-KeyandX-Auth-Token, now have their values replaced with[Filtered], regardless ofSendDefaultPiiby @jamescrosswell and @claude in #5890AutoSessionTrackingIntervalends the session, and an app killed in the background reportsexitedinstead ofabnormal. by @bitsandfoxes, @claude and @jamescrosswell in #5863backpressuredrops in client reports by @chiliec in #5841Dependencies ⬆️
Deps
... (truncated)
6.12.1
Fixes 🐛
Dependencies ⬆️
Deps
Other
6.12.0
Features ✨
Fixes 🐛
Dependencies ⬆️
Deps
Other
6.11.1
Fixes 🐛
[NSURLSessionTask cancel]when a request is cancelled after it has already completed withNative.EnableSwizzlingenabled (Cocoa SDK v9.29.0). Note that native crashes now setmechanism.synthetic, so expect a one-time regrouping of existing crash issues as your app adopts this version. by @github-actions in #5596Dependencies ⬆️
Deps
Other
6.11.0
Features ✨
Fixes 🐛
Dependencies ⬆️
Deps
6.10.0
Features ✨
SentrySdk.Loggerno longer requireEnableLogsby @jamescrosswell in #5512SentryOptions.EnableMetricsis obsolete and ignored by @jamescrosswell in #5509Fixes 🐛
Dependencies ⬆️
Deps
Other
6.9.0
Features ✨
Fixes 🐛
Dependencies ⬆️
Deps
Other
6.8.0
Features ✨
Logs
log4netintegration by @Flash0ver in #5172NLogintegration by @Flash0ver in #5176Other
AddToTransactionsonSentryAttachment#5182 by @jamescrosswell in #5182SentrySdk.RecordTransactionto record already-completed transactions and spans (e.g. replayed through a proxy) #5333 by @jamescrosswell in #5333Environmentset on theScopenow gets synchronized to the native layers (sentry-cocoaandsentry-native) by @bitsandfoxes in #5365Fixes 🐛
SentrySpanProcessorno longer leaks spans whose Activity never ends (e.g. aborted requests); the Activity is now held via aWeakReferenceso orphaned spans are pruned once it is garbage-collected. by @Ermabo in #5393Dependencies ⬆️
Deps
Other
6.7.0
Features ✨
IgnoreTransactionsoption to filter out transactions by name, matching substrings or regular expressions against the transaction name (#5377) by @Adham-Kiwan in #5377SentryEventExtensions.IsFromUnhandledException) and terminal exceptions (SentryEventExtensions.IsFromTerminalException) by @jamescrosswell in #5177Fixes 🐛
Dependencies ⬆️
Deps
Other
Sentry.Extensions.LoggingFilters by @Flash0ver in #52976.6.0
Features ✨
sentry-androidandsentry-cocoaby @bitsandfoxes in #5244Fixes 🐛
Dependencies ⬆️
Deps
Other
6.5.0
Features ✨
Fixes 🐛
SentryEventto haveIsCapturedto allow dropping screenshots of filtered events by @JoshuaMoelans in #5162PruneFilteredSpansruns by @jamescrosswell in #5186Dependencies ⬆️
Deps
Other
6.4.1
Fixes 🐛
Dependencies ⬆️
Deps
6.4.0
Features ✨
Fixes 🐛
options.Native.ExperimentalOptions.SignalHandlerStrategytoSentry.Android.SignalHandlerStrategy.ChainAtStartDependencies ⬆️
Deps
6.3.2
Dependencies ⬆️
6.3.1
Fixes 🐛
CaptureFeedbacknow supports multiple attachments correctly by @bitsandfoxes in #5077Dependencies ⬆️
Deps
Other
6.3.0
Features
ExperimentalfromSentrySdk,SentryOptionsandIHub(#5023)SENTRY1001) when a Metrics-API is invoked with an unsupported numeric type (#4840)Fixes
EnvironmentandReleaseand custom event processors are all now correctly applied to CaptureFeedback events (#4942)Dataset viaITransactionTracerinSentryTransaction(#4148)Dependencies
6.2.0
Features
Fixes
Warninginstead of anErrorwhen being ratelimited (#4927)libmonosgenandlibxamarinframes no longer show as in-app (#4960)Dependencies
SentryApiKey, you need to generate an Auth Token and useSentryAuthToken, instead.6.2.0-alpha.0
Features
Dependencies
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
6.0.0
BREAKING CHANGES
SentryLoggingOptions.ExperimentalLogging.MinimumLogLevel. Structured Logs can now be configured via the"Sentry"logging provider (e.g. inappsettings.jsonandappsettings.{HostEnvironment}.json) (#4700)SentryLog.ParentSpanIdtoSentryLog.SpanIdreflecting the protocol change (#4778)IDisposableso that they can be used withusingstatements/declarations that will automatically finish the span with a status of OK when it passes out of scope, if it has not already been finished, to be consistent withActivityclasses when using OpenTelemetry (#4627)sealed(see also #4627)ExperimentalfromSentryOptions(#4699)SentryIdand aCaptureFeedbackResultout parameter that indicate whether feedback was captured successfully and what the reason for failure was otherwise (#4613)Sentry.Azure.Functions.Workeras very few people were using it and the functionality can easily be replaced with OpenTelemetry. We've replaced our integration with a sample showing how to do this using our OpenTelemetry package instead. (#4693)BreadcrumbLevel.Criticalhas been renamed toBreadcrumbLevel.Fatalfor consistency with the other Sentry SDKs (#4605)Sentry.Maui.BreadcrumbEventthat had been marked as obsolete. That constructor expected aIEnumerable<(string Key, string Value)>[]argument (i.e. an array of IEnumerable of tuples). If you were using this constructor, you should instead use the alternate constructor that expects just an IEnumerable of tuples:IEnumerable<(string Key, string Value)>.SentrySdk.CaptureUserFeedbackand all associated members. Use the newerSentrySdk.CaptureFeedbackinstead.Features
Sentry.Extensions.AIwhich allows LLM usage instrumentation viaMicrosoft.Extensions.AI(#4657)Sentry.Google.Cloud.Functions(#4700)IsSessionActiveto allow checking the session state (#4662)Unhandledwhen capturing an unhandled but non-terminal exception, i.e. through the UnobservedTaskExceptionIntegration (#4633, #4653)app_memorythat can hold the amount of memory used by the application in bytes. (#4707)PropagateTraceparent = truewhen initializing the SDK if to include the W3C traceparent header on outgoing requests.Fixes
Serilogintegration captures Structured Logs (when enabled) independently of captured Events and added Breadcrumbs (#4691)Sentry.Extensions.Logging,Sentry.AspNetCore,Sentry.MauiandSentry.Google.Cloud.Functionsappsettings.json)SentryLoggingOptions.MinimumBreadcrumbLevel, `SentryLoggingOptions.Minimum..._Description...
Description has been truncated