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 ts-node is breaking the build 🚨 #8

Closed greenkeeper[bot] closed 7 years ago

greenkeeper[bot] commented 7 years ago

Version 1.7.3 of ts-node just got published.

Branch Build failing 🚨
Dependency ts-node
Current Version 1.7.2
Type devDependency

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

As ts-node 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/186989052) - ❌ **bitHound - Code** 2 failing files. [Details](https://www.bithound.io/github/Bomret/funkster-http-headers-content/2f0331c34c15fb3a7bb6e5cbc86ee9cb1d65ddad/files#filter-failing-file) - ✅ **bitHound - Dependencies** No failing dependencies. [Details](https://www.bithound.io/github/Bomret/funkster-http-headers-content/2f0331c34c15fb3a7bb6e5cbc86ee9cb1d65ddad/dependencies/npm?status=passing)
Release Notes `--preserve-symlinks`

Added

  • Pass through --preserve-symlinks flag to node.js
Commits

The new version differs by 3 commits .

  • b2e6990 v1.7.3
  • bcc1ff4 Pass through --preserve-symlinks flag (#253)
  • 42e5c19 Add more info about programmatic usage (#251)

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