deps: Update dependency Grynwald.MdDocs.MSBuild to version 0.6.39

[renovate]

This PR contains the following updates:

Package	Type	Update	Change
Grynwald.MdDocs.MSBuild	nuget	minor	0.5.180 -> 0.6.39

---

Release Notes

ap0llo/mddocs

v0.6.39

New Features

• .NET CLI tool: Allow mddocs to run on newer versions of .NET by default
• MSBuild Integration: Run MdDocs outside MSBuild process

Bug Fixes

• Remove framework assembly references from Grynwald.MdDocs.MSBuild NuGet package
• Retain blank lines from <code> blocks in the Markdown output

Breaking Changes

• The Grynwald.MdDocs.MSBuild package now requires the .NET 6 (or later) runtime to be installed, even when running in "Full Version" MSBuild or Visual Studio

Details

.NET CLI tool: Allow mddocs to run on newer versions of .NET by default

Enable .NET runtime setting to allow running mddocs on newer versions of .NET if none of the supported runtimes are available.

This means - while currently, the mddocs CLI tool supports .NET 6 and .NET 7, it will use the .NET 8 or newer runtime when no version of .NET 6 or .NET 7 is installed.

• See Also: https://learn.microsoft.com/en-us/dotnet/core/whats-new/dotnet-core-2-1#roll-forward
• Commit: 781564e

MSBuild Integration: Run MdDocs outside MSBuild process

Breaking Change: The Grynwald.MdDocs.MSBuild package now requires the .NET 6 (or later) runtime to be installed, even when running in "Full Version" MSBuild or Visual Studio

In the MSBuild integration, replace the MdDocs MSBuild tasks that run MdDocs inside the MSBuild process with targets that run the MdDocs CLI in a separate process.

This way, MdDocs needs to only run on .NET 6 / .NET 7 and no longer has to consider compatibility with .NET Framework.
Also, this should resolve any dependency conflicts between MdDocs and MSBuild.

The MSBuild integration continues to work in both the "Core" (.NET SDK) and "Desktop" (Visual Studio) versions of MSBuild as long as a compatible .NET runtime is installed.

• Pull Request: #​237
• Commit: a502c7b

Remove framework assembly references from Grynwald.MdDocs.MSBuild NuGet package

Remove redundant framework assembly references since the Grynwald.MdDocs.MSBuild package is a build tools package which does not require references to .NET Framework assemblies to be added to consuming projects.

• Pull Request: #​234
• Commit: 14d8c73

Retain blank lines from <code> blocks in the Markdown output

Update dependency Grynwald.MarkdownGenerator to version 3.0.106 which includes a fix for serialization of Markdown code blocks (all blank lines from code blocks used to be removed from the output).

• See: #​245
• Pull Request: #​249
• Commit: 720c8ae

---

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 Mend Renovate. View repository job log here.

[renovate]

⚠ Artifact update problem

Renovate failed to update artifacts related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

• any of the package files in this branch needs updating, or
• the branch becomes conflicted, or
• you click the rebase/retry checkbox if found above, or
• you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: src/Utilities/packages.lock.json, src/Utilities.Test/packages.lock.json

installing v2 tool dotnet v7.0.201
dotnet-install: Note that the intended use of this script is for Continuous Integration (CI) scenarios, where:
dotnet-install: - The SDK needs to be installed without user interaction and without admin rights.
dotnet-install: - The SDK installation doesn't need to persist across multiple CI runs.
dotnet-install: To set up a development environment or to run apps, use installers rather than this script. Visit https://dotnet.microsoft.com/download to get the installer.

dotnet-install: Attempting to download using primary link https://dotnetcli.azureedge.net/dotnet/Sdk/7.0.201/dotnet-sdk-7.0.201-linux-x64.tar.gz
dotnet-install: Extracting zip from https://dotnetcli.azureedge.net/dotnet/Sdk/7.0.201/dotnet-sdk-7.0.201-linux-x64.tar.gz
dotnet-install: Installed version is 7.0.201
dotnet-install: Binaries of dotnet can be found in /opt/buildpack/tools/dotnet
dotnet-install: Note that the script does not resolve dependencies during installation.
dotnet-install: To check the list of dependencies, go to https://learn.microsoft.com/dotnet/core/install, select your operating system and check the "Dependencies" section.
dotnet-install: Installation finished successfully.
linking tool dotnet v7.0.201

File name: src/Utilities.Logging/packages.lock.json

installing v2 tool dotnet v7.0.201
dotnet-install: Note that the intended use of this script is for Continuous Integration (CI) scenarios, where:
dotnet-install: - The SDK needs to be installed without user interaction and without admin rights.
dotnet-install: - The SDK installation doesn't need to persist across multiple CI runs.
dotnet-install: To set up a development environment or to run apps, use installers rather than this script. Visit https://dotnet.microsoft.com/download to get the installer.

dotnet-install: Attempting to download using primary link https://dotnetcli.azureedge.net/dotnet/Sdk/7.0.201/dotnet-sdk-7.0.201-linux-x64.tar.gz
dotnet-install: Extracting zip from https://dotnetcli.azureedge.net/dotnet/Sdk/7.0.201/dotnet-sdk-7.0.201-linux-x64.tar.gz
dotnet-install: Installed version is 7.0.201
dotnet-install: Binaries of dotnet can be found in /opt/buildpack/tools/dotnet
dotnet-install: Note that the script does not resolve dependencies during installation.
dotnet-install: To check the list of dependencies, go to https://learn.microsoft.com/dotnet/core/install, select your operating system and check the "Dependencies" section.
dotnet-install: Installation finished successfully.
linking tool dotnet v7.0.201

File name: src/Utilities.Configuration/packages.lock.json, src/Utilities.Configuration.Test/packages.lock.json

installing v2 tool dotnet v7.0.201
dotnet-install: Note that the intended use of this script is for Continuous Integration (CI) scenarios, where:
dotnet-install: - The SDK needs to be installed without user interaction and without admin rights.
dotnet-install: - The SDK installation doesn't need to persist across multiple CI runs.
dotnet-install: To set up a development environment or to run apps, use installers rather than this script. Visit https://dotnet.microsoft.com/download to get the installer.

dotnet-install: Attempting to download using primary link https://dotnetcli.azureedge.net/dotnet/Sdk/7.0.201/dotnet-sdk-7.0.201-linux-x64.tar.gz
dotnet-install: Extracting zip from https://dotnetcli.azureedge.net/dotnet/Sdk/7.0.201/dotnet-sdk-7.0.201-linux-x64.tar.gz
dotnet-install: Installed version is 7.0.201
dotnet-install: Binaries of dotnet can be found in /opt/buildpack/tools/dotnet
dotnet-install: Note that the script does not resolve dependencies during installation.
dotnet-install: To check the list of dependencies, go to https://learn.microsoft.com/dotnet/core/install, select your operating system and check the "Dependencies" section.
dotnet-install: Installation finished successfully.
linking tool dotnet v7.0.201

[renovate]

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.