WPGraphQL Smart Cache

2.3.2 Security Fix This release closes an issue where a request carrying both a query and a queryId could store the query as a GraphQL Document and claim the queryId as an alias name without authorization. The automatic persisted query flow now only accepts a queryId that is the SHA-256 hash of the query it accompanies, and documents are validated before they are stored. After updating, open "GraphQL > Settings > Saved Queries". A new panel shows how many automatically registered documents exist and how many carry an alias name that was not derived from the document hash, with a button to delete the automatically registered ones. Deleting them is safe: clients that still use one re-send the full query on their next request. Documents you have granted, denied, or grouped are kept. The same audit is available as wp graphql smart-cache documents audit and wp graphql smart-cache documents purge. 2.0.1 This release fixes an issue where authenticated user data (such as draft posts) could be incorrectly cached and served to public users when using the Object Cache feature. Users with Object Cache enabled should update immediately. 2.0.0 This release includes breaking changes to be compatible with WPGraphQL 2.0.0. When upgrading WPGraphQL to v2.0.0, you must also upgrade WPGraphQL Smart Cache to v2.0.0. WPGraphQL Smart Cache v2.0.0 is not compatible with WPGraphQL v1.x.x. 1.3.0 This fixes a regression to WPGraphQL v1.20.0 where the Query Analyzer became optional and defaulted to "off". WPGraphQL Smart Cache force-enables the Query Analyzer to support Cache tagging and tag-based cache invalidation. 1.2.0 Code Removal This release removes some code specific to WP Engine that's been moved to WP Engine's MU Plugins. Updating to WPGraphQL Smart Cache v1.2.0 or newer should be done at the same time as updating to WPGraphQL v1.16.0 otherwise some caches might not evict properly in response to data changes. Garbage Collection of GraphQL Document When using "Automated Persisted Queries", documents are stored in the "GraphQL Document" post type and as client queries change over time an excess of persisted queries can be stored. Garbage collection allows for documents to be purged after a certain amount of time. You can enable "Garbage Collection" under "GraphQL > Settings > Saved Queries" and checking the option to "Delete Old Queries". When enabling this feature, documents that are not associated with a "Group" will be purged after xx amount of days according to the settings. Before enabling this setting, we recommend going through your saved GraphQL Documents and assigning a "group" to any that you want to skip garbage collection. Groups are like bookmarks or collections for your GraphQL Documents. You can use them for whatever reason you like, but if a document is grouped, it will not be automatically garbage collected. 0.2.0 This release removes a lot of code that has since been released as part of WPGraphQL core. In order to use v0.2.0+ of WPGraphQL Smart Cache, you will need WPGraphQL v1.12.0 or newer.