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 node-cache from 4.1.1 to 4.2.1 #5

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

Conversation

coderisnot
Copy link
Owner

snyk-top-banner

Snyk has created this PR to upgrade node-cache from 4.1.1 to 4.2.1.

ℹ️ 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 2 versions ahead of your current version.

  • The recommended version was released on 5 years ago.

Release notes
Package name: node-cache
  • 4.2.1 - 2019-07-24

    …d security vulnerability

  • 4.2.0 - 2018-03-21
    • Add options.promiseValueSize for promise value. Thanks to Ryan Roemer for the pull [#84]
    • Added option deleteOnExpire
    • Added DefinitelyTyped Typescript definitions. Thanks to Ulf Seltmann for the pulls [#90] and [#92]
    • Thanks to Daniel Jin for the readme fix in pull [#93]
    • Optimized test and ci configs.
  • 4.1.1 - 2016-12-21
from node-cache 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 node-cache from 4.1.1 to 4.2.1.

See this package in npm:
node-cache

See this project in Snyk:
https://app.snyk.io/org/redlegend606/project/2f7c53a5-5128-49b0-a375-816efd480655?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.

2 participants