Repository navigation
Release Healthie.NET 4.1.3 - #83
Merged
Merged
Conversation
This was referenced Sep 29, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Healthie.NET 4.1.2 cannot take the current Dependabot set as-is: xUnit 4 requires Microsoft Testing Platform configuration, Aspire packages need the matching AppHost SDK/CLI bundle, and Quartz 4 drops the library's supported .NET 8 surface. This release updates every compatible dependency, completes the xUnit 4 and Aspire migrations, defers Quartz 4 for a future major release, removes the redundant direct SSH.NET test dependency, and pins Scorecard upload to CodeQL Action v4.38.2.
The result is a 4.1.3 patch release with regenerated locked restores and no known vulnerable NuGet dependencies.
Validation:
dotnet restore --locked-modegit diff --checkSupersedes #66 and #82. Quartz 4 PRs #80 and #81 were closed after their refreshed branches reproduced the expected .NET 8/API incompatibility.