Changelog
This is a patch release for v2.11
Bug fixes and improvements
Server
Hasura doesn't allow certain queries to be cached. Namely, Remote Schema or Action queries with forward_client_headers set to true.
Currently, Hasura throws an error and fails the query. The behavior is now changed to not throw an error. Hasura now always fetches data from the upstream API, skips the cache, and returns the response with a Warning header.
The warning headers are as follows:
warning: 199 - Actions that forward client headers cannot currently be cached
warning: 199 - Remote schemas or joins that forward client headers cannot currently be cached
Note that Remote Schemas with forward_client_headers: true were erroneously allowed to cache before.
The following bugs are also fixed -
- Include Remote Schema root fields also in the cache restriction check
- Include Remote Schema-to-Remote Schema joins also in the caching restriction check
(Enterprise edition only)
Build
Updates base image of graphql-engine to the latest available ubuntu update to avail all the security patches.