docs: state the support horizon and what happens if maintenance stops - #11
Merged
CaffeinatedCoder merged 1 commit intoAug 16, 2026
Merged
Conversation
SECURITY.md said which line receives fixes and that older majors are dropped, but not for how long the current line lives or how its end would be signalled — the two things a downstream consumer doing CRA-era supplier due diligence asks for after "do you have a disclosure channel". The horizon is tied to what the packages target: .NET 10 (and EF Core 10 for the EF Core packages), maintained while Microsoft supports that .NET release (LTS, November 2028) or until a new major supersedes it — with the note that majors here are cheap and a new one has never meant the old one lost fixes before its successor shipped. No fixed date, no SLA — an intention, phrased as one, with the promise that a change is recorded there first. A second paragraph names the single-maintainer risk plainly, says what "unmaintained" would look like, and that forking is the intended continuity mechanism. A third says how advisories reach consumers' tooling: GitHub Security Advisories → GitHub Advisory Database → NuGetAudit on restore. The .NET major in the horizon sentence is anchored to the core project's TargetFramework by SecurityPolicyConventionTests, so moving to net11.0 without moving the sentence fails the build. Verified: the new test passes as written, fails with the sentence saying .NET 11, fails with the anchor phrase reworded, passes restored. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Owner
Author
|
Dispatched run for this branch (base isn't |
CaffeinatedCoder
merged commit Aug 16, 2026
9c97af1
into
test/security-policy-consistency
3 checks passed
CaffeinatedCoder
added a commit
that referenced
this pull request
Aug 16, 2026
docs: land the support horizon on main (recovers #11)
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.
Stacked on #6 (extends
SecurityPolicyConventionTests); retargets tomainonce that merges. Mirror of EFCore.ComplexIndexes#22.Why
SECURITY.md said which line receives fixes and that older majors are dropped — but not for how long the current line lives, or how its end would be signalled. Those are the two things a downstream consumer doing CRA-era supplier due diligence asks right after "do you have a disclosure channel".
What
Three short paragraphs under Supported versions:
net10.0; EF Core 10 for the EF packages), maintained while Microsoft supports that .NET release (LTS, November 2028) or until a new major supersedes it. With the honest note that majors here are cheap and a new one has never meant the old one lost fixes before its successor shipped. No fixed date, no SLA — an intention, phrased as one.dotnet restore.The .NET major in the horizon sentence is anchored to the core project's
TargetFrameworkby a newSecurityPolicyConventionTestsmethod — moving tonet11.0without moving the sentence fails the build.Verified (verify-the-guard)
Passes as written; fails with the sentence saying .NET 11; fails with the anchor phrase reworded; passes restored.
Wording is yours to adjust — the test only pins the number.
🤖 Generated with Claude Code