docs(readme): announce /v1 GA and name the baseline version - #798
Merged
Conversation
The README already claimed GA but never said since WHICH release, while docs/api.md and SECURITY.md both name 1.5.0. A reader could not tell whether GA had actually shipped or was aspirational, nor which tag to pin against. - Adds a release badge and a one-line announcement above the nav. - Names v1.5.0 in the stability callout and states that it is the compatibility baseline every later release is audited against, which is the fact a consumer actually needs. Verified: badge renders v1.5.0, and both release links return 200. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
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.
The README claimed GA but never said since which release — while
docs/api.mdandSECURITY.mdboth name 1.5.0. A reader couldn't tell whether GA had actually shipped or was aspirational, nor which tag to pin against.Changes
A release badge and a one-line announcement above the nav:
Names the version in the stability callout, and adds the fact a consumer actually needs — that the tag is the compatibility baseline later releases are audited against:
The beta enumeration is untouched.
Verification
v1.5.0(fetched the shield, not assumed)releases/tag/v1.5.0→ 200,releases/latest→ 200Related
Companion to #797, which moves the compatibility-gate audit baseline from the pre-release freeze anchor to
v1.5.0— the same fact, stated where the gate's operator will look for it.🤖 Generated with Claude Code