chore(deps): bump openai from 4.104.0 to 6.21.0#117
chore(deps): bump openai from 4.104.0 to 6.21.0#117dependabot[bot] wants to merge 1 commit intomainfrom
Conversation
|
Codex usage limits have been reached for code reviews. Please check with the admins of this repo to increase the limits by adding credits. |
🤖 Augment PR SummarySummary: Updates the project’s OpenAI Node SDK dependency to a newer major release. Changes:
Technical Notes: This is a major-version upgrade, so runtime/API compatibility for existing OpenAI integration points should be validated via tests or a quick smoke run. 🤖 Was this summary useful? React with 👍 or 👎 |
package.json
Outdated
| "fast-xml-parser": "^4.5.3", | ||
| "@modelcontextprotocol/sdk": "1.25.3", | ||
| "openai": "^4.104.0", | ||
| "openai": "^6.21.0", |
There was a problem hiding this comment.
openai is being bumped across major versions (v4 → v6); consider double-checking that current usage patterns (e.g., new OpenAI({ apiKey }) and client.chat.completions.create(...) in the AgentOps scripts) still behave as expected under v6, and that any CI / smoke tests cover this path.
Severity: medium
🤖 Was this useful? React with 👍 or 👎, or 🚀 if it prevented an incident/outage.
Greptile SummaryThis PR bumps the Key observations:
Concern: The version mismatch between the PR description (6.21.0) and the actual installed version (^6.27.0) should be clarified to ensure the correct version was tested. Confidence Score: 3/5
Sequence DiagramsequenceDiagram
participant App as agentops/runner
participant Provider as provider.ts (callOpenAI)
participant SDK as openai@6.27.0 SDK
participant API as api.openai.com
App->>Provider: callLLM(config, prompt, context)
Provider->>SDK: new OpenAI({ apiKey })
Provider->>SDK: client.chat.completions.create({ model, messages, max_tokens })
Note over SDK: v6: uses native fetch<br/>(no node-fetch polyfill)
SDK->>API: POST /v1/chat/completions
API-->>SDK: { choices, usage }
SDK-->>Provider: ChatCompletion response
Provider-->>App: LLMResponse { content, usage }
|
package.json
Outdated
| "fast-xml-parser": "^4.5.3", | ||
| "@modelcontextprotocol/sdk": "1.25.3", | ||
| "openai": "^4.104.0", | ||
| "openai": "^6.21.0", |
There was a problem hiding this comment.
Major version bump from 4.x to 6.x - verify all OpenAI API calls still work. The basic client.chat.completions.create() usage in agentops/runner/lib/llm/provider.ts:123 and agentops/scripts/test-api-keys.ts:69 appears compatible with v6, but run the test suite to confirm.
Prompt To Fix With AI
This is a comment left during a code review.
Path: package.json
Line: 79:79
Comment:
Major version bump from 4.x to 6.x - verify all OpenAI API calls still work. The basic `client.chat.completions.create()` usage in `agentops/runner/lib/llm/provider.ts:123` and `agentops/scripts/test-api-keys.ts:69` appears compatible with v6, but run the test suite to confirm.
How can I resolve this? If you propose a fix, please make it concise.ba2220b to
1e14727
Compare
1e14727 to
1db59fe
Compare
package.json
Outdated
| "fast-xml-parser": "^4.5.3", | ||
| "@modelcontextprotocol/sdk": "1.25.3", | ||
| "openai": "^4.104.0", | ||
| "openai": "^6.25.0", |
There was a problem hiding this comment.
Version mismatch: PR title says 6.21.0, package.json specifies ^6.25.0
The PR description claims this bumps openai to 6.21.0, but package.json has been updated to ^6.25.0, which the lockfile resolves to 6.25.0. The caret range ^6.25.0 will automatically pull in any future 6.x.x releases on the next npm install, expanding the scope beyond what the PR describes.
If the intent is to pin to the validated version, consider using an exact version:
| "openai": "^6.25.0", | |
| "openai": "6.25.0", |
At minimum, confirm that 6.25.0 (the actual installed version) has been validated against the codebase, as it differs from the described target of 6.21.0.
Prompt To Fix With AI
This is a comment left during a code review.
Path: package.json
Line: 79
Comment:
**Version mismatch: PR title says `6.21.0`, package.json specifies `^6.25.0`**
The PR description claims this bumps `openai` to `6.21.0`, but `package.json` has been updated to `^6.25.0`, which the lockfile resolves to `6.25.0`. The caret range `^6.25.0` will automatically pull in any future `6.x.x` releases on the next `npm install`, expanding the scope beyond what the PR describes.
If the intent is to pin to the validated version, consider using an exact version:
```suggestion
"openai": "6.25.0",
```
At minimum, confirm that `6.25.0` (the actual installed version) has been validated against the codebase, as it differs from the described target of `6.21.0`.
How can I resolve this? If you propose a fix, please make it concise.
Additional Comments (2)
The OpenAI SDK v6 deprecates the Update to: The corresponding usage in Prompt To Fix With AIThis is a comment left during a code review.
Path: agentops/runner/lib/llm/provider.ts
Line: 126
Comment:
**`max_tokens` is deprecated in OpenAI SDK v6 — use `max_completion_tokens` instead**
The OpenAI SDK v6 deprecates the `max_tokens` parameter for `chat.completions.create()` in favour of `max_completion_tokens`. This will continue to work at runtime but may trigger deprecation warnings in strict TypeScript builds.
Update to:
```suggestion
max_completion_tokens: 4096,
```
The corresponding usage in `agentops/scripts/test-api-keys.ts:71` should also be updated.
How can I resolve this? If you propose a fix, please make it concise.
The OpenAI SDK v6 deprecates the Update to: Prompt To Fix With AIThis is a comment left during a code review.
Path: agentops/scripts/test-api-keys.ts
Line: 71
Comment:
**`max_tokens` is deprecated in OpenAI SDK v6 — use `max_completion_tokens` instead**
The OpenAI SDK v6 deprecates the `max_tokens` parameter for `chat.completions.create()` in favour of `max_completion_tokens`. This will continue to work at runtime but may trigger deprecation warnings in strict TypeScript builds.
Update to:
```suggestion
max_completion_tokens: 10,
```
How can I resolve this? If you propose a fix, please make it concise. |
2d0ec0b to
feec207
Compare
Bumps [openai](https://github.com/openai/openai-node) from 4.104.0 to 6.21.0. - [Release notes](https://github.com/openai/openai-node/releases) - [Changelog](https://github.com/openai/openai-node/blob/master/CHANGELOG.md) - [Commits](openai/openai-node@v4.104.0...v6.21.0) --- updated-dependencies: - dependency-name: openai dependency-version: 6.21.0 dependency-type: direct:production update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com>
feec207 to
f1542f4
Compare
Bumps openai from 4.104.0 to 6.21.0.
Release notes
Sourced from openai's releases.
... (truncated)
Changelog
Sourced from openai's changelog.
... (truncated)
Commits
2ffe3earelease: 6.21.08cfe66efeat(api): support for images in batch api66188cdrelease: 6.20.064bc0b4feat(api): skills and hosted shellfb5a9berelease: 6.19.01b19311feat(api): responses context_managementc205a79codegen metadata69d2b01release: 6.18.0bf5a096chore(internal): fix pagination internals not accepting option promisesaa24028fix(client): avoid removing abort listener too earlyMaintainer changes
This version was pushed to npm by apcha-oai, a new releaser for openai since your current version.
Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)