From 1ca05a7a2a52dcbb136ac1cbf4363ad90aba605e Mon Sep 17 00:00:00 2001 From: Lukasz Raczylo Date: Fri, 6 Dec 2024 11:19:05 +0000 Subject: [PATCH] Release 0.24.x - changes the query introspection. --- README.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/README.md b/README.md index a21c5f8..88dd2cb 100644 --- a/README.md +++ b/README.md @@ -40,6 +40,8 @@ I wanted to monitor the queries and responses of our graphql endpoint. Still, we You should always try to stick to the latest and greatest version of the graphql-proxy to ensure that it's as much bug-free as possible. Following list will be kept to the maximum of five "most important" bugs and enhancements included in the latest versions. +* **06/12/2024 - 0.24.1** - Fixes the bug where deeply nested introspection queries were blocked despite of being present on the whitelist. GraphQL proxy will now inspect the queries in depth to find any possible nested introspections. + * **20/08/2024 - 0.23.21+** - Fixes the bug when timeouts were not respected on proxy-graphql line. Affected versions before that were timeouting after 30 seconds which was set as default ( thanks to Jurica Železnjak for reporting ). It also provides a temporary fix for running within kubernetes deployment, when graphql server ( for example - hasura ) took more time to start than the proxy, causing avalanche of errors with "can't proxy the request". * **19/08/2024 - 0.21.82+** - Fixed the issue when proxy failed to start if global cache was disabled, therefore not initialized and proxy tried to perform the cache operations during normal query operations.