search

Elergy / nmock

HTTP mocking and expectations library for Node.js
3 stars 0 forks source link

An in-range update of qs is breaking the build 🚨 #87

Open greenkeeper[bot] opened 7 years ago

greenkeeper[bot] commented 7 years ago

Version 6.5.0 of qs just got published.

Branch Build failing 🚨
Dependency qs
Current Version 6.4.0
Type dependency

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

qs is a direct dependency of this project this is very likely breaking your project right now. If other packages depend on you it’s very likely also breaking them. I recommend you give this issue a very high priority. I’m sure you can resolve this :muscle:

Status Details - ❌ **coverage/coveralls** Coverage pending from Coveralls.io [Details](https://coveralls.io/builds/12164015) - ❌ **continuous-integration/travis-ci/push** The Travis CI build failed [Details](https://travis-ci.org/Elergy/nmock/builds/247823286?utm_source=github_status&utm_medium=notification)
Commits

The new version differs by 42 commits.

  • d66ac17 v6.5.0
  • 4d2075c [Tests] on node v8.1, v6.11
  • 0b0f272 [Dev Deps] update tape, iconv-lite
  • 229b0e9 Handle stringifying empty objects with addQueryPrefix
  • b9519c9 [Tests] add editorconfig-tools
  • e25af9b [Refactor] parse: cache index to reuse in else statement
  • f0c1480 Only apps should have lock files.
  • 4d34b8e [New] parse/stringify: add ignoreQueryPrefix/addQueryPrefix options, respectively
  • 5c09c18 [Dev Deps] update browserify
  • 9730ada [Tests] on node v8.0; npm v5+ breaks on node < v4
  • 126dcb8 [Tests] on node v7.10
  • e27c77b [Dev Deps] update iconv-lite
  • 0bc0b79 [Tests] npm v4.6 breaks on node < v1
  • 97b88ed [Docs] add various badges to readme
  • bd5009a [New] pass default encoder/decoder to custom encoder/decoder functions.

There are 42 commits in total.

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

Version 6.5.1 just got published.

Your tests are still failing with this version. Compare the changes 🚨

Commits

The new version differs by 9 commits.

  • 0e838da v6.5.1
  • 53b54cb [Refactor] name utils functions.
  • dfd28c6 [Dev Deps] update eslint, @ljharb/eslint-config, tape
  • 461a04d Merge pull request #224 from dougwilson/non-recursive-compact
  • 2ed6ea4 Fix parsing & compacting very deep objects
  • 841b933 [Tests] up to node v8.4; use nvm install-latest-npm so newer npm doesn’t break older node
  • 3be7c11 Use precise dist for Node.js 0.6 runtime
  • 489f2f8 [Tests] make 0.6 required, now that it’s passing
  • a80052d [Tests] on node v8.2; fix npm on node 0.6

See the full diff

greenkeeper[bot] commented 6 years ago

Version 6.5.2 just got published.

Your tests are still failing with this version. Compare the changes 🚨

Commits

The new version differs by 7 commits.

  • eaabd05 v6.5.2
  • 9a73e55 [Dev Deps] update browserify, eslint, iconv-lite, safer-buffer
  • 29477ba [Dev Deps] update eslint, tape, browserify
  • 73b3732 [Fix] use safer-buffer instead of Buffer constructor
  • 037f368 [Dev Deps] update eslint
  • 9dcec60 [Dev Deps] update eslint, iconv-lite
  • 6f0586f Change exports usage

See the full diff