-
-
Notifications
You must be signed in to change notification settings - Fork 429
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix: update "please-upgrade-node" to version 3.0.2 #434
fix: update "please-upgrade-node" to version 3.0.2 #434
Conversation
Includes semantic version range checking that avoids incorrect flagging of Node.js version 10+
Codecov Report
@@ Coverage Diff @@
## master #434 +/- ##
=======================================
Coverage 98.18% 98.18%
=======================================
Files 11 11
Lines 220 220
Branches 25 25
=======================================
Hits 216 216
Misses 4 4 Continue to review full report at Codecov.
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Released in v7.0.5 🎉 |
lint-staged/lint-staged#434 Includes semantic version range checking that avoids incorrect flagging of Node.js version 10+. typicode/please-upgrade-node#11 E.g.: ``` node --version v10.3.0 ``` and: ``` git commit -m "fix(html reporter): toggle visibility in IE11" src/lib/reporters/Html.ts lint-staged requires at least version 6 of Node, please upgrade pre-commit: pre-commit: We've failed to pass the specified git pre-commit hooks as the `precommit` pre-commit: hook returned an exit code (1). If you're feeling adventurous you can pre-commit: skip the git pre-commit hooks by adding the following flags to your commit: pre-commit: pre-commit: git commit -n (or --no-verify) pre-commit: pre-commit: This is ill-advised since the commit is broken. pre-commit: ```
lint-staged/lint-staged#434 Includes semantic version range checking that avoids incorrect flagging of Node.js version 10+. typicode/please-upgrade-node#11 E.g.: ``` node --version v10.3.0 ``` incorrectly causes: ``` git commit -m "fix(html reporter): toggle visibility in IE11" src/lib/reporters/Html.ts lint-staged requires at least version 6 of Node, please upgrade pre-commit: pre-commit: We've failed to pass the specified git pre-commit hooks as the `precommit` pre-commit: hook returned an exit code (1). If you're feeling adventurous you can pre-commit: skip the git pre-commit hooks by adding the following flags to your commit: pre-commit: pre-commit: git commit -n (or --no-verify) pre-commit: pre-commit: This is ill-advised since the commit is broken. pre-commit: ```
lint-staged/lint-staged#434 Includes semantic version range checking that avoids incorrect flagging of Node.js version 10+. typicode/please-upgrade-node#11 E.g.: ``` node --version v10.3.0 ``` incorrectly causes: ``` git commit -m "fix(html reporter): toggle visibility in IE11" src/lib/reporters/Html.ts lint-staged requires at least version 6 of Node, please upgrade pre-commit: pre-commit: We've failed to pass the specified git pre-commit hooks as the `precommit` pre-commit: hook returned an exit code (1). If you're feeling adventurous you can pre-commit: skip the git pre-commit hooks by adding the following flags to your commit: pre-commit: pre-commit: git commit -n (or --no-verify) pre-commit: pre-commit: This is ill-advised since the commit is broken. pre-commit: ```
Includes semantic version range checking that avoids incorrect flagging of Node.js version 10+. typicode/please-upgrade-node#11
Resolves #432
Edit: Closes #433