v0.3.0: per-TFM floors for runtime-aligned Microsoft deps; bump Spectre to 0.57.2#17
Merged
Conversation
…re to 0.57.2 Split Microsoft.Extensions.DependencyInjection.Abstractions and Microsoft.Extensions.Http into per-target-framework ItemGroups so each TFM floors them at its own aligned major: net8.0 -> 8.0.2 / 8.0.1 (latest stable 8.0.x LTS servicing), net10.0 -> 10.0.10 / 10.0.10. A library PackageReference is a floor NuGet forces on every consumer, so the previous single 10.0.x floor dragged net8 consumers off their own 8.0.x servicing line. Spectre.Console (and test-only Spectre.Console.Testing) bumped 0.56.0 -> 0.57.2; Spectre.Console.Cli stays 0.55.0 (latest stable). As independently-versioned third-party packages they remain a single common PackageReference, not split per-TFM. Build clean for both TFMs (TreatWarningsAsErrors), 196 tests pass, and the packed .nuspec shows the intended per-major floors in each TFM dependency group.
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
1 participant
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
Adopts per-target-framework dependency floors for the runtime-aligned Microsoft platform packages, and bumps Spectre to latest stable.
Since 0.2.0 multi-targeted
net8.0alongsidenet10.0but flooredMicrosoft.Extensions.*at a single10.0.x, net8 consumers were forced off their own8.0.xLTS servicing line — a libraryPackageReferenceversion is a minimum floor NuGet forces on every downstream consumer.Changes
Split the two runtime-aligned Microsoft deps into per-TFM
ItemGroups:Microsoft.Extensions.DependencyInjection.AbstractionsMicrosoft.Extensions.HttpEach is the latest stable servicing version of that TFM's major (verified on nuget.org).
Bump
Spectre.Console0.56.0 → 0.57.2 (and test-onlySpectre.Console.Testingto match).Spectre.Console.Clistays 0.55.0 (latest stable). These are independently-versioned third-party packages, so they stay a single commonPackageReference— not split per-TFM.Microsoft.SourceLink.GitHub(PrivateAssets="All", build-time only) and the test project (IsPackable=false) left as common refs.Version 0.2.0 → 0.3.0, CHANGELOG updated.
Verification
dotnet build -c Releaseclean for both TFMs (TreatWarningsAsErrors=true), 0 warnings.dotnet test -c Release→ 196 passed.dotnet pack+ inspected the.nuspecinside the.nupkg: each TFM dependency group shows the intended per-major floors; Spectre common across both; SourceLink correctly excluded.