Skip to content

chore: release main - #213

Open
github-actions[bot] wants to merge 1 commit into
mainfrom
release-please--branches--main
Open

github-actions[bot] wants to merge 1 commit into
mainfrom
release-please--branches--main

Conversation

@github-actions

@github-actions github-actions Bot commented Jul 22, 2026 •

Copy link
Copy Markdown
Contributor

🤖 I have created a release beep boop

launchdarkly-server-sdk-ai: 2.0.0

2.0.0 (2026-09-28)

⚠ 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)
  • 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-09-28)

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
Release Please version bump that publishes launchdarkly-server-sdk-ai 2.0.0 and launchdarkly-ai-optimizer 0.2.2, plus manifest, __version__, changelog, and provenance doc updates.

launchdarkly-server-sdk-ai 2.0.0 is a major release: agent graph traversal is topological (with scoped context and ready-check parity fixes), AI usage events get modelKey / modelVersion, and model_key / model_version are no longer exposed on public ModelConfig. LangChain and OpenAI provider packages now require launchdarkly-server-sdk-ai>=2.0.0.

launchdarkly-ai-optimizer 0.2.2 pins LD-API-Version on agent-optimization API calls (including an inlined pinned value).

Reviewed by Cursor Bugbot for commit 44f8a3b. Bugbot is set up for automated code reviews on this repo. Configure here.

@github-actions
github-actions Bot requested a review from a team as a code owner July 22, 2026 22:48
@github-actions
github-actions Bot force-pushed the release-please--branches--main branch from 198c1b2 to 173517f Compare August 4, 2026 14:32
@github-actions
github-actions Bot force-pushed the release-please--branches--main branch 2 times, most recently from 8f1e570 to ff1208c Compare September 2, 2026 14:12

@jsonbailey jsonbailey left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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

@github-actions
github-actions Bot force-pushed the release-please--branches--main branch from 2aa0601 to 44f8a3b Compare September 28, 2026 20:58
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant