[github-actions]

🤖 I have created a release beep boop

launchdarkly-server-sdk-ai: 2.0.0

2.0.0 (2026-10-27)

⚠ BREAKING CHANGES

• Make AgentGraph traversal topological (#214)

Features

• server-ai: stamp modelKey and modelVersion on AI usage events (AIC-2851) (#208) (66588f0)

Bug Fixes

• Make AgentGraph traversal topological (#214) (d1828ab)
• Require launchdarkly-server-sdk 9.18.3 or newer (#217) (2039275)
• server-ai: stop exposing model_key/model_version on ModelConfig (5f8b5f8)
• use == 0 for agent graph ready-check parity (3f801da)
• use topological order and scoped context for agent graph traversal (d76b2d9)

ldai_optimizer: 0.2.2

0.2.2 (2026-10-27)

Bug Fixes

• optimization: inline the pinned LD-API-Version value (fa7b6c3)
• optimization: pin LD-API-Version on agent-optimization API calls (AIC-3484) (#216) (36627c7)

---

This PR was generated with Release Please. See documentation.

---

Note

Overview
This is a Release Please cut that bumps published package versions and syncs release metadata—no new runtime logic in the diff itself.

launchdarkly-server-sdk-ai 2.0.0 (major): manifest, pyproject.toml, __version__, changelog, and provenance docs move from 1.2.0 → 2.0.0. The new changelog section documents the shipped 2.0 line: breaking AgentGraph traversal in topological order with scoped context; AI usage events get modelKey / modelVersion; ModelConfig no longer exposes model_key / model_version; and a floor of launchdarkly-server-sdk>=9.18.3.

launchdarkly-ai-optimizer 0.2.2: version and changelog for pinning LD-API-Version on agent-optimization API calls (plus provenance VERSION).

Provider packages: LangChain and OpenAI provider pyproject.toml dependencies now require launchdarkly-server-sdk-ai>=2.0.0 (was >=1.2.0).

.release-please-manifest.json reflects server-ai 2.0.0 and optimization 0.2.2.

^{Reviewed by Cursor Bugbot for commit e4ea27f. Bugbot is set up for automated code reviews on this repo. Configure here.}

[jsonbailey]

@mattrmc1 I wanted to verify you intentionally meant for this to be a v2.0 release before approving.

[andrewklatzke]

This should definitely not be version 2.0 Realizing this is not the new SDKS - this may be a breaking change that requires it?