docs: state the support horizon and what happens if maintenance stops - #22
Merged
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 package actually depends on: each major tracks one EF Core major, and the intention is to maintain the current line while Microsoft supports that EF Core release (EF Core 10, LTS, November 2028) or until a new major supersedes it. 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 (archived repository, deprecated packages, a note in the policy), 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 EF Core major in the horizon sentence is anchored to the core project's dependency floor by SecurityPolicyConsistencyTests, so moving to EF Core 11 without moving the sentence fails the build. Verified: the new test passes as written, fails with the sentence saying EF Core 11, fails with the anchor phrase reworded, passes restored. ClaudeMdConsistencyTests passes. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Owner
Author
|
Dispatched run for this branch (base isn't |
CaffeinatedCoder
changed the base branch from
test/security-policy-consistency
to
main
August 16, 2026 12:31
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 #19 (extends
SecurityPolicyConsistencyTests); retargets tomainonce that merges.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", and the CRA's own manufacturer duties (support period, EOL communication) are what they'll be checking their dependencies against from Dec 2027.
What
Three short paragraphs under Supported versions:
dotnet restore.The EF Core major in the horizon sentence is anchored to the core project's
Microsoft.EntityFrameworkCore.Abstractionsfloor by a newSecurityPolicyConsistencyTestsmethod — moving to EF Core 11 without moving the sentence fails the build.Verified (verify-the-guard)
ClaudeMdConsistencyTestspasses.Wording is yours to adjust — the test only pins the number.
🤖 Generated with Claude Code