Bump got and npm-check-updates in /src/packages/graphql-iterator

[dependabot]

Bumps got and npm-check-updates. These dependencies needed to be updated together.
Updates got from 9.6.0 to 12.4.1

Release notes

Sourced from got's releases.

v12.4.1

Fixes

• Fix options.context being not extensible b671480715dbbff908e9a385f5e714570c663cd7
• Don't emit uploadProgress after promise cancelation 693de217b030816f574d6e4cb505ee2e77b21c29

sindresorhus/got@v12.4.0...v12.4.1

v12.4.0

Improvements

• Support FormData without known length (#2120) 850773c

Fixes

• Don't call beforeError hooks with HTTPError if the throwHttpErrors option is false (#2104) 3927348

sindresorhus/got@v12.3.1...v12.4.0

v12.3.1

• Don't freeze signal when freezing Options (#2100) 43b1467

sindresorhus/got@v12.3.0...v12.3.1

v12.3.0

• Add .off() method for events (#2092) 88056be

sindresorhus/got@v12.2.0...v12.3.0

v12.2.0

• Support AbortController (#2020) 6a6d2a9
• Add enableUnixSockets option (#2062) 461b3d4

sindresorhus/got@v12.1.0...v12.2.0

v12.1.0

Improvements

• Add response.ok (#2043) 22d58fb
  • This is only useful if you have {throwHttpErrors: false}

Fixes

• Do not redirect to UNIX sockets (#2047) 861ccd9
  • CVE-2022-33987
  • Also back ported to v11

sindresorhus/got@v12.0.4...v12.1.0

v12.0.4

... (truncated)

Commits

• 523a863 12.4.1
• 8180a53 Leave uploadProgress so it gets emitted on stream end
• 693de21 Attempt to skip emitting uploadProgress after destroy
• b671480 Fix options.context being not extensible
• 231f55d 12.4.0
• 3a1074f Build TS when testing
• 850773c Support FormData without known length (#2120)
• 5c2ff68 Add quick start guide (#2059)
• 3927348 Don't call beforeError hooks with HTTPError if the throwHttpErrors opti...
• 9f06060 Upgrade dependencies
• Additional commits viewable in compare view

Maintainer changes

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

Updates npm-check-updates from 12.5.11 to 16.1.3

Release notes

Sourced from npm-check-updates's releases.

v16.0.0

Breaking

• Automatic detection of package data on stdin has been removed. This feature was deprecated in v14.0.0. Add --stdin for old behavior. (#136)
• Wild card filters now apply to scoped packages. Previously, ncu -f '*vite*' would not include @vitejs/plugin-react. Now, filters will match any part of the package name, including the scope. Use a more specific glob or regex expression for old behavior. (#1168)

v15.0.0

Breaking

• node >= 14.14 is now required (#1145)
  • Needed to upgrade update-notifier with has a moderate severity vulnerability
• yarn autodetect has been improved (#1148)
  • This is a patch, though technically it is breaking. In the obscure case where --packageManager is not given, there is no package-lock.json in the current folder, and there is a yarn.lock in an ancestor directory, npm-check-updates will now use yarn.
  • More practically, if you needed to specify --packageManager yarn explicitly before, you may not have to now

v14.1.0

Features

Group

You can now group upgrades by risk level using --format group:

Interactive Mode

Interactive mode was completely rewritten for a better user experience.

Inspired by npm-check.

Combine with --format group for a truly luxe experience:

Static Registry

A new option --packageManager staticRegistry allows upgrades to be recommended from a static JSON file. This can be used to power custom versioning infrastructure that is completely independent from the npm registry.

Thanks to agrouse who did a fine job on the PR.

Example:

$ ncu --packageManager staticRegistry --registry ./my-registry.json

my-registry.json:

... (truncated)

Commits

• 25d28f2 16.1.3
• eb2a886 Support npm config cafile which includes a tilde (#1189)
• 3fd95e7 Fix group test dependency order.
• 8ba984e 16.1.2
• ec5386f Sort dependencies in interactive mode (#1186)
• 9b653d4 16.1.1
• fbce9cb Sort dependency table (#1186).
• d19b01d Bump dependencies
• 0465e8e 16.1.0
• 66021c4 Rename getCacher -> cache
• Additional commits viewable in compare view

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.

[dependabot]

Superseded by #47.