test: pin SECURITY.md's supported-versions table to the shipped version - #6
Merged
Merged
Conversation
SECURITY.md promises fixes for "the latest released minor version" and
tabulates which line that is. Nothing tied the table to
Directory.Build.props, and 6.2.0 shipped with it still saying 6.1.x — a
reporter on 6.2 read a policy that told them their version was unsupported.
SecurityPolicyConventionTests asserts that the single '| x.y.x | ✅ |' row
is the shipped major.minor and that the '| < x.y | ❌ |' row meets it at
the same minor. The table is corrected to 6.2.x / < 6.2 in the same change.
Verified: the new test failed against the stale table ("SECURITY.md lists
6.1.x as the supported line, but Directory.Build.props ships 6.2.0") and
passes once the table is corrected; the conventions suite is green.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
This was referenced Aug 16, 2026
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.
Why
SECURITY.md promises fixes for "the latest released minor version" and tabulates which line that is. Nothing tied the table to
Directory.Build.props, and 6.2.0 shipped with it still saying 6.1.x — a reporter on 6.2 read a policy telling them their version was unsupported. "Prefer a test to a convention."What
SecurityPolicyConventionTestsasserts that the single| x.y.x | ✅ |row is the shipped major.minor, and that the| < x.y | ❌ |row meets it at the same minor.6.2.x/< 6.2.Mirror of EFCore.ComplexIndexes#19, where the table happened to be right and the defect had to be seeded.
Verified (verify-the-guard)
main("SECURITY.md lists 6.1.x as the supported line, but Directory.Build.props ships 6.2.0").🤖 Generated with Claude Code