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 ^5.16.0 #126

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

Conversation

renovate[bot]
Copy link

@renovate renovate bot commented Oct 23, 2023

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
graphql-ws ^5.14.1 -> ^5.16.0 age adoption passing confidence

Release Notes

enisdenjo/graphql-ws (graphql-ws)

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)

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 becomes conflicted, 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 has been generated by Mend Renovate. View repository job log here.

@changeset-bot
Copy link

changeset-bot bot commented Oct 23, 2023

⚠️ No Changeset found

Latest commit: 62117db

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

@renovate renovate bot changed the title fix(deps): update dependency graphql-ws to ^5.14.2 fix(deps): update dependency graphql-ws to ^5.14.3 Dec 20, 2023
@renovate renovate bot changed the title fix(deps): update dependency graphql-ws to ^5.14.3 fix(deps): update dependency graphql-ws to ^5.15.0 Feb 12, 2024
@renovate renovate bot force-pushed the renovate/graphql-ws-5.x branch from aed6e74 to 84efec1 Compare March 27, 2024 23:31
@renovate renovate bot changed the title fix(deps): update dependency graphql-ws to ^5.15.0 fix(deps): update dependency graphql-ws to ^5.16.0 Mar 27, 2024
@renovate renovate bot force-pushed the renovate/graphql-ws-5.x branch from 84efec1 to 0d6c3ab Compare April 23, 2024 17:52
@renovate renovate bot force-pushed the renovate/graphql-ws-5.x branch from 0d6c3ab to 62117db Compare April 23, 2024 18:19
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.

None yet

0 participants