Skip to content

Bump Sentry.Serilog from 6.13.0 to 7.0.1 - #2610

Closed
dependabot[bot] wants to merge 1 commit into
devfrom
dependabot/nuget/Sentry.Serilog-7.0.1
Closed

dependabot[bot] wants to merge 1 commit into
devfrom
dependabot/nuget/Sentry.Serilog-7.0.1

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Nov 17, 2026 •

Copy link
Copy Markdown
Contributor

Updated Sentry.Serilog from 6.13.0 to 7.0.1.

Release notes

Sourced from Sentry.Serilog's releases.

7.0.1

Fixes 🐛

  • fix: keep the longer rate limit when a later response sends a shorter one by @​ric-oliv with @​sentry-junior in #​5946
  • fix: Keep the transaction when TransactionNameProvider throws by @​dingsdax with @​sentry-junior in #​5941
  • fix: SentryOptions subclasses can set ScopeObserver and EnableScopeSync again by @​jamescrosswell and @​claude in #​5930
  • fix: Filter sensitive cookie values instead of sending raw cookies by @​jamescrosswell and @​claude in #​5894
  • Values of sensitive URL query parameters, such as token or session_id, are now replaced with [Filtered] in events, spans and breadcrumbs, regardless of SendDefaultPii. Outbound HTTP and GraphQL span descriptions no longer include the query string or fragment. by @​jamescrosswell and @​claude in #​5891

Dependencies ⬆️

Deps

  • chore(deps): update Cocoa SDK to v9.34.0 by @​ric-oliv and @​claude with @​github-actions in #​5924
  • chore(deps): update Java SDK to v8.64.0 by @​ric-oliv and @​claude with @​github-actions in #​5923

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

  • .NET 11. The SDK targets net11.0 alongside .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.
  • One place to initialize Sentry. The Microsoft.Extensions.Logging, Serilog, NLog and log4net integrations now only capture logs, breadcrumbs and events; they no longer start the SDK. Initialize Sentry with SentrySdk.Init or UseSentry, and configure it from the Sentry section of appsettings.json.
  • UseSentry for generic host apps. The new Sentry.Extensions.Hosting package adds UseSentry to Host.CreateApplicationBuilder and IHostBuilder, for worker services, console apps, Azure Functions (isolated) and Windows services.
  • Less noise in tracing. Requests that end in 301, 305–399 or 401–404 are no longer traced by default.
  • The right environment everywhere. ASP.NET Core, generic host apps, Blazor WebAssembly and Google Cloud Functions take the Sentry environment from the host environment, and logs, metrics, sessions and check-ins use an environment set on the scope.

Upgrading from 6.x

Target frameworks

  • MAUI and Mobile targets require .NET 10 or later: net9.0-android, net9.0-ios, net9.0-maccatalyst and net9.0-windows are no longer supported.
  • On .NET 11, the minimum Android API level is 24 (Android 7.0) and the minimum Mac Catalyst version is 17.0.
  • On .NET 11, the iOS and Mac Catalyst targets are net11.0-ios27.2 and net11.0-maccatalyst27.2, which need Xcode 27.2 to build.
  • Other targets are unchanged: .NET 8 and later, .NET Standard 2.0 and 2.1, and .NET Framework 4.6.2.

Initializing Sentry

  • Serilog's WriteTo.Sentry(...), NLog's Sentry target, log4net's SentryAppender and Logging.AddSentry(...) no longer initialize the SDK. Initialize Sentry first with SentrySdk.Init, or UseSentry in ASP.NET Core, MAUI, Blazor WebAssembly and generic host apps, and move Dsn, Release, Environment and 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).
  • In ASP.NET Core and generic host apps, UseSentry starts 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 call SentrySdk.Init at the start of Main.
  • Logging:Sentry in appsettings.json now only sets log levels: MinimumEventLevel, MinimumBreadcrumbLevel and the LogLevel rules. Move any other key to the Sentry section; the app fails at startup until you do.
  • SentryLoggingOptions, SentrySerilogOptions and SentryNLogOptions no longer derive from SentryOptions. Serilog's ApplySerilogScopeToEvents() is renamed UseSerilog().
  • NLog flushes Sentry using SentryOptions.FlushTimeout, which defaults to 2 seconds. The NLog target used to wait up to 15.
  • NLog sends entries at Info and above as logs. To send Trace and Debug entries as logs too, lower MinimumLogLevel on SentryNLogOptions, or minimumLogLevel on the target in XML config. enableLogs="false" still turns logs off, by setting MinimumLogLevel to Off.
  • Logging.AddSentry() no longer registers IHub, ISentryClient or Func<IHub> in the service collection; UseSentry does. An app that initializes Sentry with SentrySdk.Init and injects them now fails when they're resolved. Switch to UseSentry, or register HubAdapter.Instance for each type yourself.
  • In an app that calls both UseSentry and Logging.AddSentry(), the Logging.AddSentry() call now does nothing. Move its settings to the host's options, such as SentryAspNetCoreOptions, and remove the call. The exception is an app that calls ClearProviders() after UseSentry. Keep Logging.AddSentry() there, because it adds Sentry's logger providers back.
  • In MAUI, options set in the UseSentry callback now override appsettings.json, as they do in ASP.NET Core.

