Skip to content
This repository has been archived by the owner on Nov 1, 2020. It is now read-only.

[Snyk] Upgrade pm2 from 4.2.1 to 4.2.3 #9

Merged
merged 2 commits into from
Apr 9, 2020

Conversation

snyk-bot
Copy link
Contributor

Snyk has created this PR to upgrade pm2 from 4.2.1 to 4.2.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 2 versions ahead of your current version.
  • The recommended version was released 2 months ago, on 2020-01-21.
Release notes
Package name: pm2
  • 4.2.3 - 2020-01-21
    • fix: Fix an import error on Node 9.x
  • 4.2.2 - 2020-01-20
    • feat: Support ESM on Node 13 via .mjs file or "type":"module" in package.json #4540
    • fix: Fix an error for pm2 path on Windows. #4563
  • 4.2.1 - 2019-12-10
    • fix: col size too small for certain app name with tracing enabled
    • chore: check for pm2 updates
from pm2 GitHub release notes
Commit messages
Package name: pm2
  • 6e9bb1e pm2@4.2.3
  • 278d4b2 fix: #4588 import syntax on Node 9.x
  • 535b847 add travis test for node 9
  • c4b06ef pm2@4.2.2
  • fda26d0 Merge pull request #4563 from kimhc999/fix/get-pm2-path-fix
  • cafc8e5 fix: look for package.json in parent folder
  • 5166826 chore: avoid token exception on Node < 9.x
  • 15a7559 chore: skip es module check if <13.3
  • 0d44c41 feat: #4540 support ES import
  • 0b8bc19 Fix an error for pm2 path on Windows.

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

@hrueger hrueger merged commit 2ee179a into master Apr 9, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants