Releases: wp-graphql/wp-graphql-smart-cache
v1.3.3
Release Notes
Chores / Bugfixes
- #294: fix: queryid not returning X-GraphQL-Keys headers
- #292: chore: update test workflow to use docker compose instead of docker-compose
- #291: fix: restore whitespace rules for PHPCBF
- #286: chore: update .wordpress-org assets
- #284: chore: Note that hosts might set a limit on caching
New Contributors
- @josephfusco made their first contribution in #284
- @missionmike made their first contribution in #291
Full Changelog: v1.3.2...v1.3.3
Contributors
Assets 3
v1.3.2
v1.3.1
v1.3.0
Release Notes
New Features
- #270: feat: force enable query analyzer. This fixes a regression to WPGraphQL Smart Cache users caused by the WPGraphQL v1.20.0 release, where the Query Analyzer became optional and defaulted to "off". WPGraphQL Smart Cache now force-enables the Query Analyzer to support Cache tagging and tag-based cache invalidation.
Full Changelog: v1.2.1...v1.3.0
v1.2.1
Release Notes
Chores / Bugfixes
- #266: ci: update tests to run against WordPres 6.4
- #266: fix: ensure store_content() is passed a string to adhere to phpstan standards
- #262: fix: remove invalid namespaces from autoloading. Thanks @szepeviktor!
- #251: ci: add WP 6.3 to test matrix
- #258: ci: add build-plugin command to set up no-dev
New Contributors
- @szepeviktor made their first contribution in #262
Full Changelog: v1.2.0...v1.2.1
Contributors
Assets 3
v1.2.0
Release Notes
Upgrade Notice
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 Documents
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.
New Features
- #227: feat: add garbage collection for graphql_documents (see upgrade notice)
Chores / Bugfixes
v1.1.4
Release Notes
Chores / Bugfixes
- #237 fix: when creating a new query, do not show "something is wrong with form data" error
- #242 ci: increase phpstan to level 7
- #241 ci: increase phpstan to level 5,6
- #240 ci: increase phpstan to level 3,4
- #239 ci: increase phpstan to level 2
- #236 ci: add phpstan workflow to check code quality
- #234 fix: do not cache mutations to object cache results
- #235 ci: tests failing after wpgraphql v1.14.5 release