pro-1.22.0

Author: rmosolgo

CHANGELOG-pro.md

@@ -8,8 +8,17 @@
 
 ### Bug Fix
 
+# 1.22.0 (19 March 2022)
+
+### New Features
+
+- Pusher subscriptions: it now sends updates in groups of 10 by default, pass `use ..., batch_size: 1` to revert to the previous behavior.
+- OperationStore: when using ActiveRecord for storage, it now batches updates to `last_used_at` every 5 seconds. Pass `use ..., update_last_used_at_every: 0` to update that column synchronously, instead, as before.
+
 # 1.21.6 (16 March 2022)
 
+### Bug Fix
+
 - OperationStore: Fix no method error in Redis pipeline usage
 
 # 1.21.5 (7 March 2022)

guides/operation_store/active_record_backend.md

@@ -83,3 +83,13 @@ GraphQL-Pro 1.15.0 introduced new features for the OperationStore. To enable the
 add_column :graphql_client_operations, :is_archived, :boolean, default: false
 add_column :graphql_client_operations, :last_used_at, :datetime
 ```
+
+## Updating `last_used_at`
+
+By default, GraphQL-Pro updates `last_used_at` values in a background thread every 5 seconds. You can customize this by passing a number of seconds to `update_last_used_at_every:` when installing the OperationStore:
+
+```ruby
+use GraphQL::Pro::OperationStore, update_last_used_at_every: 1 # seconds
+```
+
+To update that column inline each time an operation is accessed, pass `0`.

guides/pro/checksums/graphql-pro-1.22.0.txt

@@ -0,0 +1 @@
+f35ee054e97240c089f1f56d233875e6038ac264facfeddc0aeb2abd5d1c7c0844e92f2ab3087c45c2999f4fd7bec8720bcfd4794af19dc5e565afa884e1be85

guides/subscriptions/pusher_implementation.md

@@ -157,6 +157,16 @@ This will cause subscription payloads to include `compressed_result: "..."` inst
 
 By configuring `compress_pusher_payload: true` on a query-by-query basis, the subscription backend can continue to support clients running _old_ client code (by not compressing) while upgrading new clients to compressed payloads.
 
+### Batched Deliveries
+
+By default, `PusherSubscriptions` sends updates in batches of up to 10 at a time, using [batch triggers](https://github.com/pusher/pusher-http-ruby#batches). You can customize the batch size by passing `batch_size:` when installing it, for example:
+
+```ruby
+use GraphQL::Pro::PusherSubscriptions, batch_size: 1, ...
+```
+
+`batch_size: 1` will make `PusherSubscriptions` use the single trigger API instead of batch triggers.
+
 ## Webhook configuration
 
 Your server needs to receive webhooks from Pusher when clients disconnect. This keeps your local subscription database in sync with Pusher.