This repository has been archived by the owner on Aug 10, 2020. It is now read-only.
Update pm2 to the latest version 🚀 #13
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
![greenkeeper[bot]](https://avatars.githubusercontent.com/in/505?s=60&v=4){kind=small}
Version 3.0.1 just got published.Update to this version instead 🚀 CommitsThe new version differs by 76 commits.
There are 76 commits in total. See the full diff |
Version 3.0.2 just got published.Update to this version instead 🚀 CommitsThe new version differs by 3 commits.
See the full diff |
Version 3.0.3 just got published.Update to this version instead 🚀 CommitsThe new version differs by 2 commits.
See the full diff |
Version 3.0.4 just got published. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Version 3.0.0 of pm2 was just published.
The version 3.0.0 is not covered by your current version range.
If you don’t accept this pull request, your project will work just like it did before. However, you might be missing out on a bunch of new features, fixes and/or performance improvements from the dependency update.
It might be worth looking into these changes and trying to get this project onto the latest version of pm2.
If you have a solid test suite and good coverage, a passing build is a strong indicator that you can take advantage of these changes directly by merging the proposed change into your project. If the build fails or you don’t have such unconditional trust in your tests, this branch is a great starting point for you to work on the update.
Commits
The new version differs by 200 commits.
47eecb9fix: README update + downgrade promptly5a17688docs: update documentation, change monitor to monita082a5fdocs: update documentation about new pm2 apm and metrics system29cccd9Merge remote-tracking branch 'origin/development'ca968cfMerge pull request #3728 from Unitech/release_3.0.09cb24ddtest: remove tests on http:transaction from apm, it was removed in apm 2.0.22e91827chore: upgrade pm2-io-apm to 2.0.264c1ac8Update README.md6392a38chore: upgrade pm2-io-apm to 2.0.1 to fix https patchingb6e0650Merge pull request #3734 from f-hj/development792cef8Fix #36696e3b45fchore: upgrade mocha to version 59459937chore: upgrades node modules66d5e06chore: display active transportdfd3d62fix: format cpu usage at rootThere are 200 commits in total.
See the full diff
FAQ and help
There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.
Your Greenkeeper bot 🌴