Repository navigation
Bump the nuget group with 3 updates - #275
Open
dependabot[bot] wants to merge 1 commit into
Open
dependabot[bot] wants to merge 1 commit into
dependabot[bot] wants to merge 1 commit into
Conversation
Bumps coverlet.collector from 10.1.0 to 10.1.1 Bumps Microsoft.CodeAnalysis.CSharp from 5.9.0 to 5.12.0 Bumps Sentry from 6.12.1 to 7.0.1 --- updated-dependencies: - dependency-name: Sentry dependency-version: 7.0.1 dependency-type: direct:production update-type: version-update:semver-major dependency-group: nuget - dependency-name: coverlet.collector dependency-version: 10.1.1 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: nuget - dependency-name: Microsoft.CodeAnalysis.CSharp dependency-version: 5.12.0 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: nuget - dependency-name: Sentry dependency-version: 7.0.1 dependency-type: direct:production update-type: version-update:semver-major dependency-group: nuget - dependency-name: coverlet.collector dependency-version: 10.1.1 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: nuget - dependency-name: Microsoft.CodeAnalysis.CSharp dependency-version: 5.12.0 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: nuget - dependency-name: coverlet.collector dependency-version: 10.1.1 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: nuget - dependency-name: coverlet.collector dependency-version: 10.1.1 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: nuget - dependency-name: coverlet.collector dependency-version: 10.1.1 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: nuget - dependency-name: Microsoft.CodeAnalysis.CSharp dependency-version: 5.12.0 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: nuget - dependency-name: coverlet.collector dependency-version: 10.1.1 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: nuget - dependency-name: coverlet.collector dependency-version: 10.1.1 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: nuget ... Signed-off-by: dependabot[bot] <support@github.com>
Contributor
|
Important Review skippedBot user detected. To trigger a single review, invoke the
|
This branch has not been deployed
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 coverlet.collector from 10.1.0 to 10.1.1.
Release notes
Sourced from coverlet.collector's releases.
10.1.1
Improvements
IsReachableto branch points, computed from the method's control-flow graph, and exclude unreachable branches from branch-coverage totals and from branch details in Cobertura, LCOV and OpenCover reports #2056 by @pcshrosbreeFixed
Maintenance
Diff between 10.1.0 and 10.1.1
Commits viewable in compare view.
Updated Microsoft.CodeAnalysis.CSharp from 5.9.0 to 5.12.0.
Release notes
Sourced from Microsoft.CodeAnalysis.CSharp's releases.
No release notes found for this version range.
Commits viewable in compare view.
Updated Sentry from 6.12.1 to 7.0.1.
Release notes
Sourced from Sentry's releases.
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.... (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)
Commits viewable in compare view.
Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually 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 <dependency name> major versionwill close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)@dependabot ignore <dependency name> minor versionwill close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)@dependabot ignore <dependency name>will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)@dependabot unignore <dependency name>will remove all of the ignore conditions of the specified dependency@dependabot unignore <dependency name> <ignore condition>will remove the ignore condition of the specified dependency and ignore conditions