Update dependency NLog.Extensions.Logging to v6

[dependencyupdates]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
NLog.Extensions.Logging	5.5.0 → 6.1.1

---

Release Notes

NLog/NLog.Extensions.Logging (NLog.Extensions.Logging)

v6.1.1

• #​822 NLogLogger - Optimize for default EventId capture (@​snakefoot)
• #​824 Introduced WriteToJsonConsole for fluent API to match AddJsonConsole (@​snakefoot)
• #​825 NLogLoggerProvider - Implement IAsyncDisposable (@​snakefoot)
• #​826 MicrosoftConsoleJsonLayout - Forward MaxRecursionLimit to State-JsonLayout (@​snakefoot)
• #​827 MicrosoftConsoleLayoutRenderer - Apply Span for EventId (@​snakefoot)
• #​828 Replace NETCOREAPP3_1_OR_GREATER with new NET (@​snakefoot)
• #​830 Updated to NLog v6.1 (@​snakefoot)

v6.1.0

• #​818 Added TargetFramework .NET 10 (@​snakefoot)

v6.0.6

• #​817 Updated to NLog v6.0.6 (@​snakefoot)
• #​814 Avoid boxing ITuple when used for BeginScope (@​snakefoot)
• #​813 Allow BeginScope to perform reflection of KeyValuePair (@​snakefoot)

v6.0.5

• #​811 Updated to NLog v6.0.5 (@​snakefoot)
• #​809 NLogLoggingConfiguration - ToString includes AutoReload=true (@​snakefoot)

v6.0.4

• #​808 Updated to NLog v6.0.4 (@​snakefoot)

v6.0.3

• #​806 Updated to NLog v6.0.3 (@​snakefoot)

v6.0.2

• #​805 Updated to NLog v6.0.2 (@​snakefoot)

v6.0.1

• #​802 Updated to NLog v6.0.1 (@​snakefoot)
• #​801 .NET Framework v4.6.2 with UseNLog for IHostApplicationBuilder (@​snakefoot)
• #​799 Fixed namespace for HostRootDirLayoutRenderer (@​snakefoot)

v6.0.0: Version 6.0

• Updated to NLog v6.0
• Removed support for NetStandard 1.3 + 1.5
• Updated .NET Framework 4.6.2 with NET8-nuget-dependencies
• Enabled nullable references
• Avoid boxing when extracting LogEvent properties from struct
• Reduce allocation when creating LogEvent with properties by using ReadOnlySpan
• Enabled <IsAotCompatible>
• Added ${host-environment} for NLog.Extensions.Hosting
• Added ${host-rootdir} for NLog.Extensions.Hosting
• Added ${host-appname} for NLog.Extensions.Hosting
• Added RegisterHostSettings for NLog.Extensions.Hosting

List of major changes in NLog 6.0: https://nlog-project.org/2025/04/29/nlog-6-0-major-changes.html

---

Configuration

📅 Schedule: 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

[abparticular]

We shouldn't be mixing dynamic and static archive behavior, so the code was modified to use static log file names. This means the "active" log file will no longer include the date, e.g. logfile.txt instead of logfile.yyyy-MM-dd.txt.

Archived log files, will include the date as well as the sequence number, e.g. logfile.yyyy-MM-dd.##.txt instead of logfile.yyyyMMdd.#.txt previously. (Note that the archive filename date format is not consistent with the "active" filename in current SC versions).

[dependencyupdates]

Edited/Blocked Notification

Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.

You can manually request rebase by checking the rebase/retry box above.

⚠️ Warning: custom changes will be lost.

[ramonsmits]

We shouldn't be mixing dynamic and static archive behavior, so the code was modified to use static log file names. This means the "active" log file will no longer include the date, e.g. logfile.txt instead of logfile.yyyy-MM-dd.txt.

I think that is an improvement and how it should be. Makes it super easy to use a tail like tool to.

I would include this in the milestone and label it as a patch as this isn't only a version bump but also a fix in behavior.