Cut 1.4.0: the test container source - #60
Merged
Merged
Conversation
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
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.
Release prep for 1.4.0.
VersionPrefixandFileVersionmove to 1.4.0, and the changelog gains its entry.The published version comes from the
v*tag, so this does not decide it. What it decides is what the continuous preview feed stamps: left at 1.3.1 the previews after this release would be1.3.1-ci.N, which sorts below both the released 1.3.1 and 1.4.0. That is the stale-line trap.What 1.4.0 contains
#59, and nothing else.
ITestContainerSource,ISharedTestRegistration,[Shared], and[Mock]/[InjectValues]/[TestExport]implementing the interface.A minor version rather than a major: the public API diff is purely additive, no member removed and no signature changed, and a suite that adopts none of it behaves exactly as it did.
Verified on this branch
dotnet build --configuration Release -p:ContinuousIntegrationBuild=true— clean.scripts/coverage.sh 85— 90.6%, above the gate.TestContainerSourceis at 100%.scripts/verify-packages.sh 1.4.0— packs the nine shipping projects and consumes them from throwaway apps onnet8.0andnet10.0; both resolved a generated registration at run time.Why now
Hardened.Frameworkneeds it. Its half of this work is written and green against a local1.4.0-isolation1pack: 8341 tests pass in Release, and the eleven tests that changed are all ones whose subject is the reuse itself. That branch cannot reach CI until 1.4.0 is on nuget.org.🤖 Generated with Claude Code