Bump qs from 0.4.2 to 6.2.3

[dependabot[bot]]

Bumps qs from 0.4.2 to 6.2.3.

Changelog

Sourced from qs's changelog.

6.2.3

• [Fix] follow allowPrototypes option during merge (#201, #200)
• [Fix] chmod a-x
• [Fix] support keys starting with brackets (#202, #200)
• [Tests] up to node v7.7, v6.10, v4.8; disable osx builds since they block linux builds

6.2.2

• [Fix] ensure that allowPrototypes: false does not ever shadow Object.prototype properties

6.2.1

• [Fix] ensure key[]=x&key[]&key[]=y results in 3, not 2, values
• [Refactor] Be explicit and use Object.prototype.hasOwnProperty.call
• [Tests] remove parallelshell since it does not reliably report failures
• [Tests] up to node v6.3, v5.12
• [Dev Deps] update tape, eslint, @ljharb/eslint-config, qs-iconv

6.2.0

• [New] pass Buffers to the encoder/decoder directly (#161)
• [New] add "encoder" and "decoder" options, for custom param encoding/decoding (#160)
• [Fix] fix compacting of nested sparse arrays (#150)

**6.1.2

• [Fix] follow allowPrototypes option during merge (#201, #200)
• [Fix] chmod a-x
• [Fix] support keys starting with brackets (#202, #200)
• [Tests] up to node v7.7, v6.10, v4.8; disable osx builds since they block linux builds

6.1.1

• [Fix] ensure that allowPrototypes: false does not ever shadow Object.prototype properties

6.1.0

• [New] allowDots option for stringify (#151)
• [Fix] "sort" option should work at a depth of 3 or more (#151)
• [Fix] Restore dist directory; will be removed in v7 (#148)

6.0.4

• [Fix] follow allowPrototypes option during merge (#201, #200)
• [Fix] chmod a-x
• [Fix] support keys starting with brackets (#202, #200)
• [Tests] up to node v7.7, v6.10, v4.8; disable osx builds since they block linux builds

6.0.3

• [Fix] ensure that allowPrototypes: false does not ever shadow Object.prototype properties
• [Fix] Restore dist directory; will be removed in v7 (#148)

6.0.2

• Revert ES6 requirement and restore support for node down to v0.8.

6.0.1

• [#127](ljharb/qs#127) Fix engines definition in package.json

... (truncated)

Commits

• See full diff in compare view

Maintainer changes

This version was pushed to npm by ljharb, a new releaser for qs since your current version.

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
• @dependabot use these labels will set the current labels as the default for future PRs for this repo and language
• @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
• @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
• @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language

You can disable automated security fix PRs for this repo from the Security Alerts page.