Skip to content
This repository has been archived by the owner on Jun 17, 2021. It is now read-only.

An in-range update of standard is breaking the build 🚨 #118

Closed
greenkeeper bot opened this issue Feb 19, 2018 · 3 comments · Fixed by #119
Closed

An in-range update of standard is breaking the build 🚨 #118

greenkeeper bot opened this issue Feb 19, 2018 · 3 comments · Fixed by #119

Comments

@greenkeeper
Copy link
Contributor

greenkeeper bot commented Feb 19, 2018

Version 11.0.0 of standard was just published.

Branch Build failing 🚨
Dependency standard
Current Version 10.0.3
Type devDependency

This version is covered by your current version range and after updating it in your project the build failed.

standard is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details
  • continuous-integration/travis-ci/push The Travis CI build failed Details
  • coverage/coveralls First build on greenkeeper/standard-11.0.0 at 99.17% Details

Commits

The new version differs by 50 commits.

There are 50 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 🌴

@greenkeeper
Copy link
Contributor Author

greenkeeper bot commented Feb 19, 2018

After pinning to 10.0.3 your tests are passing again. Downgrade this dependency 📌.

@axic
Copy link
Member

axic commented Feb 20, 2018

The actual failure:

standard: Use JavaScript Standard Style (https://standardjs.com)
standard: Run `standard --fix` to automatically fix some problems.
  /home/travis/build/ethereumjs/ethereumjs-util/test/defineFields.js:32:1: Expected indentation of 4 spaces but found 6.

@holgerd77
Copy link
Member

@axic Will be fixed with https://github.com/ethereumjs/ethereumjs-util/pull/119/files. You can also review if you want to.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants