[Snyk] Upgrade cache-manager from 5.2.4 to 5.5.3 #3
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 was automatically created by Snyk using the credentials of a real user.
![snyk-top-banner](https://github.com/andygongea/OWASP-Benchmark/assets/818805/c518c423-16fe-447e-b67f-ad5a49b5d123)
Snyk has created this PR to upgrade cache-manager from 5.2.4 to 5.5.3.
ℹ️ Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.
The recommended version is 8 versions ahead of your current version.
The recommended version was released on 23 days ago.
Release notes
Package name: cache-manager
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: v5.4.0...v5.5.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: v5.3.2...v5.4.0
What's Changed
New Contributors
Full Changelog: v5.3.0...v5.3.2
Major fix as
5.3.0
did not have the dist folder on release.What's Changed
wrap
function by @ douglascayers in #599New Contributors
Full Changelog: 5.2.4...v5.3.1
What's Changed
wrap
function by @ douglascayers in #599New Contributors
Full Changelog: 5.2.4...v5.3.0
Important
Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.
For more information: