Skip to content

docs: correct the 2.1.0 range-resolution note #98

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
StuartMeeks wants to merge 1 commit into
base: main
Choose a base branch
from
Open

docs: correct the 2.1.0 range-resolution note #98

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 6 additions & 2 deletions CHANGELOG.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -26,8 +26,12 @@ boundary (the identity was discoverable); the real boundary remains the filesyst
permissions on the credentials directory, and `AdditionalEntropy` — or the DPAPI / platform
keychain backends — is the way to bind a store to a secret. See the README's Security model.

No provider-facing interface changed, so this is a minor and the provider packages need no
re-cut: their `[2.0.0, 3.0.0)` dependency range resolves against 2.1.0 unchanged.
No provider-facing interface changed, so this is an API-compatible minor and existing
provider assemblies keep working against it. It does **not**, however, reach provider
_consumers_ on its own: a NuGet version range resolves to its **floor**, so the 2.x
providers' `[2.0.0, 3.0.0)` dependency resolves to core **2.0.0**, not 2.1.0. A downstream
consumer keeps getting the old core until the provider packages raise their floor to
`[2.1.0, 3.0.0)` and re-cut.

### Changed

Expand Down
Loading