Skip to content

chore: release main - #131

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 Oct 9, 2026 •

Copy link
Copy Markdown
Contributor

🤖 I have created a release beep boop

@launchdarkly/ai-claude-agents: 0.5.0

0.5.0 (2026-10-23)

⚠ BREAKING CHANGES

  • forward the same model.parameters keys as the Python SDK (#118)
  • claude-agents: accept trusted cwd and settingSources options, and load no host settings by default (#135)
  • client: the client no longer loads .env. Add import 'dotenv/config' to your entrypoint (and install dotenv) if you relied on it.

Features

  • AIC-3623: evals from code (#143) (dc74b48)
  • claude-agents: accept trusted cwd and settingSources options, and load no host settings by default (#135) (6acd53d)

Bug Fixes

  • AIC-3571: visit every child before its parent in reverseTraverse (#147) (a17a2ce)
  • AIC-3577: send object tool results to the model as JSON (#146) (be41d87)
  • claude-agents: fail the run when the CLI reports an API error as success (#138) (4637958)
  • client: stop loading dotenv from library code (#69) (fea34f3)
  • forward the same model.parameters keys as the Python SDK (#118) (f7883ce)
  • give native graph spans their LaunchDarkly identity (#101) (4d97cfa)

Dependencies

  • The following workspace dependencies were updated
    • dependencies
      • @launchdarkly/ai-server bumped from ^0.4.0 to ^0.5.0
@launchdarkly/ai-claude-messages: 0.5.0

0.5.0 (2026-10-23)

⚠ BREAKING CHANGES

  • forward the same model.parameters keys as the Python SDK (#118)
  • client: the client no longer loads .env. Add import 'dotenv/config' to your entrypoint (and install dotenv) if you relied on it.

Features

Bug Fixes

  • AIC-3577: send object tool results to the model as JSON (#146) (be41d87)
  • client: stop loading dotenv from library code (#69) (fea34f3)
  • forward the same model.parameters keys as the Python SDK (#118) (f7883ce)

Dependencies

  • The following workspace dependencies were updated
    • dependencies
      • @launchdarkly/ai-server bumped from ^0.4.0 to ^0.5.0
@launchdarkly/ai-langchain-agents: 0.5.0

0.5.0 (2026-10-23)

⚠ BREAKING CHANGES

  • forward the same model.parameters keys as the Python SDK (#118)
  • client: the client no longer loads .env. Add import 'dotenv/config' to your entrypoint (and install dotenv) if you relied on it.

Features

Bug Fixes

  • AIC-3577: send object tool results to the model as JSON (#146) (be41d87)
  • client: stop loading dotenv from library code (#69) (fea34f3)
  • forward the same model.parameters keys as the Python SDK (#118) (f7883ce)
  • give native graph spans their LaunchDarkly identity (#101) (4d97cfa)

Dependencies

  • The following workspace dependencies were updated
    • dependencies
      • @launchdarkly/ai-server bumped from ^0.4.0 to ^0.5.0
@launchdarkly/ai-langchain-messages: 0.5.0

0.5.0 (2026-10-23)

⚠ BREAKING CHANGES

  • forward the same model.parameters keys as the Python SDK (#118)
  • client: the client no longer loads .env. Add import 'dotenv/config' to your entrypoint (and install dotenv) if you relied on it.

Features

Bug Fixes

  • AIC-3577: send object tool results to the model as JSON (#146) (be41d87)
  • client: stop loading dotenv from library code (#69) (fea34f3)
  • forward the same model.parameters keys as the Python SDK (#118) (f7883ce)

Dependencies

  • The following workspace dependencies were updated
    • dependencies
      • @launchdarkly/ai-server bumped from ^0.4.0 to ^0.5.0
@launchdarkly/ai-litellm-agents: 0.2.0

0.2.0 (2026-10-23)

⚠ BREAKING CHANGES

  • forward the same model.parameters keys as the Python SDK (#118)

Features

  • add LiteLLM messages and agents integrations (#75) (127f156)

Bug Fixes

  • forward the same model.parameters keys as the Python SDK (#118) (f7883ce)

Dependencies

  • The following workspace dependencies were updated
    • dependencies
      • @launchdarkly/ai-server bumped from ^0.4.0 to ^0.5.0
@launchdarkly/ai-litellm-messages: 0.2.0

0.2.0 (2026-10-23)

⚠ BREAKING CHANGES

  • forward the same model.parameters keys as the Python SDK (#118)

Features

  • add LiteLLM messages and agents integrations (#75) (127f156)

Bug Fixes

  • forward the same model.parameters keys as the Python SDK (#118) (f7883ce)

Dependencies

  • The following workspace dependencies were updated
    • dependencies
      • @launchdarkly/ai-server bumped from ^0.4.0 to ^0.5.0
@launchdarkly/ai-node: 0.4.0

0.4.0 (2026-10-23)

⚠ BREAKING CHANGES

  • client: the client no longer loads .env. Add import 'dotenv/config' to your entrypoint (and install dotenv) if you relied on it.

Bug Fixes

  • client: stop loading dotenv from library code (#69) (fea34f3)

Dependencies

  • The following workspace dependencies were updated
    • dependencies
      • @launchdarkly/ai-server bumped from ^0.4.0 to ^0.5.0
@launchdarkly/ai-openai-agents: 0.5.0

0.5.0 (2026-10-23)

⚠ BREAKING CHANGES

  • forward the same model.parameters keys as the Python SDK (#118)
  • client: the client no longer loads .env. Add import 'dotenv/config' to your entrypoint (and install dotenv) if you relied on it.

Features

Bug Fixes

  • AIC-3571: visit every child before its parent in reverseTraverse (#147) (a17a2ce)
  • AIC-3577: send object tool results to the model as JSON (#146) (be41d87)
  • AIC-3586: propagate tool handler errors instead of sending them to the model (#139) (1f31e85)
  • client: stop loading dotenv from library code (#69) (fea34f3)
  • forward the same model.parameters keys as the Python SDK (#118) (f7883ce)
  • give native graph spans their LaunchDarkly identity (#101) (4d97cfa)

Dependencies

  • The following workspace dependencies were updated
    • dependencies
      • @launchdarkly/ai-server bumped from ^0.4.0 to ^0.5.0
@launchdarkly/ai-openai-messages: 0.5.0

0.5.0 (2026-10-23)

⚠ BREAKING CHANGES

  • forward the same model.parameters keys as the Python SDK (#118)
  • client: the client no longer loads .env. Add import 'dotenv/config' to your entrypoint (and install dotenv) if you relied on it.

Features

Bug Fixes

  • AIC-3577: send object tool results to the model as JSON (#146) (be41d87)
  • client: stop loading dotenv from library code (#69) (fea34f3)
  • forward the same model.parameters keys as the Python SDK (#118) (f7883ce)

Dependencies

  • The following workspace dependencies were updated
    • dependencies
      • @launchdarkly/ai-server bumped from ^0.4.0 to ^0.5.0
@launchdarkly/ai-otel: 0.3.0

0.3.0 (2026-10-23)

⚠ BREAKING CHANGES

  • client: the client no longer loads .env. Add import 'dotenv/config' to your entrypoint (and install dotenv) if you relied on it.

Bug Fixes

  • client: stop loading dotenv from library code (#69) (fea34f3)
@launchdarkly/ai-server: 0.5.0

0.5.0 (2026-10-23)

⚠ BREAKING CHANGES

  • forward the same model.parameters keys as the Python SDK (#118)
  • client: the client no longer loads .env. Add import 'dotenv/config' to your entrypoint (and install dotenv) if you relied on it.

Experimental

  • evaluations: hash eventId and contentHash as RFC 8785 canonical JSON, the same in every SDK (c971649)
  • evaluations: Set JSON as standard for output to pass to judge (#152) (330da44)
  • skills: Correct the HTTP 403 advice now that server-side FDv2 is available to every account (#141) (5b7b732)

Features

Bug Fixes

  • AIC-3541: accept a node-server-sdk client in initClient() without a cast (#128) (5819449)
  • AIC-3570: re-resolve graph flags on every invoke and stream (#145) (ce4f72e)
  • AIC-3571: visit every child before its parent in reverseTraverse (#147) (a17a2ce)
  • AIC-3576: record deferred judge scores under the evaluated config (#148) (d9fbee6)
  • AIC-3577: send object tool results to the model as JSON (#146) (be41d87)
  • AIC-3596: point the missing-OTel warning and docs at @launchdarkly/ai-otel (#144) (9b5f32e)
  • client: show a judge an output of 0, false, {} or [] (c971649)
  • client: stop loading dotenv from library code (#69) (fea34f3)
  • forward the same model.parameters keys as the Python SDK (#118) (f7883ce)
  • give native graph spans their LaunchDarkly identity (#101) (4d97cfa)
  • judges: a judge config's outputFormat must not reach the provider (#56) (8c6f4d2)
@launchdarkly/ai-typesafe: 0.2.0

0.2.0 (2026-10-23)

⚠ BREAKING CHANGES

  • forward the same model.parameters keys as the Python SDK (#118)

Features

Bug Fixes

  • forward the same model.parameters keys as the Python SDK (#118) (f7883ce)

Dependencies

  • The following workspace dependencies were updated
    • dependencies
      • @launchdarkly/ai-server bumped from ^0.4.0 to ^0.5.0
@launchdarkly/ai-vercel-agents: 0.3.0

0.3.0 (2026-10-23)

⚠ BREAKING CHANGES

  • forward the same model.parameters keys as the Python SDK (#118)

Features

Bug Fixes

  • forward the same model.parameters keys as the Python SDK (#118) (f7883ce)
  • give native graph spans their LaunchDarkly identity (#101) (4d97cfa)

Dependencies

  • The following workspace dependencies were updated
    • dependencies
      • @launchdarkly/ai-server bumped from ^0.4.0 to ^0.5.0
@launchdarkly/ai-vercel-messages: 0.3.0

0.3.0 (2026-10-23)

⚠ BREAKING CHANGES

  • forward the same model.parameters keys as the Python SDK (#118)

Features

Bug Fixes

  • forward the same model.parameters keys as the Python SDK (#118) (f7883ce)

Dependencies

  • The following workspace dependencies were updated
    • dependencies
      • @launchdarkly/ai-server bumped from ^0.4.0 to ^0.5.0

This PR was generated with Release Please. See documentation.

@github-actions
github-actions Bot force-pushed the release-please--branches--main branch 2 times, most recently from 9c1b6c8 to 82c576c Compare October 12, 2026 23:24

@jeffdupont jeffdupont 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.

Holding this release:

  1. Main CI is red at the commit this would ship. Run 38321949426 on 4d97cfa4 fails skills.test.ts:418 (root exports snapshot) and ai-server api:check, both from #101 adding makeGraphTrackData. #137 fixes it and is approved and green. Merge #137, then let release-please regenerate this PR.
  2. Vercel packages can't publish. In the last release run (37987586310), release-vercel-messages and release-vercel-agents failed with npm error 403 ... OIDC permission denied. npm still shows only 0.0.0 for both, so 0.2.0 never shipped and 0.2.1 will likely hit the same 403. npm trusted publishing needs setting up for both packages first.

The version bumps themselves look right: all patch releases, nothing to 1.0, ai-otel unchanged.

@github-actions
github-actions Bot force-pushed the release-please--branches--main branch from 82c576c to 03512c4 Compare October 15, 2026 19:45

@jeffdupont jeffdupont 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.

Re-checked at the regenerated head. One blocker cleared, one left.

Cleared: main CI is green now that #137 is merged (CI run on c4691cdc). The bumps are still all patches, nothing to 1.0, and ai-otel is unchanged.

Still blocking: @launchdarkly/ai-vercel-messages and @launchdarkly/ai-vercel-agents have never published. npm shows only 0.0.0 / 0.0.0-stage for both. The last release run that tried to publish them (37987586310, 9 Oct) failed with npm error 403 ... OIDC permission denied. The runs since succeeded only on days with nothing to publish. Unless npm trusted publishing has been configured for both packages, 0.2.1 will hit the same 403 and the release will go out without the two Vercel packages. Can someone with npm org access confirm the trusted-publisher setup for both packages before merging?

@github-actions
github-actions Bot force-pushed the release-please--branches--main branch 4 times, most recently from e6952e7 to 451de04 Compare October 21, 2026 14:10
@github-actions
github-actions Bot force-pushed the release-please--branches--main branch 6 times, most recently from 762f085 to 3c3d76c Compare October 23, 2026 13:21
@github-actions
github-actions Bot force-pushed the release-please--branches--main branch from 3c3d76c to 4fbf2d2 Compare October 23, 2026 15:12
jeffdupont added a commit that referenced this pull request Oct 23, 2026
…ic API (#154)

Step 5 of AIC-3500 for JS, part 2: CI fails on a breaking change to the
public API unless the PR declares it (checks 2 and 3, TESTING.md §5.2).
The Python version is python-ai-sdk#196. Stacked on #153.

**What changes**
- `scripts/api-breaking.mjs` (plain Node, no dependencies, like
`api-surface.mjs`) compares each non-experimental report declaration by
declaration.
- A removed or changed declaration is breaking, and so is a report
present at base but gone at head. An added declaration is not.
Comment-only changes such as doc comments or `@deprecated` don't count.
- TypeScript's tool can't tell a compatible change from a breaking one
(A.16), so an added optional member is flagged and passes with the
`api-compatible` label.
- `pr` mode passes when the title has `!` (same regex as Python) or the
PR has `api-compatible`.
- `release` mode runs on the release-please PR. For each package whose
version changes, it compares against the package's last release tag
(`<component>-<version>`, from `release-please-config.json`). A breaking
change needs a major bump, or a minor one before 1.0.
- `.github/workflows/api-compatibility.yml`: same triggers as Python's
(`edited`, `labeled` and `unlabeled` re-run it) and the same release-PR
detection (`release-please--branches--main`). The title goes through
`env`, not shell interpolation.
- 24 `node:test` tests (`yarn test:api-breaking`, run in CI) in a
throwaway git repo.

**Verified**
- All repo checks pass, plus `yarn test:api-breaking` (24 passed).
- A real `pr` run against part 1 and against `main` says "No breaking
changes to the public API."
- Changing `input?:` to `input:` in the openai-messages report fails and
shows the old and new lines; with a `feat!:` title it passes.
- `release` mode, with the manifest edited temporarily: client 0.4.0 →
0.4.1 fails (and passes with `api-compatible`), and 0.4.0 → 0.5.0
passes.
- Five `ai-server` declarations have changed since
`@launchdarkly/ai-server-0.4.0`. The open release PR #131 bumps the
client to 0.5.0, which passes. I didn't run the script against that
branch.

**Known limit:** the provider packages have no report at their last
release tag, so check 3 skips them, with a message, until their next
release.

🤖 Generated with [Claude Code](https://claude.com/claude-code)

<!-- CURSOR_SUMMARY -->
---

> [!NOTE]
> **Overview**
> Adds **API compatibility enforcement** so CI blocks undeclared
breaking changes to committed API Extractor reports
(`packages/*/etc/*.api.md`).
> 
> A new `scripts/api-breaking.mjs` compares stable (non-experimental)
reports declaration-by-declaration: removals, signature/type changes,
and deleted reports count as breaking; additions do not; comment-only
edits are ignored. **PR mode** fails unless the title uses conventional
`!` (`feat!:`, etc.) or the PR has the `api-compatible` label. **Release
mode** (release-please branch) compares each bumped package to its last
release tag and requires a major bump (or pre-1.0 minor) when breaking
diffs exist, with the same label escape hatch.
> 
> A dedicated `.github/workflows/api-compatibility.yml` runs those
checks on PR events (including title/label edits). Main `ci.yml` runs
`yarn test:api-breaking` (24 fixture git tests). `AGENTS.md` documents
the policy for contributors.
> 
> <sup>Reviewed by [Cursor Bugbot](https://cursor.com/bugbot) for commit
08fbcc1. Bugbot is set up for automated
code reviews on this repo. Configure
[here](https://www.cursor.com/dashboard/bugbot).</sup>
<!-- /CURSOR_SUMMARY -->

---------

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
@github-actions
github-actions Bot force-pushed the release-please--branches--main branch 4 times, most recently from d6ec0d8 to 7673ab2 Compare October 23, 2026 16:25
@github-actions
github-actions Bot force-pushed the release-please--branches--main branch 2 times, most recently from d8479e7 to ab9cd9a Compare October 23, 2026 18:56
@github-actions
github-actions Bot force-pushed the release-please--branches--main branch from ab9cd9a to 273e545 Compare October 23, 2026 19:38
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