- Update dependency laragear/cache-query to v5 #563
Closed
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
^4.2.2->^5.0.1Release Notes
Laragear/CacheQuery (laragear/cache-query)
v5.0.1Compare Source
What's Changed
Full Changelog: Laragear/CacheQuery@v5.0.0...v5.0.1
v5.0.0Compare Source
What's Changed
A lot has changed, hence why a new version.
Most notably, there are three big changes.
cache()only supports either the TTL, or a Flexible TTL array.Laragear\CacheQuery\Cacheobject instance.Full Changelog: Laragear/CacheQuery@v4.2.2...v5.0.0
Configuration
📅 Schedule: Branch creation - On day 1 of the month, every 3 months ( * * 1 */3 * ) in timezone Europe/Warsaw, Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by Renovate Bot.