Skip to content

chore: release main - #85

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 Sep 23, 2026 •

Copy link
Copy Markdown
Contributor

🤖 I have created a release beep boop

@launchdarkly/ai-server: 0.4.0

0.4.0 (2026-09-25)

Features

  • build: build the AI SDK like the other LaunchDarkly JS SDKs so CommonJS apps can load it (2/4) (#77) (2cda755)

Bug Fixes

  • judges: a judge's own config must not fail the run it grades (#17) (6e85cac)
@launchdarkly/ai-node: 0.3.0

0.3.0 (2026-09-25)

Features

  • build: build the AI SDK like the other LaunchDarkly JS SDKs so CommonJS apps can load it (2/4) (#77) (2cda755)
  • build: dual ESM/CommonJS output via tsup (d8e62e4)
@launchdarkly/ai-otel: 0.2.0

0.2.0 (2026-09-25)

Features

  • build: build the AI SDK like the other LaunchDarkly JS SDKs so CommonJS apps can load it (2/4) (#77) (2cda755)
  • build: dual ESM/CommonJS output via tsup (d8e62e4)
@launchdarkly/ai-claude-agents: 0.4.0

0.4.0 (2026-09-25)

Features

  • build: build the AI SDK like the other LaunchDarkly JS SDKs so CommonJS apps can load it (2/4) (#77) (2cda755)
@launchdarkly/ai-claude-messages: 0.4.0

0.4.0 (2026-09-25)

Features

  • build: build the AI SDK like the other LaunchDarkly JS SDKs so CommonJS apps can load it (2/4) (#77) (2cda755)

Bug Fixes

  • SEC-9507: authorize message-handler tools from the active variation (#90) (c16fe93)
@launchdarkly/ai-openai-agents: 0.4.0

0.4.0 (2026-09-25)

Features

  • build: build the AI SDK like the other LaunchDarkly JS SDKs so CommonJS apps can load it (2/4) (#77) (2cda755)
@launchdarkly/ai-openai-messages: 0.4.0

0.4.0 (2026-09-25)

Features

  • build: build the AI SDK like the other LaunchDarkly JS SDKs so CommonJS apps can load it (2/4) (#77) (2cda755)

Bug Fixes

  • SEC-9507: authorize message-handler tools from the active variation (#90) (c16fe93)
@launchdarkly/ai-langchain-agents: 0.4.0

0.4.0 (2026-09-25)

Features

  • build: build the AI SDK like the other LaunchDarkly JS SDKs so CommonJS apps can load it (2/4) (#77) (2cda755)
@launchdarkly/ai-langchain-messages: 0.4.0

0.4.0 (2026-09-25)

Features

  • build: build the AI SDK like the other LaunchDarkly JS SDKs so CommonJS apps can load it (2/4) (#77) (2cda755)

Bug Fixes

  • SEC-9507: authorize message-handler tools from the active variation (#90) (c16fe93)

This PR was generated with Release Please. See documentation.


Note

Overview
Release Please bumps nine @launchdarkly/ai-* packages (manifest, package.json, src/version.ts, and new CHANGELOG sections dated 2026-09-25). This PR does not change runtime code—it cuts the versions that ship the work already on main.

The release headline is dual ESM/CommonJS packaging (#77) so CommonJS Node apps can require the SDK like other LaunchDarkly JS SDKs; @launchdarkly/ai-node and @launchdarkly/ai-otel also call out tsup dual output in their notes. Provider packages (ai-claude-*, ai-openai-*, ai-langchain-*) pick up the same build refresh at 0.4.0; core @launchdarkly/ai-server goes to 0.4.0, @launchdarkly/ai-node to 0.3.0, @launchdarkly/ai-otel to 0.2.0.

@launchdarkly/ai-server 0.4.0 documents a judges fix: a judge’s own config must not fail the run it grades (#17). Claude, OpenAI, and LangChain message packages at 0.4.0 document SEC-9507: message-handler tools are authorized from the active variation (#90). Minor description string normalization (Unicode em dash) appears in ai-node and ai-otel package.json.

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

@github-actions
github-actions Bot force-pushed the release-please--branches--main branch 2 times, most recently from ae0b457 to 7b98e4a Compare September 25, 2026 19:08
@github-actions
github-actions Bot force-pushed the release-please--branches--main branch from 7b98e4a to 4fedf4e Compare September 25, 2026 21:57
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.

0 participants