chore: release main #982
chore: release main #982
Conversation
![cursor[bot]](https://avatars.githubusercontent.com/in/1210556?s=60&v=4){kind=small}
There was a problem hiding this comment.
Bug: Peer Dependency Mismatch for Server-SDK-AI 0.14.0
The peerDependencies for @launchdarkly/server-sdk-ai is still set to "^0.12.2" but should be "^0.14.0" according to the changelog. The changelog states "peerDependencies: @launchdarkly/server-sdk-ai bumped from ^0.12.2 to ^0.14.0" but this change was not applied. This is critical because server-sdk-ai 0.14.0 contains breaking changes, and the provider package was developed against 0.14.0 (as shown in devDependencies).
packages/ai-providers/server-ai-vercel/package.json#L51-L52
js-core/packages/ai-providers/server-ai-vercel/package.json
Lines 51 to 52 in 13694a2
Bug: Peer Dependency Version Mismatch Causes Breaking Changes
The peerDependencies for @launchdarkly/server-sdk-ai is still set to "^0.12.2" but should be "^0.14.0" according to the changelog. The changelog states "peerDependencies: @launchdarkly/server-sdk-ai bumped from ^0.12.2 to ^0.14.0" but this change was not applied. This is critical because server-sdk-ai 0.14.0 contains breaking changes, and the provider package was developed against 0.14.0 (as shown in devDependencies).
packages/ai-providers/server-ai-openai/package.json#L47-L48
js-core/packages/ai-providers/server-ai-openai/package.json
Lines 47 to 48 in 13694a2
Bug: Broken peerDependency Version Mismatch for SDK AI
The peerDependencies for @launchdarkly/server-sdk-ai is still set to "^0.12.2" but should be "^0.14.0" according to the changelog. The changelog states "peerDependencies: @launchdarkly/server-sdk-ai bumped from ^0.12.2 to ^0.14.0" but this change was not applied. This is critical because server-sdk-ai 0.14.0 contains breaking changes, and the provider package was developed against 0.14.0 (as shown in devDependencies).
packages/ai-providers/server-ai-langchain/package.json#L47-L48
js-core/packages/ai-providers/server-ai-langchain/package.json
Lines 47 to 48 in 13694a2
github-actions
bot
force-pushed
the
release-please--branches--main
branch
2 times, most recently
from
e37a980 to
e61ec94
Compare
| "devDependencies": { | ||
| "@langchain/core": "^0.3.0", | ||
| "@launchdarkly/server-sdk-ai": "^0.13.0", | ||
| "@launchdarkly/server-sdk-ai": "^0.14.0", |
There was a problem hiding this comment.
Bug: Dependency version mismatch between dev and peer ranges
The devDependencies for @launchdarkly/server-sdk-ai was updated to ^0.14.0, but the peerDependencies still specifies ^0.12.2. According to the CHANGELOG, peerDependencies should also have been bumped to ^0.14.0. This mismatch will cause version conflicts where the package requires ^0.12.2 as a peer dependency but uses ^0.14.0 for development, potentially leading to runtime errors when consumers install incompatible versions.
| "devDependencies": { | ||
| "@launchdarkly/js-server-sdk-common": "2.16.2", | ||
| "@launchdarkly/server-sdk-ai": "^0.13.0", | ||
| "@launchdarkly/server-sdk-ai": "^0.14.0", |
There was a problem hiding this comment.
Bug: Dependency mismatch: dev vs peer versions cause conflicts
The devDependencies for @launchdarkly/server-sdk-ai was updated to ^0.14.0, but the peerDependencies still specifies ^0.12.2. According to the CHANGELOG, peerDependencies should also have been bumped to ^0.14.0. This mismatch will cause version conflicts where the package requires ^0.12.2 as a peer dependency but uses ^0.14.0 for development, potentially leading to runtime errors when consumers install incompatible versions.
| "@ai-sdk/mistral": "^2.0.0", | ||
| "@ai-sdk/openai": "^2.0.0", | ||
| "@launchdarkly/server-sdk-ai": "^0.13.0", | ||
| "@launchdarkly/server-sdk-ai": "^0.14.0", |
There was a problem hiding this comment.
Bug: Peer Dependency Mismatch After Version Bump
The devDependencies for @launchdarkly/server-sdk-ai was updated to ^0.14.0, but the peerDependencies still specifies ^0.12.2. According to the CHANGELOG, peerDependencies should also have been bumped to ^0.14.0. This mismatch will cause version conflicts where the package requires ^0.12.2 as a peer dependency but uses ^0.14.0 for development, potentially leading to runtime errors when consumers install incompatible versions.
github-actions
bot
force-pushed
the
release-please--branches--main
branch
from
e61ec94 to
b16fda6
Compare
github-actions
bot
force-pushed
the
release-please--branches--main
branch
from
b16fda6 to
6cd5222
Compare
🤖 I have created a release beep boop
server-sdk-ai: 0.14.0
0.14.0 (2025-11-05)
⚠ BREAKING CHANGES
Features
Bug Fixes
server-sdk-ai-langchain: 0.3.0
0.3.0 (2025-11-05)
⚠ BREAKING CHANGES
Features
Dependencies
server-sdk-ai-openai: 0.3.0
0.3.0 (2025-11-05)
⚠ BREAKING CHANGES
Features
Dependencies
server-sdk-ai-vercel: 0.3.0
0.3.0 (2025-11-05)
⚠ BREAKING CHANGES
Features
Dependencies
This PR was generated with Release Please. See documentation.
Note
Release server-ai 0.14.0 (judge evaluations, API renames/defaults) and bump LangChain/OpenAI/Vercel providers to 0.3.0 with structured output support; update examples and manifest accordingly.
packages/sdk/server-ai) —0.14.0createJudge,judgeConfig,trackEvalScores); chat auto-evaluations.enabledin AI Config defaults; rename several AI Config types.0.3.0packages/ai-providers/server-ai-langchain: add structured output support; deps peer-bumped to@launchdarkly/server-sdk-ai@^0.14.0.packages/ai-providers/server-ai-openai: add structured output support; deps peer-bumped to@launchdarkly/server-sdk-ai@^0.14.0.packages/ai-providers/server-ai-vercel: add structured output support; deps peer-bumped to@launchdarkly/server-sdk-ai@^0.14.0.@launchdarkly/[email protected]..release-please-manifest.json.Written by Cursor Bugbot for commit 6cd5222. This will update automatically on new commits. Configure here.