An in-range update of standard is breaking the build π¨
greenkeeper opened this issue Β· 1 comments
Version 10.0.3 of standard just got published.
| Branch | Build failing π¨ |
|---|---|
| Dependency | standard |
| Current Version | 10.0.2 |
| Type | devDependency |
This version is covered by your current version range and after updating it in your project the build failed.
As standard is βonlyβ a devDependency of this project it might not break production or downstream projects, but βonlyβ your build or test tools β preventing new deploys or publishes.
I recommend you give this issue a high priority. Iβm sure you can resolve this πͺ
Status Details
- β continuous-integration/appveyor/branch AppVeyor build failed Details
Release Notes
v10.0.3- Internal changes (incremented dependency versions)
Commits
The new version differs by 99 commits.
91e80a110.0.382a0d5cchangelogd22676eMerge pull request #963 from daper/patch-1cfb84feRemove tilde to lock down eslint-config-standard-jsx version4a6e0d0Update dependecy of eslint-config-standard-jsxac9e09eMerge pull request #961 from igorsantos07/patch-1873bc9bAdding valid example for no-unsafe-negationf00b169more feross/standard -> standard/standard9770303Merge pull request #954 from standard/security8cc2285Add a security policy2fa8b0fchange more feross/standard -> standard/standarde79a692Merge branch 'devjin0617-translation-kr'34490f7Merge branch 'translation-kr' of https://github.com/devjin0617/standard into devjin0617-translation-kr6d59566Merge pull request #953 from standard/translations3895bc6move english readme/rules to docs/ folder
There are 99 commits in total.
See the full diff
Not sure how things should work exactly?
There is a collection of frequently asked questions and of course you may always ask my humans.
Your Greenkeeper Bot π΄
After pinning to 10.0.2 your tests are still failing. The reported issue might not affect your project. These imprecisions are caused by inconsistent test results.