release: v0.9.0

[graphql-ws-client-releaser]

🤖 New release

• graphql-ws-client: 0.8.2 -> 0.8.3 (✓ API compatible changes)

Changelog

v0.8.3 - 2024-06-08

New Features

• send periodic pings for keep alives (#103)
• impl debug for client (#101)
• add keep-alive capability (#93)

Bug Fixes

• swap no-logging feature for logging feature (#97)

Changes

• Fix compilation error in actor mod (#96)
• release-plz config tweaks (#95)
• simplify keep alive implementation (#94)
• pin release-plz version (#91)

---

This PR was generated with release-plz.

[rhishikeshj]

@obmarg it's weird that the CI action which uses cargo build --all-features works but cargo build does not

▶ cargo build --all-features
    Finished dev [unoptimized + debuginfo] target(s) in 0.23s

▶ cargo build
   Compiling graphql-ws-client v0.8.2 (/Users/rhishikeshj/workspace/juxt/artis/src/graphql-ws-client)
error[E0425]: cannot find value `keep_alive_duration` in this scope
   --> src/next/actor.rs:173:29
    |
173 | ...                   keep_alive_duration
    |                       ^^^^^^^^^^^^^^^^^^^
    |
help: you might have meant to use the available field
    |
173 |                             self.keep_alive_duration
    |                             +++++

For more information about this error, try `rustc --explain E0425`.
error: could not compile `graphql-ws-client` (lib) due to 1 previous error

[obmarg]

@rhishikeshj yeah, I think it's because the no-logger feature disables logging, so --all-features was (counterintuitively) removing code.

I want to rethink that, in retrospect it was not a good idea.