Skip to content

[Snyk] Upgrade node-cron from 3.0.2 to 3.0.3 #84

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

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

Conversation

Codehackerone
Copy link
Owner

This PR was automatically created by Snyk using the credentials of a real user.


Snyk has created this PR to upgrade node-cron from 3.0.2 to 3.0.3.

As this is a private repository, Snyk-bot does not have access. Therefore, this PR has been created automatically, but appears to have been created by a real user.

✨ Snyk has automatically assigned this pull request, set who gets assigned.

ℹ️ 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 1 version ahead of your current version.
  • The recommended version was released 2 months ago, on 2023-11-08.
Release notes
Package name: node-cron
  • 3.0.3 - 2023-11-08
  • 3.0.2 - 2022-08-15

    new bugfix version

from node-cron GitHub release notes
Commit messages
Package name: node-cron
  • e65a2d0 v3.0.3
  • 49fed60 Merge pull request #366 from gokulchandra/fixes-memory-leak
  • f6e2436 Merge branch 'master' into fixes-memory-leak
  • 665abde creates single instance of date formatter

Compare


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:

🧐 View latest project report

👩‍💻 Set who automatically gets assigned

🛠 Adjust upgrade PR settings

🔕 Ignore this dependency or unsubscribe from future upgrade PRs

@anuragc2001 anuragc2001 removed their assignment Jan 26, 2024
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.

3 participants