pro-1.29.12

Author: rmosolgo

CHANGELOG-pro.md

@@ -6,6 +6,14 @@
 
 ### New Features
 
+# 1.29.12 (12 Sept 2025)
+
+- `OperationStore`: also support `visibility_profile:` on lazy routes.
+
+# 1.29.11 (12 Sept 2025)
+
+- `OperationStore`: add `visibility_profile: ...` argument to `operation_store_sync` so that incoming operations are bound to the given profile.
+
 # 1.29.10 (3 Jun 2025)
 
 - `@defer`, `@stream`: Include `"data"` in the payload, if there is any, even if there are `"errors"` #5365

guides/operation_store/getting_started.md

@@ -90,6 +90,18 @@ mount lazy_routes.dashboard, at: "/graphql/dashboard"
 mount lazy_routes.operation_store_sync, at: "/graphql/sync"
 ```
 
+### With Visibility Profiles
+
+You can apply a {% internal_link "visibility profile", "/authorization/visibility#visibility-profiles" %} to incoming operations by passing the profile name to `operation_store_sync`, for example:
+
+```ruby
+mount MySchema.operation_store_sync(visibility_profile: :public_api), at: "/graphql/sync"
+# or:
+mount lazy_routes.operation_store_sync(visibility_profile: :public_api), at: "/graphql/sync"
+```
+
+This will apply that profile to all newly-synced operations. (It doesn't affect operations that were already synced.)
+
 ## Update the Controller
 
 Add `operation_id:` to your GraphQL context:

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

@@ -0,0 +1 @@
+ea5f544ddad2a88d1813629567dbaa3c6e0a11408ddc0c31e0b2129bc599aa1af0b791b0307944d2d26689f58f611b8c0aaac14f85b7b5c9cd5c1b5938499a90

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

@@ -0,0 +1 @@
+fea66a1684747ef85ea4d086f292cbb605ca2f28b0a705b47ae68b6701bd97c9ef462451767cab04b70516ac38b8a55069775803abc5c9289633ed1b73e19144