-
Notifications
You must be signed in to change notification settings - Fork 7
Update dependency ws to v8.18.2 #134
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
Open
renovate
wants to merge
1
commit into
main
Choose a base branch
from
renovate/ws-8.x
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Conversation
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
1d253dd
to
e6216e1
Compare
e6216e1
to
28e4151
Compare
e4f1d2a
to
9181e5b
Compare
9181e5b
to
7a24d50
Compare
7a24d50
to
15e06df
Compare
15e06df
to
a9e8b9a
Compare
cafb25f
to
908acd2
Compare
908acd2
to
530d977
Compare
530d977
to
b1fc3dd
Compare
b1fc3dd
to
9d9fe3e
Compare
9d9fe3e
to
414f652
Compare
414f652
to
bddea25
Compare
bddea25
to
3fa3854
Compare
3fa3854
to
987bb7c
Compare
987bb7c
to
3ccfafe
Compare
3ccfafe
to
786a331
Compare
c82973a
to
022b645
Compare
022b645
to
dae5a1d
Compare
dae5a1d
to
c658611
Compare
c658611
to
4339807
Compare
4339807
to
7738677
Compare
7738677
to
a061bb2
Compare
501e23d
to
7c35b83
Compare
7c35b83
to
3fe95cd
Compare
3fe95cd
to
c278300
Compare
c278300
to
34b42b0
Compare
34b42b0
to
edaa6f3
Compare
edaa6f3
to
b3f6bca
Compare
b3f6bca
to
e64b36f
Compare
e64b36f
to
6ca7025
Compare
6ca7025
to
483dd16
Compare
483dd16
to
644a97c
Compare
644a97c
to
23c1234
Compare
23c1234
to
422aea1
Compare
422aea1
to
5f621b0
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
None yet
0 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.
This PR contains the following updates:
8.3.0
->8.18.2
8.2.1
->8.18.1
Release Notes
websockets/ws (ws)
v8.18.2
Compare Source
Bug fixes
Fixed an issue that, during message decompression when the maximum size was
exceeded, led to the emission of an inaccurate error and closure of the
connection with an improper close code (#2285).
v8.18.1
Compare Source
Bug fixes
make them work when run via CITGM (
021f7b8
).v8.18.0
Compare Source
Features
Blob
(#2229).v8.17.1
Compare Source
Bug fixes
A request with a number of headers exceeding the[
server.maxHeadersCount
][server.maxHeadersCount]threshold could be used to crash a ws server.
The vulnerability was reported by Ryan LaPointe in https://github.com/websockets/ws/issues/2230.
In vulnerable versions of ws, the issue can be mitigated in the following ways:
[
--max-http-header-size=size
][--max-http-header-size=size] and/or the [maxHeaderSize
][maxHeaderSize] options sothat no more headers than the
server.maxHeadersCount
limit can be sent.server.maxHeadersCount
to0
so that no limit is applied.v8.17.0
Compare Source
Features
WebSocket
constructor now accepts thecreateConnection
option (#2219).Other notable changes
allowSynchronousEvents
option has been changed totrue
(#2221).This is a breaking change in a patch release. The assumption is that the option
is not widely used.
v8.16.0
Compare Source
Features
autoPong
option (01ba54e
).v8.15.1
Compare Source
Notable changes
allowMultipleEventsPerMicrotask
option has been renamed toallowSynchronousEvents
(4ed7fe5
).This is a breaking change in a patch release that could have been avoided with
an alias, but the renamed option was added only 3 days ago, so hopefully it
hasn't already been widely used.
v8.15.0
Compare Source
Features
allowMultipleEventsPerMicrotask
option (93e3552
).v8.14.2
Compare Source
Bug fixes
swallowed when running tests (
7f4e1a7
).v8.14.1
Compare Source
Bug fixes
fd3c64c
).v8.14.0
Compare Source
Features
WebSocket
constructor now accepts HTTP(S) URLs (#2162).socket
argument ofserver.handleUpgrade()
can now be a genericDuplex
stream (#2165).Other notable changes
v8.13.0
Compare Source
Features
finishRequest
option to support late addition of headers (#2123).v8.12.1
Compare Source
Bug fixes
browser
condition to package.json (#2118).v8.12.0
Compare Source
Features
utf-8-validate@6
(ff63bba
).Other notable changes
buffer.isUtf8()
][buffer.isUtf8()] is now used instead ofutf-8-validate
if available(
42d79f6
).v8.11.0
Compare Source
Features
WebSocket.prototype.addEventListener()
now supports an event listenerspecified as an object with a
handleEvent()
method. (9ab743a
).Bug fixes
WebSocket.prototype.addEventListener()
now adds an event listener only if itis not already in the list of the event listeners for the specified event type
(
1cec17d
).v8.10.0
Compare Source
Features
211d5d3
).v8.9.0
Compare Source
Features
v8.8.1
Compare Source
Bug fixes
Authorization
andCookie
headers are no longer sent if the originalrequest for the opening handshake is sent to an IPC server and the client is
redirected to another IPC server (
bc8bd34
).v8.8.0
Compare Source
Features
WS_NO_BUFFER_UTIL
andWS_NO_UTF_8_VALIDATE
environmentvariables (
becf237
).v8.7.0
Compare Source
Features
them with a custom HTTP response. (
6e5a5ce
).Bug fixes
Upgrade
header field value in the HTTPresponse is not a case-insensitive match for the value "websocket" (
0fdcc0a
).Authorization
andCookie
headers are no longer sent when following aninsecure redirect (wss: to ws:) to the same host (
d68ba9e
).v8.6.0
Compare Source
Features
v8.5.0
Compare Source
Features
WebSocket
class on the server (#2007).Bug fixes
Authorization
andCookie
headers are nolonger sent if the redirect host is different from the original host (#2013).
v8.4.2
Compare Source
Bug fixes
v8.4.1
Compare Source
Notable changes
websocket.ping()
,websocket.pong()
, andwebsocket.send()
are no longer converted toBuffer
s if the data does not need to be masked (#2000).v8.4.0
Compare Source
Features
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about these updates again.
This PR was generated by Mend Renovate. View the repository job log.