release: 1.0.1 - #34
Merged
Merged
Conversation
Ships the first stable release as 1.0.1 rather than 1.0.0. 1.0.0 was prepared and merged but never tagged, so it was never published. Nothing was released and then withdrawn, and there is no 1.0.0 package on nuget.org for a consumer to upgrade from — the CHANGELOG says so explicitly so the gap in the version sequence is not read as a yanked release. PackageValidationBaselineVersion stays at 0.3.1: that is still the last version actually published, so it remains the correct surface to validate against. Validation passes. Package verified: 1.0.1, lib/net8.0 + lib/net10.0. Release build: 0 warnings. 410 tests (205 × net8.0/net10.0) pass. Co-Authored-By: Claude Opus 5 <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.
Ships the first stable release as 1.0.1 rather than 1.0.0.
Why the gap
1.0.0 was prepared and merged but never tagged, so it was never published. Nothing was released and then withdrawn, and there is no 1.0.0 package on nuget.org for anyone to upgrade from.
The CHANGELOG says this explicitly, because a missing version in a published sequence normally reads as a yanked release — which would be a much more alarming signal than the truth.
Changes
<Version>1.0.0→1.0.1[1.0.0]section →[1.0.1], with the note above;Unreleasedcompare and tag link refs repointed tov1.0.1PackageValidationBaselineVersionstays at0.3.1— that is still the last version actually published, so it remains the correct surface to validate against. Validation passes.The
SkipVersionPredicateexample in the README mentions"1.0.0"as a sample version string; it is unrelated to this package's own version and is left alone.What 1.0.1 contains
Everything from the 1.0.0 work: the interface inversion (breaking for implementers only), the standards catch-up, the buildless CodeQL analysis, and the narrowed exception handling. See the
[1.0.1]section for the full set — in particular the breaking change for implementers ofIUpdateSource/IUpdateChecker/ISelfUpdater, and the deliberate behaviour change where a masked defect now surfaces instead of being reported as "no update available".Verification
Release build: 0 warnings, 0 errors.
dotnet test --configuration Release: 410 passed, 0 failed (205 ×net8.0/net10.0).Package inspected:
1.0.1,lib/net8.0+lib/net10.0.No tag pushed. Publishing is tag-gated; tag
v1.0.1only after this merges.🤖 Generated with Claude Code