Documentation lists Aggregate, but feature not released in pg_graphql

**Describe the bug** The Supabase GraphQL documentation mentions the possibility to enable `aggregate` fields using table comments (see: [https://supabase.com/docs/guides/graphql/configuration#aggregate](https://supabase.com/docs/guides/graphql/configuration#aggregate)). However, when attempting to enable it on a Supabase Cloud project, the feature does not appear in the schema. This looks like either: - the feature is not yet released despite being documented, or - there is a bug in the extension where the configuration is silently ignored. **To Reproduce** Steps to reproduce the behavior: 1. On Supabase Cloud, with pg_graphql v1.5.11 (Postgres 17.4.1.074), open the SQL Editor. 2. Run: ```sql comment on table "TableName" is e'@graphql({"aggregate": {"enabled": true}})'; ``` 3. Go to the GraphQL schema explorer in Supabase Studio or introspect the schema via GraphQL. 4. Notice that the `aggregate` field is not exposed on the type. **Expected behavior** The GraphQL schema should expose an `aggregate` field on the `BlogPost` type when `aggregate.enabled = true`, as described in the documentation. **Screenshots** No SQL error is returned when applying the comment, but the field is missing from the schema. Example from the GraphQL Explorer: ```graphql # Expected to see something like: aggregate { count ... } # But aggregate is not present. ``` **Versions:** - PostgreSQL: 17.4.1.074 - pg\_graphql: 1.5.11 (Supabase Cloud) **Additional context** - The related PR implementing aggregate support is [https://github.com/supabase/pg\_graphql/pull/589](https://github.com/supabase/pg_graphql/pull/589) (merged May 2025). - The last pg\_graphql release on GitHub is from February 2025, so it seems the feature has not been released yet. - However, the Supabase documentation already describes `aggregate` as available, which creates confusion. **Security** This is not a security issue.