Skip to content

Docs: Correct the Repository methods listed in the upgrade guide #32

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
Moritz Mazetti (Radiergummi) merged 1 commit into from
Oct 26, 2026
Merged

Docs: Correct the Repository methods listed in the upgrade guide #32

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -413,8 +413,8 @@ Version 2 replaces Laravel's cache tags with tag versioning. Existing cache entr
- **Cached responses:** responses are stored as their status, headers and content, so caching works even if `serializable_classes` is restricted in
`config/cache.php` (the default in Laravel 13). A cached response is returned as an `Illuminate\Http\Response` with the same status, headers and
content, whatever class the original response had. Responses without content, such as streamed responses and file downloads, are not cached.
- **`Repository`:** the methods `get()`, `has()`, `getStore()`, `supportsTags()`, `serialize()` and `hydrate()` were removed, along with custom
serialization through a `Repository` subclass. Its constructor takes the tag TTL as a third argument.
- **`Repository`:** `has()`, `getStore()`, `supportsTags()` and `serialize()` were removed, along with custom serialization through a `Repository`
subclass. `get()`, `put()` and `delete()` have new signatures. Its constructor takes the tag TTL as a third argument.
- **Configuration:** `store` defaults to `null` (your default cache store) instead of `file`. The new `tag_ttl` option sets how long tag versions are kept
(30 days by default) and must be at least one second. The `failover` cache store is refused with an `InvalidArgumentException`.
- **Stores:** tags work on every cache store; a store with tag support is no longer needed.
Loading