Changelog
8 September 2026
v1.10.0
Set your filter when you connect
StartStreamRequest now carries a filters field, so the filter travels with the connection that uses
it. Omit it, or send an empty filter, for an unfiltered stream. Nothing from a previous connection
carries over.
Filters no longer reset or expire
A filtered stream previously reverted to unfiltered when the connection dropped and was re-established, and stopped being applied after roughly an hour on a long-lived connection. Both are resolved: the filter you send applies for the whole life of that connection.
Changing a filter through UpdateSubscription
SubscriptionService.UpdateSubscription is now marked deprecated. It still applies a new filter to an
open stream at the next revalidation pass, but the change does not survive a reconnect. To change a
filter, reconnect with the filter you want on StartStreamRequest.
The filter now belongs to the connection rather than being held for you between connections. That makes
the behaviour predictable — what you send is what you get, for exactly as long as you stay connected —
and it removes the reset and expiry surprises above. UpdateSubscription remains available for now so
existing integrations keep working, but new work should not use it.
See the filtering guide for the filter structure and worked examples.