pm2-deploy - npm Package Compare versions

Comparing version 0.3.5 to 0.3.6

CHANGELOG.md

 
+# 0.3.6
+
+- ability to omit user in deploy_conf
+
 # 0.3.2
@@ -3,0 +7,0 @@

deploy.js

@@ -53,3 +53,22 @@ var fs = require('fs');
   if (!tv4.validate(target_conf, {
-    required: ["user", "host", "repo", "path", "ref"]
+    type: 'object',
+    properties: {
+      user: {
+        type: 'string',
+        minLength: 1,
+      },
+      host: {
+        type: ['string', 'array'],
+      },
+      repo: {
+        type: 'string',
+      },
+      path: {
+        type: 'string',
+      },
+      ref: {
+        type: 'string',
+      },
+    },
+    required: ["host", "repo", "path", "ref"],
   })) {
@@ -56,0 +75,0 @@ return cb(tv4.error);

package.json

 {
   "name": "pm2-deploy",
-  "version": "0.3.5",
+  "version": "0.3.6",
   "description": "Deployment system for PM2",
@@ -5,0 +5,0 @@ "main": "deploy.js",

New alerts

License Policy Violation

License

This package is not allowed per your license policy. Review the package's license to ensure compliance.

Found 1 instance in 1 package

Fixed alerts

License Policy Violation

License

This package is not allowed per your license policy. Review the package's license to ensure compliance.

Found 1 instance in 1 package

New author

Supply chain risk

A new npm collaborator published a version of the package for the first time. New collaborators are usually benign additions to a project, but do indicate a change to the security surface area of a package.

Found 1 instance in 1 package

Improved metrics

Total package byte prevSize

14332

increased by3.33%

Lines of code

138

increased by15.97%

Number of medium supply chain risk alerts

1

decreased by-50%

No dependency changes