Update ws package version to 7.5.11 - #67408
Conversation
|
Thanks for your PR, @birarroshan. Someone from the team will get assigned to your PR shortly and we'll get it reviewed. |
There was a problem hiding this comment.
Pull request overview
This PR updates the TypeScript SignalR client’s ws dependency to a non-vulnerable patch level to address the reported CVE (issue #67407).
Changes:
- Bump
wsdependency range in@microsoft/signalrfrom^7.5.10to^7.5.11.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
@dotnet-policy-service agree |
|
Will merge once branches re-open for August (next week) |
|
Thanks @wtgodbe for accepting change. What is tentative release date? |
August 11 |
PR dotnet#67408 bumped the ws dependency from ^7.5.10 to ^7.5.11 in src/SignalR/clients/ts/signalr/package.json and regenerated signalr/yarn.lock accordingly, but never propagated the change to the downstream yarn.lock files that transitively depend on @microsoft/signalr via a link: reference: - src/Components/Web.JS/yarn.lock - src/SignalR/clients/ts/FunctionalTests/yarn.lock - src/SignalR/clients/ts/signalr-protocol-msgpack/yarn.lock Each still only had a locked entry for the old ^7.5.10 range. With --frozen-lockfile, yarn classic v1 has no cached resolution for the new ^7.5.11 range and its fallback behavior when a fresh HTTP request isn't made is a non-deterministic 'Couldn't find package' error rather than a clean fetch - which is what has been intermittently failing in internal/release/8.0 CI (e.g. build 3029345's Web.JS prebuild-hook yarn install). Regenerated each lockfile so ws now resolves cleanly (latest patch satisfying ^7.5.11 in each case). Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Upgrade ws version for SingnalR release 8
Summary of the changes (Less than 80 chars)
Description
Upgrade ws package to latest fixed version 7.5.11
Fixes #67407 #67271