Skip to content
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.

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

[Snyk] Upgrade cache-manager from 5.2.4 to 5.5.3 #3

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

dagistan-tuncbilek
Copy link
Owner

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
  • 5.5.3 - 2024-05-22
  • 5.5.2 - 2024-04-29
  • 5.5.1 - 2024-04-05
  • 5.5.0 - 2024-04-04

    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:

    const memoryCache = await caching('memory', {
      max: 100,
      ttl: 10 * 1000 /*milliseconds*/,
    });
    memoryCache.on('error', (error) => {
      console.error('Cache error:', error);
    });

    What's Changed

    New Contributors

    Full Changelog: v5.4.0...v5.5.0

  • 5.4.0 - 2024-01-19

    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

  • 5.3.2 - 2023-12-19

    What's Changed

    New Contributors

    Full Changelog: v5.3.0...v5.3.2

  • 5.3.1 - 2023-11-17

    Major fix as 5.3.0 did not have the dist folder on release.

    What's Changed

    New Contributors

    Full Changelog: 5.2.4...v5.3.1

  • 5.3.0 - 2023-11-16

    What's Changed

    New Contributors

    Full Changelog: 5.2.4...v5.3.0

  • 5.2.4 - 2023-10-06
from cache-manager GitHub release notes

Important

  • Check the changes in this PR to ensure they won't cause issues with your project.
  • This PR was automatically created by Snyk using the credentials of a real user.

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:

Snyk has created this PR to upgrade cache-manager from 5.2.4 to 5.5.3.

See this package in npm:
cache-manager

See this project in Snyk:
https://app.snyk.io/org/dagistan-tuncbilek/project/b00749f8-a315-4ff7-8e14-6b59961f689e?utm_source=github&utm_medium=referral&page=upgrade-pr
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Adding refreshThreshold Parameter to the wrap Function
2 participants