Skip to content

Bump NuGet dependencies - #7498

Merged
donker merged 22 commits into
dnnsoftware:developfrom
bdukes:bump-nuget-dependencies
Sep 4, 2026
Merged

Bump NuGet dependencies#7498
donker merged 22 commits into
dnnsoftware:developfrom
bdukes:bump-nuget-dependencies

Conversation

@bdukes

@bdukes bdukes commented Sep 2, 2026

Copy link
Copy Markdown
Contributor

Summary

This PR bumps NuGet dependencies. There are more to bump, but my local environment is not happy with me and I can't see what's working and what's not, so I'll need to do some experimentation via this branch.

@bdukes bdukes added this to the 10.4.0 milestone Sep 2, 2026
@bdukes bdukes added Type: Maintenance .NET Pull requests that update .net code labels Sep 2, 2026
@bdukes
bdukes force-pushed the bump-nuget-dependencies branch 16 times, most recently from 298e1c3 to 50d05f2 Compare September 3, 2026 13:28
- AngleSharp from 1.5.2 to 1.7.2
- AngleSharp.Css from 1.0.0-beta.224 to 1.0.2
- HtmlSanitizer from 9.1.968-beta to 9.2.1039
- NUnit from 4.5.0 to 4.6.1
- NUnit.Analyzers from 4.11.2 to 4.14.0
- NUnit3TestAdapter from 6.1.0 to 6.3.0
- Microsoft.NET.Test.Sdk from 18.0.1 to 18.9.0
- Verify.NUnit from 31.13.2 to 32.0.0
- coverlet.collector from 8.0.0 to 10.0.1
- MailKit from 4.16.0 to 4.17.0
- MimeKit from 4.16.0 to 4.17.0
- BouncyCastle.Cryptography from 2.6.2 to 2.7.0
@bdukes
bdukes force-pushed the bump-nuget-dependencies branch 2 times, most recently from ea8e9e6 to 87cc37d Compare September 3, 2026 13:53
Referencing DotNetNuke.Instrumentation as net48 was causing problems

Platform/DotNetNuke.ContentSecurityPolicy/DotNetNuke.ContentSecurityPolicy.csproj
Platform/DotNetNuke.DependencyInjection/DotNetNuke.DependencyInjection.csproj
Platform/DotNetNuke.Web.Client.ResourceManager/DotNetNuke.Web.Client.ResourceManager.csproj
@bdukes
bdukes force-pushed the bump-nuget-dependencies branch from 87cc37d to 57eb8a8 Compare September 4, 2026 15:53
@bdukes
bdukes force-pushed the bump-nuget-dependencies branch from 57eb8a8 to f6777d3 Compare September 4, 2026 16:10
@bdukes
bdukes marked this pull request as ready for review September 4, 2026 16:33
@bdukes

bdukes commented Sep 4, 2026

Copy link
Copy Markdown
Contributor Author

Hmm… built successfully via GitHub Actions, still failed on Azure Pipelines

@valadas

valadas commented Sep 4, 2026

Copy link
Copy Markdown
Contributor

Soo, is this when we disconnect azure ;)

@bdukes

bdukes commented Sep 4, 2026

Copy link
Copy Markdown
Contributor Author

I've successfully installed the artifact from the GitHub Actions build and done an upgrade from 10.3.3 after installing 2sxc.

I'd be good with removing the connection to Azure Pipelines.

@bdukes
bdukes requested review from donker, mitchelsellers and valadas and removed request for valadas September 4, 2026 17:39
@bdukes

bdukes commented Sep 4, 2026

Copy link
Copy Markdown
Contributor Author

After this is merged, the following NuGet packages are still behind their latest version:

Spectre

  • Spectre.Console & Spectre.Console.Testing are at 0.54.0, latest is 0.57.2
  • Spectre.Console.Cli is at 0.53.1, latest is 0.55.0

Spectre is used by Cake, and also used by the Bulk Install Deploy Client. A version bump does require code changes in the Deploy Client. I've had issues with the version of Spectre cause problems running Cake, even when I'm trying to configure things so that the Deploy Client shouldn't affect the Cake version.

Cake

  • Cake.Frosting is at 6.1.0, latest is 6.2.0
  • Cake.FileHelpers is at 7.0.0, latest is 9.0.0
  • Cake.Json is at 7.0.1, latest is 11.0.0
  • Cake.Issues & Cake.Frosting.Issues.MsBuild are at 5.9.1, latest is 6.0.0

The Cake.Issues bump from 5.x to 6.x does require code changes and bringing in additional NuGet packages. The other libraries can be bumped without code changes, but any time I touch Cake things, I get conflicts with Spectre. Bumping Cake.Frosting from 6.1.0 to 6.2.0 also bumps Spectre.Console.

XUnit

  • xunit.runner.visualstudio is at 3.1.5, latest is 4.0.0
  • xunit.v3 is at 3.2.2, latest is 4.0.0

Bulk Install uses XUnit, while the rest of the project uses NUnit. I have a PR which migrates from XUnit to NUnit, so I did not bother dealing with this major version bump. FWIW, I believe the XUnit tests are not currently being run in CI, so that's another benefit of the switch.

QuickIO

  • QuickIO.NET is at 2.6.2, latest is 3.0.37

QuickIO 3.x supports .NET 7+, so we are stuck on 2.x (2.6.2 is the latest 2.x version).

@bdukes
bdukes force-pushed the bump-nuget-dependencies branch from 2294388 to f6777d3 Compare September 4, 2026 17:51
@bdukes bdukes mentioned this pull request Sep 4, 2026

@donker donker left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I've managed to build in VS locally and I've managed to build and deploy packages with this. So green light from me.

@donker
donker added this pull request to the merge queue Sep 4, 2026
Merged via the queue into dnnsoftware:develop with commit c5fc79a Sep 4, 2026
13 of 14 checks passed
@bdukes
bdukes deleted the bump-nuget-dependencies branch September 8, 2026 18:53
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

.NET Pull requests that update .net code Type: Maintenance

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants