-
Notifications
You must be signed in to change notification settings - Fork 30
chore: release main #982
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
chore: release main #982
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,6 +1,6 @@ | ||
| { | ||
| "name": "@launchdarkly/server-sdk-ai-openai", | ||
| "version": "0.2.0", | ||
| "version": "0.3.0", | ||
| "description": "LaunchDarkly AI SDK OpenAI Provider for Server-Side JavaScript", | ||
| "homepage": "https://github.com/launchdarkly/js-core/tree/main/packages/ai-providers/server-ai-openai", | ||
| "repository": { | ||
|
|
@@ -28,7 +28,7 @@ | |
| "license": "Apache-2.0", | ||
| "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. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Bug: Dependency mismatch: dev vs peer versions cause conflictsThe 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. |
||
| "@trivago/prettier-plugin-sort-imports": "^4.1.1", | ||
| "@types/jest": "^29.5.3", | ||
| "@typescript-eslint/eslint-plugin": "^6.20.0", | ||
|
|
||
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,6 +1,6 @@ | ||
| { | ||
| "name": "@launchdarkly/server-sdk-ai-vercel", | ||
| "version": "0.2.0", | ||
| "version": "0.3.0", | ||
| "description": "LaunchDarkly AI SDK Vercel Provider for Server-Side JavaScript", | ||
| "homepage": "https://github.com/launchdarkly/js-core/tree/main/packages/ai-providers/server-ai-vercel", | ||
| "repository": { | ||
|
|
@@ -32,7 +32,7 @@ | |
| "@ai-sdk/google": "^2.0.0", | ||
| "@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. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Bug: Peer Dependency Mismatch After Version BumpThe 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. |
||
| "@trivago/prettier-plugin-sort-imports": "^4.1.1", | ||
| "@types/jest": "^29.5.3", | ||
| "@typescript-eslint/eslint-plugin": "^6.20.0", | ||
|
|
||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
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.