chore(deps): upgrade to ws@8.20.1#5439
Open
AviVahl wants to merge 1 commit into
Open
Conversation
AviVahl
changed the title
Contributor
Author
|
upgraded to 8.20.0 and rebased to latest main |
AviVahl
force-pushed
the
ws-8.19.0
branch
2 times, most recently
from
846a05f to
94cd88e
Compare
codeCraft-Ritik
left a comment
codeCraft-Ritik
left a comment
There was a problem hiding this comment.
Solid change — keeping up with new Node.js versions is important for long-term stability.
Thanks for the update.
Contributor
Author
|
@darrachequesne any chance this can merge? |
AviVahl
force-pushed
the
ws-8.19.0
branch
2 times, most recently
from
94cd88e to
9e7257e
Compare
AviVahl
changed the title
Contributor
Author
|
Rebased to |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
https://github.com/websockets/ws/releases/tag/8.20.1
packages/socket.io-cluster-adapter/package-lock.json. Package is specified in the "workspaces" and is locked by the rootpackage-lock.jsonpackage-lock.jsonincludes"peer": truechanges and other cleanups thatnpm@11.12.1applies. (version that comes withnode@24.15.0)The kind of change this PR does introduce