Repository navigation
chore(deps): update Dotnet SDK to v7.0.1 - #148
Open
github-actions[bot] wants to merge 1 commit into
Open
github-actions[bot] wants to merge 1 commit into
github-actions[bot] wants to merge 1 commit into
Conversation
bruno-garcia
force-pushed
the
deps/dependencies/Sentry.properties
branch
from
September 12, 2026 03:02
9784a1b to
7dba7cf
Compare
bruno-garcia
force-pushed
the
deps/dependencies/Sentry.properties
branch
from
September 22, 2026 03:02
7dba7cf to
fcbd30d
Compare
bruno-garcia
force-pushed
the
deps/dependencies/Sentry.properties
branch
from
October 2, 2026 03:02
fcbd30d to
b8dcf0b
Compare
bruno-garcia
force-pushed
the
deps/dependencies/Sentry.properties
branch
from
October 14, 2026 03:01
b8dcf0b to
5c4149d
Compare
bruno-garcia
force-pushed
the
deps/dependencies/Sentry.properties
branch
from
November 12, 2026 03:01
5c4149d to
67912af
Compare
bruno-garcia
force-pushed
the
deps/dependencies/Sentry.properties
branch
from
November 13, 2026 03:01
67912af to
0f11cc8
Compare
bruno-garcia
force-pushed
the
deps/dependencies/Sentry.properties
branch
from
November 18, 2026 03:01
0f11cc8 to
1ab9732
Compare
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes and found 1 potential issue.
❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.
Reviewed by Cursor Bugbot for commit 1ab9732. Configure here.
| @@ -1,3 +1,3 @@ | |||
| version = 6.10.0 | |||
| version = 7.0.1 | |||
There was a problem hiding this comment.
EnableLogs assignment fails after bump
High Severity
The bump to sentry-dotnet 7.0.1 removes SentryOptions.EnableLogs. Start-Sentry configs that assign it, including write-sentrylog.tests.ps1, throw because that property no longer exists on the options object, so Sentry never starts and log tests fail.
Reviewed by Cursor Bugbot for commit 1ab9732. Configure here.
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.


Bumps dependencies/Sentry.properties from 6.10.0 to 7.0.1.
Auto-generated by a dependency updater.
Changelog
7.0.1
Fixes 🐛
TransactionNameProviderthrows by dingsdax with sentry-junior in #5941tokenorsession_id, are now replaced with[Filtered]in events, spans and breadcrumbs, regardless ofSendDefaultPii. Outbound HTTP and GraphQL span descriptions no longer include the query string or fragment. by jamescrosswell and claude in #5891Dependencies ⬆️
Deps
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.LogContextto events as tags, even when the app doesn't callUseSerilog(). In 6.x this only happened when the sink initialized the SDK or the app calledApplySerilogScopeToEvents().Breaking Changes 🛠
GetInternalSentryOptions, which was only meant for Sentry's own integrations. Integrations that need the SDK's diagnostic logger can call the newGetDiagnosticLogger()extension onIHub, inSentry.Extensibility. by jamescrosswell in #5862builder.Logging.AddSentry()no longer registersIHub,ISentryClientorFunc<IHub>in the service collection.UseSentryregisters them; apps that initialize Sentry withSentrySdk.Initand inject them now register them themselves by jamescrosswell in #5740Microsoft.Extensions.Loggingintegration no longer initializes the SDK. Sentry must now be initialized separately from the logging integration (usingSentrySdk.InitorUseSentry) by jamescrosswell in #5595Logging:Sentry) now only configures the logging integration. Core SDK settings there, such asDsn, no longer have any effect and fail at startup with migration guidance: move them to theSentrysection, or pass them where Sentry is initialized by jamescrosswell in #5595Scope.ReleaseandScope.Distributionhave been removed, andReleaseandDistributionhave moved fromIEventLiketoITransactionData. Set them onSentryOptionsinstead. by jamescrosswell in #5671SentryOptions.ApplyDefaultTagshas been removed. Default tags set inSentryOptions.DefaultTagsare still applied to events and transactions. by jamescrosswell in #5671Scope.Environmenttonullclears the override. by jamescrosswell in #5671sentry.dotnet.aspnetcore. Blazor WebAssembly now reportssentry.dotnet.aspnetcore.blazor.webassembly. by jamescrosswell in #5671SENTRY_RELEASEnow takes precedence over the default release derived from the app package. by jamescrosswell in #5671Envelope.FromEvent,Envelope.FromFeedbackandEnvelope.FromTransactionnow take theIDiagnosticLoggeras their last parameter, afterattachments(andsessionUpdate). This only affects code that creates envelopes directly and passes these arguments positionally; those calls no longer compile, so reorder the arguments or pass them by name. by jamescrosswell in #5669SentryOptions.Native.EnableAppHangTrackingV2on iOS and Mac Catalyst (useEnableAppHangTrackinginstead) by jamescrosswell in #5654SentryOptions.Native.AddInAppExclude(string)on iOS, which had no effect by jamescrosswell in #5654SentryOptions.ScopeObserver,EnableScopeSyncandCrashedLastRunare now internal by jamescrosswell in #5631Features ✨
net9.0-android,net9.0-ios,net9.0-maccatalystandnet9.0-windowshave been dropped. by jamescrosswell in #5529Fixes 🐛
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
Other
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