Skip to content

Conversation

@imskyyc
Copy link
Member

@imskyyc imskyyc commented Jun 28, 2023

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


Snyk has created this PR to upgrade pm2 from 5.2.2 to 5.3.0.

ℹ️ 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 3 months ago, on 2023-03-15.
Release notes
Package name: pm2
  • 5.3.0 - 2023-03-15
  • 5.2.2 - 2022-10-13
    • fix cluster error avoiding process restart (#5396)
    • ensure increment_var value is a number (#5435)
    • update dependencies
    • add node latest to travis testing
from pm2 GitHub release notes
Commit messages
Package name: pm2
  • c7a84c2 pm2@5.3.0
  • d61f139 Merge branch 'development'
  • 1b5e0ab Merge pull request #5533 from Sailboat265/development-flush-patch
  • 4cabf82 Merge pull request #5524 from BlueWater86/development
  • 3a6b48d hotfix: replace non-working if-else condition to use fs.existsSync while handling flush
  • ca36f30 Update ProcessContainer.js
  • 5dbb561 Update .travis.yml
  • 5278057 Merge pull request #5456 from dko-slapdash/fix-large-id-erasure-in-pm2-list
  • dcffe8d Merge branch 'development' of github.com:Unitech/pm2 into development
  • 43b638d Merge pull request #5457 from JSKitty/development
  • 0e2b65e fix other launch typos
  • 6fe3179 fix cli launching typo
  • e1e301f fix large id erasure in "pm2 list"

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

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