Bump cacheable-request and update-notifier

[dependabot]

Bumps cacheable-request to 10.2.7 and updates ancestor dependency update-notifier. These dependencies need to be updated together.

Updates cacheable-request from 6.1.0 to 10.2.7

Release notes

Sourced from cacheable-request's releases.

v10.2.6

Fix for memory leak on Listeners

The listener was not being removed on response and just error but new handlers were being added causing a memory leak.

line 220 in src/index.ts was modified to remove the listener on response also

			if (this.cache instanceof Keyv) {
				const cachek = this.cache;
				cachek.once('error', errorHandler);
				ee.on('error', () => cachek.removeListener('error', errorHandler));
				ee.on('response', () => cachek.removeListener('error', errorHandler));
			}

What's Changed

• upgrading jest and components to latest by @​jaredwray in jaredwray/cacheable-request#220
• upgrading @​types/jest to 29.2.6 by @​jaredwray in jaredwray/cacheable-request#221
• fixing listener memory leak - issue #222 by @​jaredwray in jaredwray/cacheable-request#223

Full Changelog: https://github.com/jaredwray/cacheable-request/compare/v10.2.5...v10.2.6

v10.2.5

Types definition issue with http-cache-sematics as that type definition needs to be in dependencies. Thanks @​Maxim-Mazurok

What's Changed

• Move @​types/http-cache-semantics from dev to deps by @​Maxim-Mazurok in jaredwray/cacheable-request#219

Full Changelog: https://github.com/jaredwray/cacheable-request/compare/v10.2.4...v10.2.5

v10.2.4

Minor updates with one exception is that we removed @types/http-cache-semantics from the main dependencies as it does not look to be needed.

What's Changed

• upgrading typescript to 4.9.4 by @​jaredwray in jaredwray/cacheable-request#214
• upgrading jest types and eslint for jest to latest by @​jaredwray in jaredwray/cacheable-request#215
• upgrading sqlite3 to 5.1.4 by @​jaredwray in jaredwray/cacheable-request#216
• removing @​types/http-cache-semantics from the dependencies and moving… by @​jaredwray in jaredwray/cacheable-request#217

Full Changelog: https://github.com/jaredwray/cacheable-request/compare/v10.2.3...v10.2.4

v10.2.3 Maintenance Release

Upgrading core modules in the system such as keyv and also a minor fix to an uncaught exception that we were seeing referenced here: sindresorhus/got#1925

Additional update is moving normalize-url to 8.0.0 which after testing it looks to not affect anything but will post the release notes here: https://github.com/sindresorhus/normalize-url/releases/tag/v8.0.0

... (truncated)

Commits

• See full diff in compare view

Maintainer changes

This version was pushed to npm by jaredwray, a new releaser for cacheable-request since your current version.

Updates update-notifier from 4.0.0 to 6.0.2

Release notes

Sourced from update-notifier's releases.

v6.0.2

• Fix license d152f85

sindresorhus/update-notifier@v6.0.1...v6.0.2

v6.0.1

• Update dependencies (#222) 3f7c9f3

sindresorhus/update-notifier@v6.0.0...v6.0.1

v6.0.0

Breaking

• Require Node.js 14 9183541
• This package is now pure ESM. Please read this.

sindresorhus/update-notifier@v5.1.0...v6.0.0

v5.1.0

• Upgrade dependencies 73c391b

sindresorhus/update-notifier@v5.0.1...v5.1.0

v5.0.1

• Update dependencies 9e2b772

sindresorhus/update-notifier@v5.0.0...v5.0.1

v5.0.0

Breaking

• Require Node.js 10 5b440c2

Fixes

• Don't suggest to upgrade to lower version (#192) 3dfe42d

sindresorhus/update-notifier@v4.1.1...v5.0.0

v4.1.1

• Improve vertical alignment of the notifier output (#183) f42fc8f

sindresorhus/update-notifier@v4.1.0...v4.1.1

v4.1.0

• Add template support for the message option (#175) adbeb6e

sindresorhus/update-notifier@v4.0.0...v4.1.0

Commits

• 3b6b9b1 6.0.2
• d152f85 Fix license
• 020613b 6.0.1
• 3f7c9f3 Update dependencies (#222)
• 311557e 6.0.0
• 9183541 Require Node.js 14 and move to ESM
• 3fdb218 5.1.0
• 73c391b Upgrade dependencies
• 0a6027e Move to GitHub Actions
• d8fa601 Rename master branch to main
• 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]

OK, I won't notify you again about this release, but will get in touch when a new version is available.

If you change your mind, just re-open this PR and I'll resolve any conflicts on it.