Releases: CuatroElixir/slipstream
Releases · CuatroElixir/slipstream
v1.2.2
What's Changed
- Fix missing join_ref in PushMessage for Phoenix V2 protocol by @evan-hines-js in #84
- This fixes compatibility with Phoenix v1.8.3.
New Contributors
- @evan-hines-js made their first contribution in #84
Full Changelog: v1.2.1...v1.2.2
v1.2.1
What's Changed
- Fix sample code in
c:Slipstream.init/1by @eksperimental in #77 - fix: elixir v1.19 compatible struct update syntax by @StrongFennecs in #82
New Contributors
- @eksperimental made their first contribution in #77
- @StrongFennecs made their first contribution in #82
Full Changelog: v1.2.0...v1.2.1
v1.2.0
v1.1.3
Fixed
- Fixed callback return types to include
{:noreply, new_socket}and{:noreply, new_socket, _rest}(for returning timeouts or triggeringhandle_continue/2for example). These return types were always supported but not declared in the callback, so the dialyzer would complain if these values were returned.c:Slipstream.handle_connect/1c:Slipstream.handle_disconnect/2c:Slipstream.handle_join/3c:Slipstream.handle_message/4c:Slipstream.handle_reply/3c:Slipstream.handle_topic_close/3c:Slipstream.handle_leave/2
v1.1.2
What's Changed
- Bump github action versions by @svrdlans in #62
- Clarify push docs by @nathanl in #65
- Note that message retries are the application's responsibility by @nathanl in #64
- Fix documentation mispelling :norelpy -> :noreply by @davydog187 in #69
- Clarify client startup behavior in tests by @davydog187 in #68
- Update to the latest ex_doc by @davydog187 in #67
- Fix Elixir 1.17 type error by @fhunleth in #70
New Contributors
- @svrdlans made their first contribution in #62
- @nathanl made their first contribution in #65
- @davydog187 made their first contribution in #69
Full Changelog: v1.1.1...v1.1.2
v1.1.1
What's Changed
- Deserialize binary broadcast messages by @the-mikedavis in #61
Full Changelog: v1.1.0...v1.1.1
v1.1.0
v1.0.4
v1.0.3
Fixed
nimble_optionsis now allowed at~> 1.0 or ~> 0.1.- NimbleOptions' v1.0.0 release contains no breaking changes from the 0.x release series.
v1.0.2
Fixed
- Fixed a memory growth issue that could occur when a socket failed to join a channel repeatedly.
- Memory usage of the Slipstream.Connection process and the client process could grow sharply as the socket tried to rejoin the failed topic, with higher memory usage per retry and per unjoined topic.