docs: no version-sensitive claims in the README - #267
Open
thedavidmeister wants to merge 1 commit into
Open
thedavidmeister wants to merge 1 commit into
thedavidmeister wants to merge 1 commit into
Conversation
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
|
Warning Review limit reachedNext included review available in 51 seconds. View limit detailsLimit details: You’ve used the included review currently available. You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository. Review configuration: ⚙️ Run configurationConfiguration used: Organization UI Review profile: ASSERTIVE Plan: Advanced Run ID: 📒 Files selected for processing (1)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
This branch has not been deployed
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
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.
What
The README named soldeer versions (
0.1.5,0.1.6) and five tags to mark where the library/deploy split falls.Owner ruling 2026-09-21: docs carry no version-sensitive claims — they rot as soon as the next release lands, and
nothing keeps them in step. The paragraph now says the same thing without a version or tag in it: pre-split releases
carried the concrete and the deploy pins, and the Protofire reports audit those rather than the current tree.
The audit issue that paragraph came from (#111) stays closed; this is the ruling applied to its wording.
QA
grep -nE '0\.1\.[0-9]|sol-v|v0\.1\.' README.mdreturns nothing, andforge testis unchanged at 78 passing.CLAUDE.md, the NatSpec undersrc/, and.github/carry noversion or tag claims;
audit/mutation-test-scans.jsonand.audit/do, and stay, because they are records of arun at a commit rather than documentation.
🤖 Generated with Claude Code