test: pin SECURITY.md's supported-versions table to the shipped version - #19
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: a release that bumps the version and forgets the table leaves the policy pointing a reporter at a line that no longer receives fixes. The sibling repository (CodoMetis.ValueRanges) shipped 6.2.0 with the table still saying 6.1.x; here it happens to be right. SecurityPolicyConsistencyTests 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. Verified: passes against the current table (5.0.x, shipping 5.0.3); fails with the table changed to 5.1.x; fails with the unsupported row changed to '< 4.0'; passes again once restored. ClaudeMdConsistencyTests passes with the new table row. 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, so it is exactly the line a version bump forgets — the sibling repository shipped 6.2.0 with its table still saying 6.1.x. Here it happens to be right (5.0.x, shipping 5.0.3). "Prefer a test to a convention."What
SecurityPolicyConsistencyTestsasserts that the single| x.y.x | ✅ |row is the shipped major.minor, and that the| < x.y | ❌ |row meets it at the same minor (so no range is left described by neither). One row added to the convention-tests table in CLAUDE.md.Verified (verify-the-guard)
5.1.x("SECURITY.md lists 5.1.x as the supported line, but Directory.Build.props ships 5.0.3").< 4.0.ClaudeMdConsistencyTestspasses with the new table row.🤖 Generated with Claude Code