search

Kronos-Integration / kronos-interceptor-http-request

Interceptors to handle http requests
BSD 2-Clause "Simplified" License
0 stars 0 forks source link

An in-range update of semantic-release is breaking the build 🚨 #294

Closed greenkeeper[bot] closed 7 years ago

greenkeeper[bot] commented 7 years ago

Version 8.2.0 of semantic-release was just published.

Branch Build failing 🚨
Dependency semantic-release
Current Version 8.1.2
Type devDependency

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

semantic-release 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 - Dependencies** No failing dependencies. [Details](https://www.bithound.io/github/Kronos-Integration/kronos-interceptor-http-request/52d93badc885d4316e010e40a93380f437aced45/dependencies/npm?status=passing) - ❌ **bitHound - Code** 3 failing files. [Details](https://www.bithound.io/github/Kronos-Integration/kronos-interceptor-http-request/52d93badc885d4316e010e40a93380f437aced45/files#filter-failing-file) - ❌ **continuous-integration/travis-ci/push** The Travis CI build is in progress [Details](https://travis-ci.org/Kronos-Integration/kronos-interceptor-http-request/builds/288355456?utm_source=github_status&utm_medium=notification)
Release Notes v8.2.0

8.2.0 (2017-10-12)

Features

  • Allow to recover from ENOTINHISTORY with a tag and handle detached head repo (580ad9c)
Commits

The new version differs by 1 commits.

  • 580ad9c feat: Allow to recover from ENOTINHISTORY with a tag and handle detached head repo

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 7 years ago

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