Skip to content

Releases: wp-graphql/wp-graphql-smart-cache

v1.3.2

25 Apr 21:25
9c27ed0
Compare
Choose a tag to compare

Release Notes

Chores / Bugfixes

  • #278: ci: Update tests to run against WordPress 6.5

Full Changelog: v1.3.1...v1.3.2

v1.3.1

19 Feb 20:40
7d98350
Compare
Choose a tag to compare

Release Notes

Chores / Bugfixes

  • #273: fix: improve clarity on Cache settings page
  • #272: fix: invalidate caches for menu items

Full Changelog: v1.3.0...v1.3.1

v1.3.0

07 Feb 23:34
7181a68
Compare
Choose a tag to compare

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

11 Dec 21:48
c80c0d5
Compare
Choose a tag to compare

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

Full Changelog: v1.2.0...v1.2.1

v1.2.0

31 Aug 21:46
Compare
Choose a tag to compare

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

  • #244: fix: handle errors when editing graphql documents in the admin
  • #253: ci: add varnish docker image. Update docs.
  • #247: fix: remove wpengine specific code (see upgrade notice).
  • #257: ci: use .distignore when building plugin for github release

v1.1.4

03 Aug 20:21
Compare
Choose a tag to compare

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

v1.1.3

17 Jul 17:29
Compare
Choose a tag to compare

Release Notes:

Chores / Bugfixes**

  • #230 fix: disable cache maps when "Use Object Cache" is disabled.

v1.1.2

26 Jun 18:51
Compare
Choose a tag to compare

Release Notes

Chores / Bugfixes

  • #226 fix: add missing events to purge calls. Remove call to purge list of terms when term relationship has changed.

v1.1.1

18 May 19:21
Compare
Choose a tag to compare

Release Notes

Chores / Bugfixes

  • #221 fix: updating menus not assigned to locations doesn't purge menus, even if their model is public

v1.1.0

28 Apr 19:59
209831b
Compare
Choose a tag to compare

Release Notes

New Features

  • #215 feat: graphql_purge_logs

Chores / Bugfixes

  • #214 fix: over-purging tags