docs: keep README release-agnostic - #88
Merged
Merged
Conversation
thossullivan
marked this pull request as ready for review
August 18, 2026 19:01
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.
Summary
@v0pinning guidance while removing historical version referencesWhy
The README should explain the current product and its enduring operating contract. Version history ages quickly and is better maintained in GitHub Releases.
Impact
Documentation only. There are no CLI, Action, schema, feed, or runtime changes, and
package.jsonremains at 0.5.0. After merge, 0.5.1 can be released separately so npm carries the cleaned README.Validation
npm testgit diff --check