Skip to content

feat(serilog): support restrictedToMinimumLevel when configuring Serilog in code - #5181

Merged
jamescrosswell merged 5 commits into
mainfrom
feat/serilog-restricted-to-minimum-level
Jul 16, 2026
Merged

feat(serilog): support restrictedToMinimumLevel when configuring Serilog in code#5181
jamescrosswell merged 5 commits into
mainfrom
feat/serilog-restricted-to-minimum-level

test(serilog): update Net4_8 API approval snapshot

3516b83
Select commit
Loading
Failed to load commit list.
@sentry/warden / warden completed May 6, 2026 in 1m 18s

1 issue

Medium

Adding optional parameters to public Sentry() overloads is a binary-breaking change - `test/Sentry.Serilog.Tests/ApiApprovalTests.Run.DotNet9_0.verified.txt:24`

Adding new optional parameters (restrictedToMinimumLevel, levelSwitch) to the existing public Sentry() extension methods changes their metadata signatures. While source-compatible, this is binary-breaking in .NET: consumers compiled against a previous version of Sentry.Serilog will get a MissingMethodException at runtime until they recompile. For a public library this is an API contract change that warrants senior engineer review and, ideally, preservation of the prior signatures via additional overloads instead of in-place parameter additions.

4 skills analyzed
Skill Findings Duration Cost
code-review 1 54.7s $2.77
find-bugs 0 1m 13s $1.62
gha-security-review 0 58.2s $1.01
security-review 0 1m 10s $1.10

Duration: 4m 17s · Tokens: 1.1M in / 9.1k out · Cost: $6.51 (+dedup: $0.00)