chore(deps): bump ws from 8.20.0 to 8.20.1#807
Conversation
Bumps [ws](https://github.com/websockets/ws) from 8.20.0 to 8.20.1. - [Release notes](https://github.com/websockets/ws/releases) - [Commits](websockets/ws@8.20.0...8.20.1) --- updated-dependencies: - dependency-name: ws dependency-version: 8.20.1 dependency-type: indirect ... Signed-off-by: dependabot[bot] <support@github.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
There was a problem hiding this comment.
LGTM — dependabot security patch bump of ws from 8.20.0 to 8.20.1 (uninitialized memory disclosure fix), lockfile-only change.
Extended reasoning...
Overview
This Dependabot PR bumps the transitive dependency ws from 8.20.0 to 8.20.1. The only file changed is pnpm-lock.yaml. ws is not a direct dependency of this repo — it appears only as an optional/transitive peer of openai, @langchain/openai, autoevals, etc.
Security risks
None introduced by this PR; the upstream release is itself a security fix for an uninitialized memory disclosure in websocket.close() when a TypedArray is passed as the reason. This codebase doesn't appear to use ws directly, so the practical exposure is minimal, but bumping is still strictly an improvement.
Level of scrutiny
Minimal — this is a patch-level lockfile-only bump generated by Dependabot. No source code is modified, no API surface changes, and the upstream changelog is constrained to a single security fix and CI-only changes.
Other factors
There is one residual reference to ws@8.20.0 (made optional) and a new openai@6.22.0(ws@8.20.0) snapshot kept around because of a remaining openai: 6.22.0(ws@8.20.0) consumer in langsmith — this is normal pnpm lockfile resolution behavior and not a concern.
Bumps ws from 8.20.0 to 8.20.1.
Release notes
Sourced from ws's releases.
Commits
5d9b316[dist] 8.20.1c0327ec[security] Fix uninitialized memory disclosure inwebsocket.close()ce2a3d6[ci] Test on node 2658e45b8[ci] Do not test on node 255f26c24[ci] Run the lint step on node 24Dependabot 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)You can disable automated security fix PRs for this repo from the Security Alerts page.