Releases: matchory/response-cache
Releases · matchory/response-cache
Version 1.4.2
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
Changelog
- Fix: The response cache flush command alias would not be recognised properly, leading to an invalid command entry
Version 1.4.0
Changelog
This release adds support for Laravel 11.
Version 1.3.2
Changelog
- Fix: The
artisan response-cache:flush
command has been renamed toartisan 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
Changelog
- Fix: Removed readonly declaration from base strategy
Version 1.3.0
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
Change log
- Fix: Configuration repository would not be injected as a callable
Version 1.2.1
Change log
- Fix: The config resolver could not be resolved
Version 1.2.0
Change log
- Feature: Compatibility with Laravel Octane: The library will not create memory leaks anymore and reacts to configuration changes at runtime if running in Laravel Octane.
- Fix: The source code would contain references to reserved copyright, conflicting with the package license (MIT). Those comments have been removed.
Version 1.1.2
Change log
- Fix: Disabling via config flag
enabled = false
would not work in some scenarios (#4) - Chore: Cleaned up
- Chore: Bumped dependency versions