search

fvdm / nodejs-haveibeenpwned

API methods for HaveIBeenPwnd.com (unofficial)
https://www.npmjs.com/package/haveibeenpwned
The Unlicense
17 stars 5 forks source link

An in-range update of dotest is breaking the build 🚨 #12

Closed greenkeeper[bot] closed 6 years ago

greenkeeper[bot] commented 6 years ago

Version 2.1.0 of dotest was just published.

Branch Build failing 🚨
Dependency dotest
Current Version 2.0.0
Type devDependency

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

dotest 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 - ✅ **bitHound - Code** No failing files. [Details](https://www.bithound.io/github/fvdm/nodejs-haveibeenpwned/4dadcbcf98543944f86ed2639849a75426209016/files?status=passing) - ✅ **bitHound - Dependencies** No failing dependencies. [Details](https://www.bithound.io/github/fvdm/nodejs-haveibeenpwned/4dadcbcf98543944f86ed2639849a75426209016/dependencies/npm?status=passing) - ❌ **continuous-integration/travis-ci/push** The Travis CI build failed [Details](https://travis-ci.org/fvdm/nodejs-haveibeenpwned/builds/315181508?utm_source=github_status&utm_medium=notification) - ✅ **coverage/coveralls** First build on greenkeeper/dotest-2.1.0 at 100.0% [Details](https://coveralls.io/builds/14611414)
Commits

The new version differs by 6 commits.

  • 3b70113 2.1.0
  • ad673a7 Docs(changelog): update changelog
  • 0dceea5 Refactor: Revert devdeps to dotest
  • d7267d8 Chore(package): Update dependencies to enable Greenkeeper (#23)
  • 67bd924 Test(config): Update Travis CI node versions
  • b6489bb Docs(readme): Replaced coffee link with a button

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 2.0.0 your tests are still failing. The reported issue might not affect your project. These imprecisions are caused by inconsistent test results.

greenkeeper[bot] commented 6 years ago

Version 2.3.0 just got published.

Your tests are passing again with this version. Explicitly upgrade to this version 🚀

Commits

The new version differs by 26 commits.

  • 8931ce1 2.3.0
  • ee0669c Docs(changelog): Update changelog
  • 4f945d2 Feat(runner): Add NSP check
  • 4b8440a Chore(package): Add nsp dependency
  • a6772a7 Style(runner): Clean up
  • 7c1d411 2.2.0
  • b920fa8 Docs(changelog): Update changelog
  • 0a62b49 Fix(done): Value was converted to seconds
  • 6fc83fb Refactor(testFunc): Rewrite to add test details
  • 4803a6c Style(syntax): Clean up
  • f7e1568 Style(syntax): Short inline functions
  • 36480a2 Refactor(log): Removed pre node v6 conditional
  • 3104d88 Test(config): Removed obsolete ecmaVersion
  • d039a04 Docs(readme): Minor tweaks and text edits
  • 5396e1f Docs(readme): Code examples in ES6 style

There are 26 commits in total.

See the full diff