search

paritytech / email-verification

e-mail verification for Parity.
https://github.com/ethcore/email-verification#parity-e-mail-verification
Other
8 stars 4 forks source link

An in-range update of config is breaking the build 🚨 #14

Open greenkeeper[bot] opened 6 years ago

greenkeeper[bot] commented 6 years ago

Version 1.31.0 of config was just published.

Branch Build failing 🚨
Dependency config
Current Version 1.30.0
Type dependency

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

config is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Status Details - ❌ **continuous-integration/travis-ci/push** The Travis CI build could not complete due to an error [Details](https://travis-ci.org/paritytech/email-verification/builds/407278569?utm_source=github_status&utm_medium=notification)
Commits

The new version differs by 12 commits.

  • a6d49e5 Bump for 1.31 release
  • 76bebd8 Merge pull request #490 from SimonSchick/chore/deps
  • ce2a291 remove unused dependency and bump up json5
  • 66bd8e1 Merge pull request #486 from leonardovillela/node-env-define-multiple-load-files
  • 7e7c9cf Fix new line at end of files
  • a27b959 Add support for load multiple files by values defined in NODE_ENV
  • 54d2f71 Merge pull request #484 from bastbijl/issue-483-support-coffeescript
  • b0126a2 Fix coffeescript to 2.2.4
  • 1964867 Fix version of coffeescript to 2.3.1
  • becba67 Remove node_js 4 from travis test
  • b16d4a5 History log
  • 2112be4 Support using coffeescript without dash

See the full diff

FAQ and help There is a collection of [frequently asked questions](https://greenkeeper.io/faq.html). If those don’t help, you can always [ask the humans behind Greenkeeper](https://github.com/greenkeeperio/greenkeeper/issues/new).

Your Greenkeeper Bot :palm_tree:

greenkeeper[bot] commented 6 years ago

After pinning to 1.30.0 your tests are still failing. The reported issue might not affect your project. These imprecisions are caused by inconsistent test results.