Skip to content
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

fix(deps): update dependency graphql-ws to v5.16.2 #456

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Jun 9, 2022

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
graphql-ws (source) 5.10.1 -> 5.16.2 age adoption passing confidence

Release Notes

enisdenjo/graphql-ws (graphql-ws)

v5.16.2

Compare Source

Patch Changes

v5.16.1

Compare Source

Patch Changes

v5.16.0

Compare Source

Bug Fixes
  • server: Return all subscriptions regardless of the return invocation order (f442288)
  • server: should not send error messages if socket closes before onSubscribe hooks resolves (db47a66), closes #​539
Features
  • server: Close code and reason are optional (6ae6e6f), closes #​547

v5.15.0

Compare Source

Bug Fixes
  • client: Use TerminatedCloseEvent class extending an Error for rejecting promises when terminating (74b4ceb), closes #​531
  • server: Dispose of subscriptions on close even if added late to the subscriptions list (#​534) (e45d6b1), closes #​532
Features

5.14.3 (2023-12-20)

Bug Fixes
  • client: Use closures instead of bindings (with this) (812129d)
  • remove package.json workspaces entry in release (63a831e), closes #​524

5.14.2 (2023-10-23)

Bug Fixes
  • client: correct close code for Bad Gateway reason (#​512) (0438650)

5.14.1 (2023-09-28)

Bug Fixes
  • server: Acknowledge connection before notifying the client to avoid race conditions with slow sends (#​506) (8cb82bd), closes #​501

v5.14.3

Compare Source

Bug Fixes
  • client: Use closures instead of bindings (with this) (812129d)
  • remove package.json workspaces entry in release (63a831e), closes #​524

v5.14.2

Compare Source

Bug Fixes
  • client: correct close code for Bad Gateway reason (#​512) (0438650)

v5.14.1

Compare Source

Bug Fixes
  • server: Acknowledge connection before notifying the client to avoid race conditions with slow sends (#​506) (8cb82bd), closes #​501

v5.14.0

Compare Source

Features

5.13.1 (2023-05-15)

Bug Fixes

v5.13.1

Compare Source

Bug Fixes

v5.13.0

Compare Source

Features

5.12.1 (2023-03-31)

Bug Fixes
  • Add file extensions to imports/exports in ESM type definitions (48775be)

v5.12.1

Compare Source

Bug Fixes
  • Add file extensions to imports/exports in ESM type definitions (48775be)

v5.12.0

Compare Source

Features

5.11.3 (2023-02-01)

Bug Fixes

5.11.2 (2022-09-21)

Bug Fixes
  • Reorder types paths in package.json for better import resolution (#​406) (37263c5)

5.11.1 (2022-09-16)

Bug Fixes
  • server: Shouldn't send a complete message if client sent it (331fe47), closes #​403

v5.11.3

Compare Source

Bug Fixes

v5.11.2

Compare Source

Bug Fixes
  • Reorder types paths in package.json for better import resolution (#​406) (37263c5)

v5.11.1

Compare Source

Bug Fixes
  • server: Shouldn't send a complete message if client sent it (331fe47), closes #​403

v5.11.0

Compare Source

Features
  • client: Provide subscribe payload in generateID (d0bc6e1), closes #​398

5.10.2 (2022-09-12)

Performance Improvements

5.10.1 (2022-08-19)

Bug Fixes
  • client: Debounce close by lazyCloseTimeout (c332837), closes #​388

v5.10.2

Compare Source

Performance Improvements

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

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 this update again.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate renovate bot force-pushed the renovate/graphql-ws-5.x branch 30 times, most recently from 0cfa718 to d9eba5f Compare June 16, 2022 17:01
@renovate renovate bot force-pushed the renovate/graphql-ws-5.x branch from f0c6a37 to 15f13c8 Compare September 16, 2022 16:41
@renovate renovate bot changed the title fix(deps): update dependency graphql-ws to v5.11.0 fix(deps): update dependency graphql-ws to v5.11.1 Sep 16, 2022
@renovate renovate bot force-pushed the renovate/graphql-ws-5.x branch from 15f13c8 to 34c9ce4 Compare September 21, 2022 20:29
@renovate renovate bot changed the title fix(deps): update dependency graphql-ws to v5.11.1 fix(deps): update dependency graphql-ws to v5.11.2 Sep 21, 2022
@renovate renovate bot changed the title fix(deps): update dependency graphql-ws to v5.11.2 fix(deps): update dependency graphql-ws to v5.12.0 Mar 19, 2023
@renovate renovate bot force-pushed the renovate/graphql-ws-5.x branch from 34c9ce4 to b1b7086 Compare March 19, 2023 01:57
@renovate renovate bot changed the title fix(deps): update dependency graphql-ws to v5.12.0 fix(deps): update dependency graphql-ws to v5.12.1 Mar 31, 2023
@renovate renovate bot force-pushed the renovate/graphql-ws-5.x branch from b1b7086 to 9fdbf9c Compare March 31, 2023 14:31
@renovate renovate bot changed the title fix(deps): update dependency graphql-ws to v5.12.1 fix(deps): update dependency graphql-ws to v5.13.1 May 28, 2023
@renovate renovate bot force-pushed the renovate/graphql-ws-5.x branch from 9fdbf9c to 95064be Compare May 28, 2023 11:41
@renovate renovate bot changed the title fix(deps): update dependency graphql-ws to v5.13.1 fix(deps): update dependency graphql-ws to v5.14.0 Jun 22, 2023
@renovate renovate bot force-pushed the renovate/graphql-ws-5.x branch from 95064be to bf57893 Compare June 22, 2023 14:01
@renovate renovate bot force-pushed the renovate/graphql-ws-5.x branch 3 times, most recently from b6db624 to 0c1abd6 Compare July 30, 2023 02:51
@renovate renovate bot changed the title fix(deps): update dependency graphql-ws to v5.14.0 fix(deps): update dependency graphql-ws to v5.14.1 Sep 28, 2023
@renovate renovate bot force-pushed the renovate/graphql-ws-5.x branch from 0c1abd6 to 8381737 Compare September 28, 2023 18:36
@renovate renovate bot force-pushed the renovate/graphql-ws-5.x branch from 8381737 to 60e85e5 Compare October 23, 2023 17:21
@renovate renovate bot changed the title fix(deps): update dependency graphql-ws to v5.14.1 fix(deps): update dependency graphql-ws to v5.14.2 Oct 23, 2023
@renovate renovate bot changed the title fix(deps): update dependency graphql-ws to v5.14.2 fix(deps): update dependency graphql-ws to v5.14.3 Dec 20, 2023
@renovate renovate bot force-pushed the renovate/graphql-ws-5.x branch from 60e85e5 to 14fd2dc Compare December 20, 2023 12:26
@renovate renovate bot force-pushed the renovate/graphql-ws-5.x branch from 14fd2dc to 5deb23a Compare February 12, 2024 18:18
@renovate renovate bot changed the title fix(deps): update dependency graphql-ws to v5.14.3 fix(deps): update dependency graphql-ws to v5.15.0 Feb 12, 2024
@renovate renovate bot force-pushed the renovate/graphql-ws-5.x branch from 5deb23a to 3e1d497 Compare March 27, 2024 22:11
@renovate renovate bot changed the title fix(deps): update dependency graphql-ws to v5.15.0 fix(deps): update dependency graphql-ws to v5.16.0 Mar 27, 2024
@renovate renovate bot force-pushed the renovate/graphql-ws-5.x branch from 3e1d497 to 9110a13 Compare January 8, 2025 20:14
@renovate renovate bot changed the title fix(deps): update dependency graphql-ws to v5.16.0 fix(deps): update dependency graphql-ws to v5.16.1 Jan 8, 2025
@renovate renovate bot force-pushed the renovate/graphql-ws-5.x branch from 9110a13 to 9b9df9b Compare January 10, 2025 16:16
@renovate renovate bot changed the title fix(deps): update dependency graphql-ws to v5.16.1 fix(deps): update dependency graphql-ws to v5.16.2 Jan 10, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants