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-resque from 7.0.2 to 7.0.3 #1442

Merged
merged 2 commits into from Apr 29, 2020

Conversation

snyk-bot
Copy link
Contributor

Snyk has created this PR to upgrade node-resque from 7.0.2 to 7.0.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 1 version ahead of your current version.
  • The recommended version was released 22 days ago, on 2020-04-06.
Release notes
Package name: node-resque
  • 7.0.3 - 2020-04-06
    • update prettier and lint rules (#331)
    • test node v13 and use redis v5 (#332)
    • Remove jobs definition of producer example (#333)
    • process.nextTick() takes callback as argument (#336)
    • Code style fixes (#338)
    • Update README.md (#339)
    • update deps (#341)
  • 7.0.2 - 2020-03-16
    • Schedule should also watch delayed_queue_schedule #329
    • Update Dependencies
from node-resque GitHub release notes
Commit messages
Package name: node-resque

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

🛠 Adjust upgrade PR settings

🔕 Ignore this dependency or unsubscribe from future upgrade PRs

@evantahler evantahler merged commit aa95921 into master Apr 29, 2020
@evantahler evantahler deleted the snyk-upgrade-d6fffc10e2e4137d803eadf06a95b757 branch April 29, 2020 21:37
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.

None yet

2 participants