Skip to content

Update dependency Mindscape.Raygun4Net.NetCore to 11.2.8 - #6028

Open
dependencyupdates[bot] wants to merge 1 commit into
masterfrom
renovate/mindscape.raygun4net.netcore-11.x
Open

dependencyupdates[bot] wants to merge 1 commit into
masterfrom
renovate/mindscape.raygun4net.netcore-11.x

Conversation

@dependencyupdates

@dependencyupdates dependencyupdates Bot commented Oct 20, 2026 •

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
Mindscape.Raygun4Net.NetCore (source) 11.2.6 → 11.2.8 age adoption passing confidence

Release Notes

MindscapeHQ/raygun4net (Mindscape.Raygun4Net.NetCore)

v11.2.8

  • Fix: #​590 - LogCritical could hang the calling thread when a message builder awaits
    • Mindscape.Raygun4Net.Extensions.Logging: on a thread with a SynchronizationContext or a custom TaskScheduler, for example a UI thread, LogCritical sends the log asynchronously, the same as the other log levels
    • On other threads, LogCritical still waits until the message is queued, so that the message still has the ASP.NET Core request data
    • See: #​591
  • Fix: #​587 - AddRaygunLogger could hang when a user provider or message builder depends on ILogger<T>
    • Mindscape.Raygun4Net.NetCore, Mindscape.Raygun4Net.AspNetCore: the client from AddRaygun creates its user provider and message builders when it builds its first message, not when it is created. This removes the dependency cycle with ILogger<T>
    • If the user provider or a message builder cannot be created, the application still starts. The message is not sent, the same as other send failures: SendAsync throws when ThrowOnError is true. The client tries again on the next message
    • A message sent while the user provider or message builders are being created, for example an error that their constructor logs, is sent without a user or without message builders
    • The Raygun logger still creates the client when the logger is created, so the client catches unhandled exceptions at startup
    • Mindscape.Raygun4Net.NetCore.Common: new public LazyRaygunUserProvider and LazyMessageBuilders classes. Use them when your own client factory gets the user provider or message builders from the container
    • See: #​591
  • Feature: Modern .NET reports capture the current W3C activity's trace and span identifiers in optional Details.TraceContext metadata
    • On .NET 6 and later, TraceId and SpanId are captured as lowercase hexadecimal strings when the exception report is built, including when the activity is not sampled
    • The metadata is omitted when no valid W3C activity is current. Automatic capture is not enabled for the netstandard2.0 target
    • See: #​588

v11.2.7

  • Feature: Opt-in request IP address masking (IsRequestIpAddressMasked)
    • Masks IPv4 and IPv4-mapped IPv6 addresses to the embedded IPv4 /24, and native IPv6 addresses to /48 (ports retained)
    • Excludes known client-IP forwarding headers and server variables from request metadata while masking is enabled
    • Supported on AspNetCore, MVC/Net4, and WebApi providers; disabled by default
    • Classic Net4/WebApi IP extraction now accepts IPv6 (including bracketed forms) from X-Forwarded-For / REMOTE_ADDR
    • XFF/REMOTE_ADDR acceptance requires canonical four-octet IPv4 values and strict port validation; masking still best-effort redacts the host when a port suffix is malformed
    • AspNetCore: unmasked IPv6+port keeps the historical addr:port shape; masked IPv6+port uses unambiguous [addr]:port
    • See: #​583
  • Fix: #​584 - SendInBackground could block indefinitely while collecting disk space on Windows when a mapped network drive was unavailable
    • Mindscape.Raygun4Net.NetCore.Common: disk-space collection checks the drive type before readiness, so drives that are not reported (e.g. network drives, non-root mounts) are no longer probed
    • Mindscape.Raygun4Net.NetCore.Common: disk space is collected on a background thread with a 5 second limit. If it runs out, the report is sent (or stored offline) with an empty DiskSpaceFree and DiskSpaceFreeStatus set to "TimedOut", instead of stale values
    • Mindscape.Raygun4Net.NetCore.Common: if the disk check fails, the report has an empty DiskSpaceFree and DiskSpaceFreeStatus set to "Error"
    • Mindscape.Raygun4Net.NetCore.Common: reports that arrive while another report is collecting disk space wait for the fresh values instead of skipping them, for up to twice the disk limit. Machine details (OS, CPU, memory) are cached separately, and only the first report of the process waits for them
    • See: #​586
    • See: #​585
  • Feature: IsDiskSpaceFreeIgnored setting turns off disk space collection
    • Reports sent while it is on have an empty DiskSpaceFree and DiskSpaceFreeStatus set to "Ignored"
    • Those reports never wait for a disk check running for another client, so an unresponsive disk cannot delay them
    • Applies to the modern .NET packages only. The .NET Framework packages (Mindscape.Raygun4Net, .Mvc, .WebApi, .Azure.WebJob) still collect disk space without a time limit and have no opt-out
    • See: #​585

Configuration

📅 Schedule: (UTC)

  • Branch creation
    • At any time (no schedule defined)
  • Automerge
    • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

Commands to ignore dependencies

You can trigger dependency actions by commenting on this PR:

  • @particularbot ignore this major version
  • @particularbot ignore this minor version
  • @particularbot ignore this dependency

@dependencyupdates dependencyupdates Bot added dependencies Pull requests that update a dependency file NuGet labels Oct 20, 2026
@dependencyupdates
dependencyupdates Bot force-pushed the renovate/mindscape.raygun4net.netcore-11.x branch 2 times, most recently from 441862e to befc690 Compare November 3, 2026 07:58
@dependencyupdates
dependencyupdates Bot force-pushed the renovate/mindscape.raygun4net.netcore-11.x branch from befc690 to 4695a89 Compare November 17, 2026 21:17
@dependencyupdates dependencyupdates Bot changed the title Update dependency Mindscape.Raygun4Net.NetCore to 11.2.7 Update dependency Mindscape.Raygun4Net.NetCore to 11.2.8 Nov 17, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Pull requests that update a dependency file NuGet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants