Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Document the release and environment changes for v7.0.0

Open Beginner friendly
  • Is something wrong?
#5,709 1 comment 0 reactions 1 assignee View on GitHub

Maintainers usually reply within 1 day

@jamescrosswell is already working on this.

Since Oct 13, 2026.

  • #19960 by @jamescrosswell — open

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
77/100
Issue type
Documentation
Clarity
Clearly specified
Activity status
Active
Tech stack
csharp
Domain
documentation

Research direction

Start with docs/platforms/dotnet/common/configuration/options.mdx and platform-includes/set-release/dotnet.mdx, then check the Google Cloud Functions and Blazor WebAssembly guides. Compare the option wording with the listed 7.0.0 behavior and the open #5703 dependency. Done means the docs explain the Android and iOS release precedence, environment sources and scope behavior, and accurately describe host environment support.

Written by the indexing model from the issue text.

Description

.NET Docs Next Major

#5671 changed how release, environment and SDK name are resolved in 7.0.0. #5703, which is still open, extends the host-environment mapping from ASP.NET Core to Blazor WebAssembly and Google Cloud Functions. The option docs still describe 6.x.

The .NET docs aren't versioned. As with #5698, the new text should say that it applies from 7.0.0 on, or the PR should merge when 7.0.0 ships.

What changed in 7.0.0

  • Release, distribution, environment and default tags are resolved once, at init. Every kind of telemetry then takes each value from the item itself, then from the scope, then from those defaults.
  • An environment set on the scope now applies to logs, metrics, sessions, check-ins and trace propagation, not only to events. Setting Scope.Environment to null clears the override.
  • Scope.Release and Scope.Distribution are removed, so release and distribution can only be set on SentryOptions.
  • On Android and iOS, SENTRY_RELEASE now takes precedence over the release derived from the app package.
  • With #5703, Blazor WebAssembly and Google Cloud Functions take the environment from the host environment, as ASP.NET Core does. The precedence is Environment set in code or appsettings.json, then SENTRY_ENVIRONMENT, then the host environment (Production, Staging and Development lower-cased, custom names kept as they are).
  • Events, transactions, logs and metrics report the SDK name of the integration that initialized Sentry, such as sentry.dotnet.aspnetcore. Blazor WebAssembly now reports sentry.dotnet.aspnetcore.blazor.webassembly. Serilog and NLog events no longer report sentry.dotnet.serilog or sentry.dotnet.nlog, so saved queries and alerts that filter on those names need updating.

Pages to update in getsentry/sentry-docs

  • docs/platforms/dotnet/common/configuration/options.mdx:
    • Environment says only ASP.NET Core picks up the host environment. Add Blazor WebAssembly and Google Cloud Functions once #5703 merges, give the precedence above, and say that a scope's environment now applies to every kind of telemetry.
    • Release: say that on Android and iOS the default comes from the app package, and that SENTRY_RELEASE takes precedence over it.
  • platform-includes/set-release/dotnet.mdx describes how the SDK finds the release (SENTRY_RELEASE, then the entry assembly's version). Add the Android and iOS case.
  • docs/platforms/dotnet/guides/google-cloud-functions/index.mdx already lists "Environment is automatically set (IHostingEnvironment)" as a feature. That only becomes true with #5703. Check the Blazor WebAssembly guide too.

The SDK name change mostly belongs in the 7.x migration guide; it needs no page of its own.

Dominant language
C#
Stars
768
Forks
253
Avg merge
2d 3h
Merged PRs (30d)
82

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from getsentry/sentry-dotnet

All issues in getsentry/sentry-dotnet

Similar issues

More C# issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.