v0.7.1: per-TFM dependency floors and servicing bumps - #5
Merged
Conversation
Split the runtime-aligned Microsoft platform packages into per-target-framework floors so net8 (LTS) consumers keep their 8.0.x servicing line instead of being forced onto 10.0.x: net8 floors DI.Abstractions 8.0.2, Http 8.0.1, ProtectedData 8.0.0; net10 floors all three at 10.0.10. Bump Spectre.Console to 0.57.2 and Microsoft.SourceLink.GitHub to 10.0.301; test-only Microsoft.NET.Test.Sdk to 18.8.1. Spectre.Console.Cli stays 0.55.0 (latest stable). No public API change. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
StuartMeeks
force-pushed
the
release/0.7.1
branch
from
July 24, 2026 04:05
3c70519 to
b60a60d
Compare
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
2 participants
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.
Summary
Routine maintenance release. Headline change is adopting per-target-framework dependency floors for the runtime-aligned Microsoft platform packages, plus servicing bumps. No public API change.
Why per-TFM floors
A
PackageReferenceversion in a library is a minimum floor NuGet forces on every downstream consumer. Flooring the Microsoft platform packages at a single10.0.xdraggednet8.0(LTS) consumers off their own8.0.xservicing line, even though anet8.0asset shipped in 0.7.0. Each target now floors at its aligned major.Changed
net8.0:Microsoft.Extensions.DependencyInjection.Abstractions8.0.2,Microsoft.Extensions.Http8.0.1,System.Security.Cryptography.ProtectedData8.0.0net10.0: all three at10.0.10Spectre.Console→0.57.2,Microsoft.SourceLink.GitHub→10.0.301, test-onlyMicrosoft.NET.Test.Sdk→18.8.1Spectre.Console.Clistays0.55.0(latest stable;Spectre.Consoleis deliberately not lowered — pre-1.0 makes a low floor meaningless)Verification
dotnet build -c Release— both TFMs, 0 warnings (TreatWarningsAsErrorson)dotnet test -c Release— 145/145 pass.nuspec:net8.0dependency group shows the8.0.xfloors andnet10.0shows10.0.10, as intended🤖 Generated with Claude Code