fix(deps): update dependency cache-manager to v6.3.1 #4087
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:
6.0.0
->6.3.1
3.6.3
->6.3.1
Release Notes
jaredwray/cacheable (cache-manager)
v5.5.0
Added Event Errors
Cache Manager now does not throw errors by default. Instead, all errors are evented through the error event. Here is an example on how to use it:
What's Changed
New Contributors
Full Changelog: jaredwray/cacheable@v5.4.0...v5.5.0
v5.4.0
Refresh cache keys in background
Both the caching and multicaching modules support a mechanism to refresh expiring cache keys in background when using the
wrap
function.This is done by adding a
refreshThreshold
attribute while creating the caching store or passing it to the wrap function.If
refreshThreshold
is set and after retrieving a value from cache the TTL will be checked.If the remaining TTL is less than refreshThreshold, the system will update the value asynchronously,
following same rules as standard fetching. In the meantime, the system will return the old value until expiration.
What's Changed
Full Changelog: jaredwray/cacheable@v5.3.2...v5.4.0
v5.3.2
What's Changed
New Contributors
Full Changelog: jaredwray/cacheable@v5.3.0...v5.3.2
v5.3.1
Major fix as
5.3.0
did not have the dist folder on release.What's Changed
wrap
function by @douglascayers in https://github.com/node-cache-manager/node-cache-manager/pull/599New Contributors
Full Changelog: jaredwray/cacheable@5.2.4...v5.3.1
v5.3.0
What's Changed
wrap
function by @douglascayers in https://github.com/node-cache-manager/node-cache-manager/pull/599New Contributors
Full Changelog: jaredwray/cacheable@5.2.4...v5.3.0
v5.2.4
Updates 🍻
async <T>(key: string, fn: () => Promise<T>, ttl?: WrapTTL<T>)
- https://github.com/node-cache-manager/node-cache-manager/pull/535What's Changed
New Contributors
Full Changelog: jaredwray/cacheable@5.2.3...5.2.4
v5.2.3
Bug Fixes
v5.2.2
Bug Fixes
v5.2.1
Bug Fixes
v5.2.0
Bug Fixes
Features
v5.1.7
Bug Fixes
v5.1.6
Bug Fixes
v5.1.5
Bug Fixes
v5.1.4
Compare Source
Bug Fixes
v5.1.3
Bug Fixes
v5.1.2
Bug Fixes
v5.1.1
Bug Fixes
v5.1.0
Features
v5.0.1
v5.0.0
v4.1.0
Compare Source
v4.0.1
Compare Source
v4.0.0
Compare Source
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about these updates again.
This PR was generated by Mend Renovate. View the repository job log.