docs: correct the 2.1.0 range-resolution note - #98
Open
StuartMeeks wants to merge 1 commit into
Open
StuartMeeks wants to merge 1 commit into
StuartMeeks wants to merge 1 commit into
Conversation
The 2.1.0 entry claimed the provider packages "need no re-cut: their [2.0.0, 3.0.0) dependency range resolves against 2.1.0 unchanged." That is wrong. NuGet resolves a version range to its floor (lowest-applicable-version), so the 2.x providers' [2.0.0, 3.0.0) dependency resolves to core 2.0.0, not 2.1.0. Downstream consumers of the providers therefore did not pick up the 2.1.0 keystore data-loss fix at all. Correct the note to say the fix reaches downstream consumers only once the provider packages raise their floor to [2.1.0, 3.0.0) and re-cut, so other consumers of this package are not misled into thinking a core minor reaches them on its own. Keep the note free of any specific downstream provider version — that is the providers' repo to record, and coupling it here would go stale.
StuartMeeks
force-pushed
the
docs/correct-2.1.0-range-resolution-note
branch
from
September 21, 2026 12:48
88d3e6c to
b8c997d
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
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.
What
Corrects a factual error in the released 2.1.0 CHANGELOG entry.
The error
The 2.1.0 note read:
The second clause is wrong. NuGet resolves a version range to its floor (lowest-applicable-version), so the 2.x providers'
[2.0.0, 3.0.0)dependency resolves to core 2.0.0, not 2.1.0. Consumers of the providers therefore did not pick up 2.1.0 — including its keystore data-loss fix — automatically.The correction
The note now states that 2.1.0 is API-compatible (existing provider assemblies keep working), but does not reach provider consumers on its own; a downstream consumer keeps resolving core 2.0.0 until the provider packages raise their floor to
[2.1.0, 3.0.0)and re-cut.Docs-only; the first (correct) clause about API compatibility is preserved. The note deliberately names no specific downstream provider version — that is the providers' repo to record, and coupling it here would go stale. No
[Unreleased]entry — consistent with how the estate handles changelog/doc corrections.