Skip to content

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

@greenkeeper

Description

@greenkeeper

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 💪

Status Details
  • coverage/coveralls Coverage pending from Coveralls.io Details
  • continuous-integration/travis-ci/push The Travis CI build failed Details

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 and of course you may always ask my humans.


Your Greenkeeper Bot 🌴

Metadata

Metadata

Assignees

No one assigned

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions