search

pksunkara / octonode

github api v3 in nodejs
MIT License
1.19k stars 237 forks source link

Update nock requirement from ^10.0.0 to ^11.3.2 #331

Closed dependabot-preview[bot] closed 5 years ago

dependabot-preview[bot] commented 5 years ago

Updates the requirements on nock to permit the latest version.

Release notes *Sourced from [nock's releases](https://github.com/nock/nock/releases).* > ## v11 > ## Upgrading from Nock 10 to Nock 11 > > ### Bug fixes and internal improvements > > Nock 11 includes many under-the-hood improvements, including a fully offline > test suite and 100% test coverage. The codebase was also converted to ES6 > syntax and formatted with Prettier. Leaning on the test coverage, some > substantial refactors have begun. > > Many bug fixes are included. See the detailed changelog below or the > [compare view][compare] for details. > > ### Fabulous new features for developers > > 1. The library ships with TypeScript definitions. (Added in v11.3) > 1. Add support for the `http.request` signatures added in Node 10.9 > 1. Scopes can be filtered using the system environment or any external factor > using e.g. `.conditionally(() => true)` > 1. In-flight modifications to headers are preserved in mock requests. > 1. Recorded mocks can be stringified using custom code in the `afterRecord()` > post-processing hook. When `afterRecord()` returns a string, the > recorder will no longer attempt to re-stringify it. (Added in v11.3) > 1. Reply functions passed to `.reply()` can now be async/promise-returning. > 1. Specifying reply headers, either via `.reply()` or `.defaultReplyHeaders()`, > can now be done consistently using an object, Map, or flat array. > > ### Breaking changes > > For many developers no code changes will be needed. However, there are several > minor changes to the API, and it's possible that you will need to update your > code for Nock to keep working properly. It's unlikely that your tests will > falsely pass; what's more probable is that your tests will fail until the > necessary changes are made. > > 1. Nock 11 requires Node 8 or later. Nock supports and tests all the "current" > and "maintenance" versions of Node. As of now, that's Node 8, 10, and 12. > > 1. In Nock 10, when `reply()` was invoked with a function, the return values were > handled ambiguously depending on their types. > > Consider the following example: > > ```js > const scope = nock('http://example.com') > .get('/') > .reply(200, () => [500, 'hello world']) > ``` > > In Nock 10, the 200 was ignored, the 500 was interpreted as the status > ... (truncated)
Commits - [`9d5cda0`](https://github.com/nock/nock/commit/9d5cda02efac32967babc8264bb4ae61795ad88d) docs(README): adapt badges for [@​latest](https://github.com/latest) release - [`cfc129c`](https://github.com/nock/nock/commit/cfc129c6bb9e37e1f1067898cbf74d09ec6b2c2c) chore(deps): bump eslint-utils from 1.4.0 to 1.4.2 ([#1698](https://github-redirect.dependabot.com/nock/nock/issues/1698)) - [`21733b4`](https://github.com/nock/nock/commit/21733b4d9aecd1664d9f604cfee7231d52b8596b) refactor: Remove the last of the real hostnames ([#1691](https://github-redirect.dependabot.com/nock/nock/issues/1691)) - [`f00f0f3`](https://github.com/nock/nock/commit/f00f0f3f3cc2eb2c27bc470a85c476e922b35792) test: Replace test_s3 with test of `Expect: 100-continue` ([#1690](https://github-redirect.dependabot.com/nock/nock/issues/1690)) - [`b83e720`](https://github.com/nock/nock/commit/b83e7207aa71635b0fcadbb24e3768953807eb50) fix(types): use export = and declares ([#1695](https://github-redirect.dependabot.com/nock/nock/issues/1695)) - [`66799f3`](https://github.com/nock/nock/commit/66799f312da5f46769ba521cab72d4f95f528c8b) refactor: Refactor net connect tests ([#1688](https://github-redirect.dependabot.com/nock/nock/issues/1688)) - [`dafa35b`](https://github.com/nock/nock/commit/dafa35bd5ed49f09178db822d1d0080f8ee79893) docs: Add "Common issues" section documenting got automatic retrying ([#1687](https://github-redirect.dependabot.com/nock/nock/issues/1687)) - [`11a9517`](https://github.com/nock/nock/commit/11a9517c64ca82aa645e2fcdf4a50d27020f77bc) style: Minor style improvements ([#1693](https://github-redirect.dependabot.com/nock/nock/issues/1693)) - [`50c821b`](https://github.com/nock/nock/commit/50c821b036c5b33bf8faf1e13ca9bfb56c8f283b) test: Add todo test for conflict between hostnames ([#1109](https://github-redirect.dependabot.com/nock/nock/issues/1109)) - [`a334e92`](https://github.com/nock/nock/commit/a334e920459df2865c5883405b7b067045f4a630) fix: add extension to main field in package.json ([#1683](https://github-redirect.dependabot.com/nock/nock/issues/1683)) - Additional commits viewable in [compare view](https://github.com/nock/nock/compare/v10.0.0...v11.3.2)


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 - `@dependabot badge me` will comment on this PR with code to add a "Dependabot enabled" badge to your readme Additionally, you can set the following in your Dependabot [dashboard](https://app.dependabot.com): - Update frequency (including time of day and day of week) - Automerge options (never/patch/minor, and dev/runtime dependencies) - Pull request limits (per update run and/or open at any time) - Out-of-range updates (receive only lockfile updates, if desired) - Security updates (receive only security updates, if desired) Finally, you can contact us by mentioning @dependabot.