Releases: anycable/anycable-rails
Release list
1.6.1
1.6.0
1.5.0
Features
-
JWT functionality is available without additional dependencies.
No need to install anycable-rails-jwt anymore.
-
Signed streams support.
Added
#signed_stream_namehelper andAnyCable::Rails.signed_stream_namehelper to generate signed streams. -
Added
websocket_urlparameter to provide a WS server address for clients.This new parameter automatically updates the
config.action_cable.urlto provide the WS server information to clients via#action_cable_meta_tag(or#action_cable_with_jwt_meta_tag) helpers. Thus, all you need to point your clients to AnyCable is configure thewebsocket_url(orANYCABLE_WEBSOCKET_URL) value, no code changes required. -
Allow specifying the whispering stream via
#stream_from(..., whisper: true).You can use specify the stream to use for whispering (client-initiated broadcasts) by adding
whisper: trueto the#stream_from(or#stream_for) method call. -
Broadcasting to objects.
Extended
ActionCable.server.broadcastto accept not only strings but objects (similar toChannel.broadcast_to(...)).See docs.
-
Extracted
rails g anycable:binfromrails g anycable:setup.This generator creates a
bin/anycable-goscript to run (and install) AnyCable server locally.
1.4.2
Features
- New
broadcast ..., to_others: trueAPI.
This new API makes it possible to exclude initiator from the list of recipients.
See docs.
- Automatic batch broadcasting.
It's possible to turn batch broadcasting on for web requests, background jobs, or any other units of work in Rails applications. The feature uses new batch broadcasting API.
See docs.
Changes
- Print warning if the database pool size is less than RPC pool size.
1.3.7
1.3.4
Features
- Add support and backport for Connection command callbacks.
- Backport command callbacks, so it could be used in Rails <7.1 (even w/o AnyCable).
1.3.0
This release makes our Action Cable integration more robust and safe to use with other extensions.
We also made it easier to run both Action Cable and AnyCable at the same time, so you can migrate gradually.
Changes
- Action Cable integration is completely rewritten to avoid potential patches incompatibility. The amount of patches code has been minimized, no more open classes, only
Module#prependwith a feature check.
Features
- Added
AnyCable::Rails.extend_adapter!method to make any Action Cable pub/sub adapter compatible with AnyCable (i.e., broadcast updates to both Action Cable engine and AnyCable).
Other
- Added a dedicated documentation on using AnyCable with Hotwire focused on the RPC-less use case.
1.2.0 🎄
1.1.0 🚸
This is a maintenance release. Most changes are internal and doesn't affect public APIs.
Requirements
- Ruby >= 2.6 is required.
- Rails >= 6.0 is required.
Changes
- Adding
anycableorgrpcgem as an explicit dependency is required.
Now, anycable-rails depends on anycable-core, which doesn't include gRPC server implementation.
You should either add anycable or grpc (>= 1.37) gem as an explicit dependency.
Features
- Added ability to embed AnyCable RPC into a Rails server process.
Set embedded: true in the configuration to launch RPC along with rails s (only for Rails 6.1+).
1.1.0.rc1
See notes for v1.1.0.