Removed and changed APIs

  • SentryOptions.EnableLogs is removed. With SentrySdk.Init and the logging integrations, logs are always sent; drop them with SetBeforeSendLog(_ => null). ASP.NET Core, MAUI and Blazor WebAssembly keep the opt-in: set EnableLogs on their options or in the Sentry section, as in 6.x.
  • SentryOptions.EnableMetrics is removed. Return null from SetBeforeSendMetric to drop metrics.
  • Scope.Release, Scope.Distribution and SentryOptions.ApplyDefaultTags are removed. Set Release and Distribution on SentryOptions. DefaultTags are still applied.
  • SentryOptions.ScopeObserver, EnableScopeSync and CrashedLastRun are now internal.
  • On iOS and Mac Catalyst, SentryOptions.Native.EnableAppHangTrackingV2 is removed; use EnableAppHangTracking. SentryOptions.Native.AddInAppExclude(string), which had no effect, is removed too.
  • Envelope.FromEvent, Envelope.FromFeedback and Envelope.FromTransaction take the IDiagnosticLogger as their last parameter.
  • The OTLP exporter no longer sets a global OpenTelemetry propagator, and its defaultTextMapPropagator parameter is removed. The propagator should be configured via the OpenTelemetry SDK instead.
  • SentryClientExtensions.GetInternalSentryOptions is removed. Integrations that need the SDK's diagnostic logger can call the new GetDiagnosticLogger() extension on IHub, in Sentry.Extensibility.
  • ILoggerFactory.AddSentry() is removed, and calls to it no longer compile. Use ILoggingBuilder.AddSentry() instead, for example LoggerFactory.Create(builder => builder.AddSentry()). Unlike the old method, it also sends ILogger entries as Sentry logs.

Changes in behavior

  • Requests that end in 301, 305–399 or 401–404 are no longer traced. To trace them again, call options.TraceIgnoreStatusCodes.Clear().
  • Apps that use the ISentryBuilder overloads of UseSentry (including gRPC apps), Blazor WebAssembly or Google Cloud Functions, and don't set an environment, now report the host environment, such as development or staging, instead of production. Update alerts and filters that rely on the old value.
  • Events, transactions, logs and metrics report the SDK name of the integration that initialized Sentry, such as sentry.dotnet.aspnetcore, rather than the logging integration that captured them.
  • On Android and iOS, SENTRY_RELEASE takes precedence over the release derived from the app package.
  • SentryOptions.DecompressionMethods now defaults to GZip | Deflate, leaving out Brotli. To accept Brotli responses again, set options.DecompressionMethods |= DecompressionMethods.Brotli.
    ... (truncated)

7.0.0-rc.3

Breaking Changes 🛠

  • Exclude Brotli from default SentryOptions.DecompressionMethods by @​jamescrosswell and @​claude in #​5816

Features ✨

