Repository navigation
docs: match READMEs and AGENTS.md to the released versions - #303
Draft
jeffdupont wants to merge 1 commit into
Draft
jeffdupont wants to merge 1 commit into
jeffdupont wants to merge 1 commit into
Conversation
The versioning notes describe per-package 1.x versions, the LiteLLM READMEs lose the 0.x banner, and the client agents.md names shadow requests as the one experimental feature. launchdarkly-ai-python 1.x requires launchdarkly-ai-server>=1.0.0,<2, so the "does not pin" and "upgrade both" notes for Agent Skills and Evaluations from Code are replaced. AGENTS.md now says how a breaking experimental change ships at 1.x and adds a docs check for release PRs. Co-Authored-By: Claude Opus 5.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
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.
Several READMEs and agent guides still describe the SDK as it was before 1.0. This brings them in line with the released packages, and adds a release rule so it doesn't happen again.
What changed
packages/client/agents.mdnames shadow requests (launchdarkly_ai_server.experimental.shadow_requests) as the one experimental feature instead of "No feature is experimental now".AGENTS.mdandpackages/client/agents.mdno longer describe the 0.x!/ minor-bump rule. At 1.x a!forces a major release, so a breaking change to an experimental feature ships in a minor release with its feature scope. The API compatibility check skips experimental modules.README.mdno longer says every package is released at the same version. Packages are versioned on their own, all on major 1, with>=1.x,<2ranges on the core package.launchdarkly-ai-python: its README no longer says it "does not pin" the server. It requireslaunchdarkly-ai-server>=1.0.0,<2.packages/client/README.md: the "upgrade both" caveats are replaced. With pip's default upgrade strategy, upgradinglaunchdarkly-ai-pythonfrom 0.x brings the server to 1.x (tested with pip 26.2.2). The shadow-requests note, which needs server 1.1.0, is kept.Release rule
AGENTS.md("PR Titles and the Changelog") gains a rule: before a release PR merges, every README (root and every package),AGENTS.md, example, install line and maturity banner must match the version being released, with grep evidence in the release PR.Docs only.
🤖 Generated with Claude Code