Repository navigation
Conversation
The release candidate note named 7.0.0-rc.2 and listed three things that work differently there. 7.0.0-rc.3 has all three fixes, so the note now names rc.3 and drops the list. The NU1605 paragraph stays, because rc.3's net11.0 builds depend on the .NET 11 RC 3 versions of the same packages. Refs NET-860 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
1 Skipped Deployment
|
The release candidate note named a version, so every new release candidate needed a docs PR. It now points at the latest release candidate on NuGet. The NU1605 paragraph now also names Microsoft.AspNetCore.Components.WebAssembly, which Sentry.AspNetCore.Blazor.WebAssembly depends on. It covers apps that pin an older .NET 11 release candidate as well as 10.0.x, and says that the error message shows the version to use. Refs NET-860 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
ric-oliv
marked this pull request as ready for review
October 30, 2026 14:30
This branch was successfully 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.
DESCRIBE YOUR PR
Version
7.0.0-rc.3of the Sentry SDK for .NET is out, so this PR updates the release candidate note at the top of the 7.x migration guide from #20143.The note listed three things that work differently on
7.0.0-rc.2. All three fixes are in rc.3, so I removed the list:Logging.AddSentry()afterClearProviders()adds Sentry's logger providers back, from fix(logging): make Logging.AddSentry() work after UseSentry and ClearProviders() sentry-dotnet#5776.DecompressionMethodsleaves out Brotli by default, from fix!: exclude Brotli from default SentryOptions.DecompressionMethods sentry-dotnet#5816.ILoggerentries through NLog no longer crashes withDebugon, from fix(nlog): stack overflow when Debug is on and NLog handles ILogger sentry-dotnet#5823.The note no longer names a release candidate. It points at the latest one on NuGet instead, so another release candidate before GA won't need a docs PR.
I also fixed two gaps in the NU1605 paragraph:
Sentry.AspNetCore.Blazor.WebAssemblydepends on the .NET 11 version ofMicrosoft.AspNetCore.Components.WebAssembly, so a Blazor WebAssembly app that pins 10.0.x fails to restore too. The paragraph now names that package.11.0.0-rc.2, fails the same way as one that pins 10.0.x. The paragraph now says "an older version" and that the error message shows the version to use.I checked this against
7.0.0-rc.3from nuget.org:DecompressionMethodsisGZip, Deflate.Microsoft.Extensions.Http10.0.0 or 11.0.0-rc.2.Microsoft.AspNetCore.Components.WebAssembly10.0.0.7.0.0-rc.3tag.No other page in the guide names a release candidate version. The whole alert still comes out at 7.0.0 GA.
Refs https://linear.app/getsentry/issue/NET-860
Refs getsentry/sentry-dotnet#5710
IS YOUR CHANGE URGENT?
Help us prioritize incoming PRs by letting us know when the change needs to go live.
Select exactly one option. For deadlines, replace
YYYY-MM-DDwith the due date. You can update this information later by editing the PR description.PRE-MERGE CHECKLIST
Make sure you've checked the following before merging your changes: