Skip to content

Releases: matchory/response-cache

Version 1.5.2

Choose a tag to compare

@Radiergummi Radiergummi released this 11 Mar 11:59
55cd545

Changelog

  • Chore: Added support for Laravel 12
  • Chore: Improved development tooling

Version 1.5.1

Choose a tag to compare

@Radiergummi Radiergummi released this 17 Feb 07:15
324bd93

Change log

  • Fix: The cache flushing was handled using a PSR CacheInterface method (clear) instead of the Laravel-specific method (flush). Despite this should have had the same effect, calling clear on Laravel caches purges the entire store, even if called on a TaggedStore. This is a bug in Laravel, but they won't fix it.
  • Fix: If the response cache was used with a long-running application server, such as Octane, and the cache would be enabled or disabled at runtime, this change may in some circumstances have not been picked up.

Version 1.5.0

Choose a tag to compare

@Radiergummi Radiergummi released this 27 Jan 15:17
47cd850

Changelog

  • Feature: Added an option to add a Response-Cache-Status: hit|miss header to all responses passing through the cache middleware. This makes it easier to verify whether a response has been served from the cache at runtime.
  • Chore: Bumped dependencies, added more tests

Cache Status

The cache status header will be enabled by default for new installations, but not added in existing installations unless you update your configuration file to include the new setting response_status_enabled.

Full Changelog: 1.4.2...1.5.0

Version 1.4.2

Choose a tag to compare

@Radiergummi Radiergummi released this 01 Aug 13:32
b3a8ecb

Changelog

  • Fix: If a response could not be resolved from the cache despite being reported as existing, the Response typehint of the middleware handler would cause the request to fail.

Full Changelog: 1.4.1...1.4.2

Version 1.4.1

Choose a tag to compare

@Radiergummi Radiergummi released this 21 Jun 14:20
87a8ef8

Changelog

  • Fix: The response cache flush command alias would not be recognised properly, leading to an invalid command entry

Version 1.4.0

Choose a tag to compare

@Radiergummi Radiergummi released this 21 Jun 13:54
2e29670

Changelog

This release adds support for Laravel 11.

Version 1.3.2

Choose a tag to compare

@Radiergummi Radiergummi released this 30 Aug 12:47
b948bf0

Changelog

  • Fix: The artisan response-cache:flush command has been renamed to artisan response-cache:clear, which keeps it in line with other cache clearing commands in Laravel. An alias has been put into place, so the previous version keeps on working.
    Additionally, a log message akin to the Laravel commands will be printed now, to make it feel more "Laravel-y".
  • Chore: Bumped dependency versions

Version 1.3.1

Choose a tag to compare

@Radiergummi Radiergummi released this 06 Mar 08:22
189eaa6

Changelog

  • Fix: Removed readonly declaration from base strategy

Version 1.3.0

Choose a tag to compare

@Radiergummi Radiergummi released this 06 Mar 06:41
e797bf6

Changelog

  • Feature: switched to PHP 8.2
  • Fix: Fixed potential issue where tags would be null
  • Chore: added tests
  • Chore: Widened Laravel support to include 8/9/10

Version 1.2.2

Choose a tag to compare

@Radiergummi Radiergummi released this 20 May 14:11
efd5c92

Change log

  • Fix: Configuration repository would not be injected as a callable