publish: getsentry/sentry-dotnet@6.8.0

[sentry-release-bot]

Requested by: @jamescrosswell

Merge target: (default)

Quick links:

• View changes
• View check runs

Assign the accepted label to this issue to approve the release.

Targets

• nuget
• github
• registry

Checked targets will be skipped (either already published or user-requested skip). Uncheck to retry a target.

---

📋 Changelog

Features ✨

Logs

• feat(logs): add log4net integration by @Flash0ver in #5172
• feat(logs): add NLog integration by @Flash0ver in #5176

Other

• feat(serilog): support restrictedToMinimumLevel when configuring Serilog in code by @jamescrosswell in #5181
• Attachments can now be sent with transactions by setting AddToTransactions on SentryAttachment #5182 by @jamescrosswell in #5182
• Added SentrySdk.RecordTransaction to record already-completed transactions and spans (e.g. replayed through a proxy) #5333 by @jamescrosswell in #5333
• The Environment set on the Scope now gets synchronized to the native layers (sentry-cocoa and sentry-native) by @bitsandfoxes in #5365

Fixes 🐛

• fix: SentrySpanProcessor no longer leaks spans whose Activity never ends (e.g. aborted requests); the Activity is now held via a WeakReference so orphaned spans are pruned once it is garbage-collected. by @Ermabo in #5393
• The SDK was incorrectly ignoring server rate limits for errors, check-ins, and logs by @jamescrosswell in #5412
• fix: BackpressureMonitor.Dispose() no longer deadlocks on single-threaded targets by @jamescrosswell in #5330
• fix: Create a single TaskBlockingListener per process for CaptureBlockingCalls by @jamescrosswell in #5381

Dependencies ⬆️

Deps

• chore(deps): update CLI to v3.6.1 by @github-actions in #5417
• chore(deps): update Native SDK to v0.15.4 by @github-actions in #5416
• chore(deps): update Cocoa SDK to v9.22.0 by @github-actions in #5395
• chore(deps): update Java SDK to v8.49.0 by @github-actions in #5398

Other

• ci: drop install-zstd workaround by @jpnurmi in #5391
• docs: add Sentry.OpenTelemetry.Exporter to README.md by @Flash0ver in #5194
• meta: Update CODEOWNERS by @Flash0ver in #5386

[github-actions]

Approved. Checking CI status on the release branch. Publishing will start automatically when CI passes.

[getsantry]

CI checks passed for getsentry/sentry-dotnet@6.8.0. Publishing is starting now.

[jamescrosswell]

Publish run #12178 failed — Docker Hub was temporarily unreachable.

The publish job runs craft as a container action, so its first step is docker pull getsentry/craft:latest. All three attempts timed out against Docker Hub:

/usr/bin/docker pull getsentry/craft:latest
Error response from daemon: Get "https://registry-1.docker.io/v2/":
  net/http: request canceled while waiting for connection (Client.Timeout exceeded...)
  ...back off 4.894 seconds before retry.
  ...context deadline exceeded          (retry 2)
  ...context deadline exceeded          (retry 3)
##[error]Docker pull failed with exit code 1

craft never started, so nothing was published (no NuGet push, no GitHub tag) — a re-run is safe. This also left the issue orphaned: the failure-handler steps (update-issue.js / post-result.js) crashed with MODULE_NOT_FOUND because the checkout step had been skipped, so the label was never removed and no failure comment was posted.

Could someone on the release team re-run the publish for 6.8.0? Thanks!

[github-actions]

Approved. Checking CI status on the release branch. Publishing will start automatically when CI passes.