Hangfire

  • feat(hangfire): Add an option to monitor all recurring jobs by @​wedamija and @​claude in #​5742
  • Hangfire recurring jobs marked with [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 with UseSentry(o => o.SendMonitorConfig = false). by @​wedamija and @​claude in #​5665

Other

  • feat(quartz): Add an option to monitor all scheduled jobs by @​wedamija, @​michaelmairegger and 3 others in #​5741
  • feat: add support for .NET 11 RC 3 by @​ric-oliv, @​claude and @​jamescrosswell in #​5830
  • Add 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 #​5668
    • Register it with services.AddQuartz(q => q.AddJobListener<SentryJobListener>()) or scheduler.ListenerManager.AddJobListener(new SentryJobListener())
    • Jobs marked with [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 automatically
    • Quartz.NET 3.x has no job middleware, so unlike Sentry.Quartz this doesn't run each job in its own scope or capture the exceptions jobs throw
  • Add Sentry.Quartz, an integration for Quartz.NET 4.x by @​michaelmairegger, @​jamescrosswell and 3 others in #​5505
    • services.AddQuartz(q => q.AddSentry()) runs each job in its own scope and trace, tagged with its job key, and captures the exceptions jobs throw
    • Jobs marked with [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 automatically
    • SentryQuartzOptions.ConfigureMonitorOptions customizes thresholds or the schedule, and SendMonitorConfig = false sends check-ins without a schedule

Fixes 🐛

Logging

  • fix(logging): warn when ClearProviders() removes the logger providers UseSentry added by @​ric-oliv and @​claude in #​5789
  • fix(logging): make Logging.AddSentry() work after UseSentry and ClearProviders() by @​ric-oliv and @​claude in #​5776

Other

  • fix(hosting): start the SDK during Build() even when the app clears or replaces logger providers by @​ric-oliv and @​claude in #​5772
  • fix(maui): report in_foreground for apps using the UIScene lifecycle by @​jamescrosswell and @​claude in #​5730
  • fix(nlog): stack overflow when Debug is on and NLog handles ILogger by @​jamescrosswell and @​claude in #​5823
  • fix: drop attachments whose stream turns out empty when the envelope is sent by @​bitsandfoxes in #​5787
  • fix: upload symbols and create releases when publishing Native AOT with the .NET 11 SDK by @​jamescrosswell and @​claude in #​5731
  • fix: don't upload pre-trim PDBs for trimmed iOS and Mac Catalyst builds by @​jamescrosswell and @​claude in #​5732
  • fix: avoid first-chance exception when getting length of non-seekable attachment streams by @​bitsandfoxes in #​5736

Dependencies ⬆️

Deps

  • chore(deps): update Native SDK to v0.17.5 by @​github-actions in #​5826
  • chore(deps): update Java SDK to v8.62.0 by @​github-actions in #​5824
  • chore(deps): update Java SDK to v8.61.1 by @​github-actions in #​5777
  • chore(deps): update CLI to v3.8.2 by @​github-actions in #​5778
  • chore(deps): update Cocoa SDK to v9.31.0 by @​ric-oliv and @​claude with @​github-actions in #​5769
    ... (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.

This is a release candidate, built against .NET 11 RC 2.

Highlights

  • .NET 11. The SDK targets net11.0 alongside .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.
  • One place to initialize Sentry. The Microsoft.Extensions.Logging, Serilog, NLog and log4net integrations now only capture logs, breadcrumbs and events; they no longer start the SDK. Initialize Sentry with SentrySdk.Init or UseSentry, and configure it from the Sentry section of appsettings.json.
  • UseSentry for generic host apps. The new Sentry.Extensions.Hosting package adds UseSentry to Host.CreateApplicationBuilder and IHostBuilder, for worker services, console apps, Azure Functions (isolated) and Windows services. ASP.NET Core apps can call builder.UseSentry(...) on WebApplicationBuilder and keep chaining.
  • Cron monitors from code. SentrySdk.WithMonitor and SentrySdk.WithMonitorAsync run 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.
  • Less noise in tracing. Requests that end in 301, 305–399 or 401–404 are no longer traced by default.
  • The right environment everywhere. ASP.NET Core, generic host apps, Blazor WebAssembly and Google Cloud Functions take the Sentry environment from the host environment, and logs, metrics, sessions and check-ins use an environment set on the scope.

Upgrading from 6.x

Target frameworks

  • Mobile targets require .NET 10 or later: net9.0-android, net9.0-ios, net9.0-maccatalyst and net9.0-windows are no longer supported.
  • On .NET 11, the minimum Android API level is 24 (Android 7.0) and the minimum Mac Catalyst version is 17.0.
  • Other targets are unchanged: .NET 8 and later, .NET Standard 2.0 and 2.1, and .NET Framework 4.6.2.

Initializing Sentry

  • Serilog's WriteTo.Sentry(...), NLog's Sentry target, log4net's SentryAppender and Logging.AddSentry(...) no longer initialize the SDK. Initialize Sentry first with SentrySdk.Init, or UseSentry in ASP.NET Core, MAUI, Blazor WebAssembly and generic host apps, and move Dsn, Release, Environment and 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:Sentry in appsettings.json now only sets log levels: MinimumEventLevel, MinimumBreadcrumbLevel and the LogLevel rules. Move any other key to the Sentry section; the app fails at startup until you do.
  • SentryLoggingOptions, SentrySerilogOptions and SentryNLogOptions no longer derive from SentryOptions. Serilog's ApplySerilogScopeToEvents() is renamed UseSerilog().
  • NLog flushes Sentry using SentryOptions.FlushTimeout, which defaults to 2 seconds. The NLog target used to wait up to 15.
  • Logging.AddSentry() no longer registers IHub, ISentryClient or Func<IHub> in the service collection; UseSentry does. An app that initializes Sentry with SentrySdk.Init and injects them now fails when they're resolved. Switch to UseSentry, or register HubAdapter.Instance for each type yourself.
  • In an app that calls both UseSentry and Logging.AddSentry(), the Logging.AddSentry() call now does nothing. Move its settings to the host's options, such as SentryAspNetCoreOptions, and remove the call.
  • In MAUI, options set in the UseSentry callback now override appsettings.json, as they do in ASP.NET Core.

Removed and changed APIs

  • SentryOptions.EnableLogs is removed. With SentrySdk.Init and the logging integrations, logs are always sent; drop them with SetBeforeSendLog(_ => null). ASP.NET Core, MAUI and Blazor WebAssembly keep the opt-in: set EnableLogs on their options or in the Sentry section, as in 6.x.
  • SentryOptions.EnableMetrics is removed. Return null from SetBeforeSendMetric to drop metrics.
  • Scope.Release, Scope.Distribution and SentryOptions.ApplyDefaultTags are removed. Set Release and Distribution on SentryOptions. DefaultTags are still applied.
  • SentryOptions.ScopeObserver, EnableScopeSync and CrashedLastRun are now internal.
  • On iOS and Mac Catalyst, SentryOptions.Native.EnableAppHangTrackingV2 is removed; use EnableAppHangTracking. SentryOptions.Native.AddInAppExclude(string), which had no effect, is removed too.
  • Envelope.FromEvent, Envelope.FromFeedback and Envelope.FromTransaction take the IDiagnosticLogger as their last parameter.
  • The OTLP exporter no longer sets a global OpenTelemetry propagator, and its defaultTextMapPropagator parameter is removed. The propagator should be configured via the OpenTelemetry SDK instead. Sentry.OpenTelemetry and Sentry.OpenTelemetry.Exporter now require OpenTelemetry 1.12.0 or later.

Changes in behavior

  • Requests that end in 301, 305–399 or 401–404 are no longer traced. To trace them again, call options.TraceIgnoreStatusCodes.Clear().
  • Apps that use the ISentryBuilder overloads of UseSentry (including gRPC apps), Blazor WebAssembly or Google Cloud Functions, and don't set an environment, now report the host environment, such as development or staging, instead of production. Update alerts and filters that rely on the old value.
  • Events, transactions, logs and metrics report the SDK name of the integration that initialized Sentry, such as sentry.dotnet.aspnetcore, rather than the logging integration that captured them.
  • On Android and iOS, SENTRY_RELEASE takes precedence over the release derived from the app package.
  • Hangfire recurring jobs marked with [SentryMonitorSlug] send their schedule and time zone, which updates existing monitors on the next run. To keep managing schedules in Sentry, opt out with UseSentry(o => o.SendMonitorConfig = false).

Breaking Changes 🛠

... (truncated)

Commits viewable in compare view.

Dependabot compatibility score

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 rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @dependabot ignore this major version will 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 version will 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 dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

---
updated-dependencies:
- dependency-name: Sentry.Serilog
  dependency-version: 7.0.1
  dependency-type: direct:production
  update-type: version-update:semver-major
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot Bot added dependencies Represent PR about updating deps of the project ship it! Auto merge the PR labels Nov 17, 2026
@kody-ai

kody-ai Bot commented Nov 17, 2026 •

Copy link
Copy Markdown

Code Review Could Not Complete ⚠️

The review failed before suggestions could be generated.

Reason: The configured API key (open_router) is out of credits or has hit its billing limit. Top up the account or adjust the plan.

open_router · ~deepseek/deepseek-flash-latest · HTTP 402 · generalist

Provider said: Insufficient credits. Add more using https://openrouter.ai/settings/credits

After fixing the issue, comment @kody review on this PR to re-run the review.

Kody Guide: Usage and Configuration
Interacting with Kody
  • Request a Review: Ask Kody to review your PR manually by adding a comment with the @kody start-review command at the root of your PR.

  • Validate Business Logic: Ask Kody to validate your code against business rules by adding a comment with the @kody -v business-logic command.

  • Provide Feedback: Help Kody learn and improve by reacting to its comments with a 👍 for helpful suggestions or a 👎 if improvements are needed.

Current Kody Configuration
Review Options

The following review options are enabled or disabled:

Options Enabled
Bug ✅
Performance ✅
Security ✅
Business Logic ✅

Access your configuration settings here.

​

@coderabbitai

coderabbitai Bot commented Nov 17, 2026

Copy link
Copy Markdown
Contributor

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

Run configuration

  • Source mode: Auto
  • Repository: Unavailable
  • Branch: Unavailable
  • File: No configuration file from this repository applied
  • Commit: Unavailable
  • Layers: Organization UI
  • Review profile: CHILL
  • Plan: Advanced
  • Run ID: 20beb0b9-5d64-4baf-ac19-9a1504baa36a

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

  • Trigger review
  • Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

Share

@dependabot @github

dependabot Bot commented on behalf of github Nov 19, 2026

Copy link
Copy Markdown
Contributor Author

Looks like Sentry.Serilog is no longer updatable, so this is no longer needed.

@dependabot dependabot Bot closed this Nov 19, 2026
@dependabot
dependabot Bot deleted the dependabot/nuget/Sentry.Serilog-7.0.1 branch November 19, 2026 04:19
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Represent PR about updating deps of the project ship it! Auto merge the PR

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants