Skip to content

Releases: obmarg/graphql-ws-client

v0.11.1

29 Oct 19:32
9e8ee6a
Compare
Choose a tag to compare

Bug Fixes

  • Fixed an infinite loop in the actor that could occur when all Client
    instances are dropped and there are still ongoing operations (#124)

Contributors

Thanks to the people who contributed to this release:

v0.11.0

25 Oct 09:35
280127b
Compare
Choose a tag to compare

Changes

  • Updated tungstenite bounds to support 0.24 as well as 0.23. (#121)

Contributors

Thanks to the people who contributed to this release:

v0.10.2

21 Aug 17:13
fa8447d
Compare
Choose a tag to compare

Bug Fixes

  • send graphql-specific ping instead of ws ping frame (#117)

Changes

  • Tidied up some documentation (#114)
  • Handled some clippy lints (#114)

Bug Fixes

  • graphql-transport-ws pings are now responded to with graphql-tranport-ws pongs,
    rather than websocket pongs (#116)
  • Keep alives now send graphql-transport-ws ping messages instead of websocket ping
    frames (#117)

Contributors

Thanks to the people who contributed to this release:

v0.10.1

08 Jun 16:20
a167a2a
Compare
Choose a tag to compare

Bug Fixes

  • Fixed some compile errors when ws_stream_wasm was enabled and tungstenite
    was not (#111)

v0.10.0

08 Jun 14:58
ee7848e
Compare
Choose a tag to compare

Breaking Changes

  • All Connection trait functions now return impl Future instead of BoxFuture
    (#108)
  • Removed the legacy API that was deprecated in v0.8.0
    (#81)
  • The deprecated async-tungstenite feature has been removed. Use the
    tungstenite feature instead, which works with async-tungtenite,
    tokio-tungstenite and any other library that provides a
    futures::{Stream, Sink} based tungsetenite interface.
    (#106)

Changes

  • MSRV is now 1.76
  • Updated dependencies (#100)
    • tungstenite 0.23
    • graphql_client 0.14
  • Removed unused dependencies (#105)
    • async-trait
    • pin-project-lite

Contributors

Thanks to the people who contributed to this release:

v0.9.0

08 Jun 12:43
b30e2b8
Compare
Choose a tag to compare

Breaking Changes

  • The no-logging feature has been removed in favour of a default logging
    feature (#97)

New Features

  • Added keep-alive functionality. When enabled this will send periodic pings
    when the connection appears inactive. If these pings are not replied to, the
    connection will be considered broken.
    (#93, #94, #103)
  • Client is now Debug (#101)

Changes

  • simplify keep alive implementation
  • pin release-plz version (#91)

Contributors

Thanks to the people who contributed to this release:

v0.8.2

09 Apr 09:27
01ce959
Compare
Choose a tag to compare

Changes

  • Client::subscribe now takes &self instead of &mut self, to make sharing a
    Client among threads easier (#88)
  • Client is now clone, again to make sharing among threads easier
    (#88)

v0.8.1

21 Mar 16:04
Compare
Choose a tag to compare

Fixes

  • Hopefully fixed the docs.rs build

v0.8.0

17 Mar 14:52
Compare
Choose a tag to compare

Breaking Changes

  • async_tungstenite is no longer a default feautre, you should explicitly
    enable it if you need it.
  • Updated to tungstenite 0.21
  • MSRV is now 1.69 (there was no official MSRV before)
  • Subscription IDs sent to the server are now just monotonic numbers rather
    than uuids.

Deprecations

These will be removed in a future version, probably in v0.9.0

  • AsyncWebsocketClient and all its supporting traits and structs are now
    deprecated.
  • The async-tungstenite feature flag is deprecated and will be removed in
    favour of tungstenite eventually.

New Features

  • Added an entirely new client API as a replacement for the old API.
  • Added a subscribe function to next::ClientBuilder to make
    creating a single subscription on a given connection easier.

Changes

  • graphql-ws-client now depends only on tungstenite and not directly on
    async-tungstenite (or tokio-tungstenite). This should allow it to work
    with more versions of the async libraries (provided they support the same
    tungstenite version).

v0.8.0-rc.2

13 Feb 12:39
f6ad843
Compare
Choose a tag to compare
v0.8.0-rc.2 Pre-release
Pre-release

Breaking Changes

  • async-tungstenite is no longer automatically enabled when adding any of the
    client feature flags.

Changes

  • graphql-ws-client now depends only on tungstenite and not directly on
    async-tungstenite (or tokio-tungstenite) This should allow it to work
    with more versions of the async libraries (provided they support the same
    tungstenite version).

Bug Fixes

  • Fixed tokio-tungstenite support by switching the async_tungstenite
    Connection impl to a generic impl on any tungstenite compatible Stream
    & Sink.