search

Bomret / funkster-http-headers-content

Adds combinators for parsing and setting the HTTP Content-* headers in Funkster.
0 stars 0 forks source link

An in-range update of funkster-core is breaking the build 🚨 #9

Closed greenkeeper[bot] closed 7 years ago

greenkeeper[bot] commented 7 years ago

Version 0.7.2 of funkster-core just got published.

Branch Build failing 🚨
Dependency funkster-core
Current Version 0.7.1
Type devDependency

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

As funkster-core 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 :muscle:

Status Details - ❌ **continuous-integration/travis-ci/push** The Travis CI build is in progress [Details](https://travis-ci.org/Bomret/funkster-http-headers-content/builds/188134721) - ✅ **bitHound - Dependencies** No failing dependencies. [Details](https://www.bithound.io/github/Bomret/funkster-http-headers-content/48c34806e016de99ca169af5a6eb65accee274fb/dependencies/npm?status=passing) - ❌ **bitHound - Code** 2 failing files. [Details](https://www.bithound.io/github/Bomret/funkster-http-headers-content/48c34806e016de99ca169af5a6eb65accee274fb/files#filter-failing-file)
Commits

The new version differs by 12 commits .

See the full diff.

Not sure how things should work exactly? There is a collection of [frequently asked questions](https://greenkeeper.io/faq.html) and of course you may always [ask my humans](https://github.com/greenkeeperio/greenkeeper/issues/new).

Your Greenkeeper Bot :palm_tree:

greenkeeper[bot] commented 7 years ago

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