Enforce matching engines on npm install (#481)

Co-authored-by: Sindre Sorhus <sindresorhus@gmail.com>
Co-authored-by: Itai Steinherz <itaisteinherz@gmail.com>

readme.md

@@ -22,6 +22,7 @@
 - Ensures you are publishing from the `master` branch
 - Ensures the working directory is clean and that there are no unpulled changes
 - Reinstalls dependencies to ensure your project works with the latest dependency tree
+- Ensures your Node.js and npm versions are supported by the project and its dependencies
 - Runs the tests
 - Bumps the version in package.json and npm-shrinkwrap.json (if present) and creates a git tag
 - Prevents [accidental publishing](https://github.com/npm/npm/issues/13248) of pre-release versions under the `latest` [dist-tag](https://docs.npmjs.com/cli/dist-tag)

source/index.js

@@ -140,7 +140,7 @@ module.exports = async (input = 'patch', options) => {
 				enabled: () => options.yarn === false,
 				task: () => {
 					const args = hasLockFile ? ['ci'] : ['install', '--no-package-lock', '--no-production'];
-					return exec('npm', args);
+					return exec('npm', [...args, '--engine-strict']);
 				}
 			}
 		]);