Bump cacheable-request, @antora/site-generator-default and npm-check-updates in /doc-sites

[dependabot]

Bumps cacheable-request to 10.2.7 and updates ancestor dependencies cacheable-request, @antora/site-generator-default and npm-check-updates. 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: jaredwray/cacheable@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: jaredwray/cacheable@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: jaredwray/cacheable@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 @antora/site-generator-default from 2.3.4 to 3.1.2

Changelog

Sourced from @​antora/site-generator-default's changelog.

== 3.1.2 (2022-10-28)

=== Fixed

• playbook-builder: Decouple logic to compute default log format from process environment (#1022)
• playbook-builder: Allow content aggregator to parse value of content.branches and content.tags playbook keys (#1025)
• content-aggregator: Fix infinite auth loop if credentials embedded in content source URL are empty and repository requires auth (#1010)
• content-aggregator: Fix crash if value of worktrees key on content source is ~ (null) and at least one branch is specified (#1018)
• content-classifier: Add guard to prevent ContentCatalog#registerSiteStartPage from registering alias loop (#1020)
• redirect-producer: Preserve target when creating static route if target is an absolute URL (#1024)
• site-generator: Look for IS_TTY on playbook.env in site generator to decouple check from process environment
• release process: Automatically populate version and release attributes during release (#1011)

== 3.1.1 (2022-09-20)

=== Changed

• logger: Use pretty log format by default if IS_TTY environment variable is set to true (#1004)
• site-generator: Print success message if IS_TTY environment variable is set to true (#1004)

=== Fixed

• asciidoc-loader: Define public export @antora/asciidoc-loader/include/resolve-include-file for requiring resolveIncludeFile function
• asciidoc-loader: Prevent message from ignored log message from overwriting message from next reported log message (#1003)
• site-generator: Don't require custom output provider to return a report object
• cli: If logger cannot be found, print error message to stderr instead of crashing during shutdown

== 3.1.0 (2022-08-22)

=== Added

• logger: Add reftype key with value of branch or tag to source object in structured log message (#988)
• logger: Add remote key with value of remote tracking branch to source object in structured log message, if applicable (#988)
• logger: Add local key with path of local repository to source object in structured log message, if applicable (#988)
• playbook-builder: Resolve attribute references in value of AsciiDoc attribute defined in playbook (#981)
• playbook-builder: Honor escaped attribute references in value of AsciiDoc attribute defined in playbook (#989)
• content-aggregator: Add reftype property to origin object to explicitly identify type of ref (branch or tag) (#988)
• content-aggregator: Add remote property to origin object to identify a remote tracking branch (#988)
• content-aggregator: Add origins property containing unique origin objects to each entry in content aggregate (#978)
• content-aggregator: Attach parsed component version descriptor to descriptor property on origin object (#525)
• content-aggregator: Log info message if no references are found for content source (#221)
• ui-loader: Include target in error message for broken or cyclic symbolic link (#900)
• ui-loader: Add removeFile method to UiCatalog for removing file (#814)
• content-classifier: Resolve attribute references in value of AsciiDoc attribute defined in component descriptor (#981)
• content-classifier: Honor escaped attribute references in value of AsciiDoc attribute defined in component descriptor (#989)
• content-classifier: Add removeFile method to ContentCatalog for removing file (#814)
• asciidoc-loader: Define page-component-latest-version attribute with value of version string from latest component version (#921)
• asciidoc-loader: Define boolean page-component-version-is-latest attribute if page is in latest version of component (#921)
• asciidoc-loader: Assign edit URL of current page, if set, to page-edit-url attribute (#354)
• asciidoc-loader: Define boolean page-origin-private attribute if origin of page is private (#354)

... (truncated)

Commits

• f09e3ac release 3.1.2
• 937c40c upgrade dependencies that can be upgraded and refresh dependency lock file
• 5af8e49 refresh dependency lock file
• cdd7223 update release process; automate management of release and tool version attri...
• a8d8e72 merge !964
• 911ae54 update What's New for Antora 3.1.2
• f6fc688 replace raise event with emit event
• 1975bd2 backport fix for #1025 allow content aggregator to parse value of content.bra...
• 7a39895 reclassify CHANGELOG entries
• 34ac3e2 backport fix for #1024 preserve target when creating static route if target i...
• Additional commits viewable in compare view

Updates npm-check-updates from 7.0.2 to 16.7.4

Release notes

Sourced from npm-check-updates's releases.

v16.4.0

Feature

Added --cacheClear option for—you guessed it—clearing the cache 🫥.

This brings the suite of cache-related options to:

• --cache : Cache versions to the cache file.
• --cacheClear : Clear the default cache, or the cache file specified by --cacheFile.
• --cacheExpiration <min> : Cache expiration in minutes (default: 10).
• --cacheFile <path> : Filepath for the cache file (default: "~/.ncu-cache.json").

Thanks to @​ly3xqhl8g9 whose code is gratefully more lucid than his username.

v16.3.0

Feature

• Added workspace support! 🚢

Upgrade all workspaces:

ncu --workspaces
ncu -ws

Upgrade a single workspace:

ncu --workspace a
ncu -w a

Upgrade more than one workspace:

ncu --workspace a --workspace b
ncu -w a -w b

Upgrade all workspaces AND the root project:

ncu --workspaces --root

Upgrade a single workspace AND the root project:

ncu --workspace a --root
</tr></table> 

... (truncated)

Changelog

Sourced from npm-check-updates's changelog.

Changelog

This file documents all major version releases. For other releases, please read the commit history.

[16.0.0] - 2022-07-23

Breaking

• Automatic detection of package data on stdin has been removed. This feature was deprecated in v14.0.0. Add --stdin for old behavior.
• 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.

raineorshine/npm-check-updates@v15.3.4...v16.0.0

[15.0.0] - 2022-06-30

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

raineorshine/npm-check-updates@v14.1.1...v15.0.0

[14.0.0] - 2022-06-16

Breaking

Prerelease versions are now "upgraded" to versions with a different preid.

For example, if you have a dependency at 1.3.3-next.1 and the version fetched by ncu is 1.2.3-dev.2, ncu will suggest an "upgrade" to 1.2.3-dev.2. This is because prerelease versions with different preids are incomparable. Since they are incomparable, ncu now assumes the fetched version is desired.

Since this change affects only prereleases, there is no impact on default ncu usage that fetches the latest version. With --pre 1 or --target newest or --target greatest, this change could affect which version is suggested if versions with different preids are published. The change was made to support the new --target @[tag] feature.

If you have a use case where this change is not what is desired, please report an issue. The intention is for zero disruption to current usage.

Features

• You can now upgrade to a specific tag, e.g. --target @next. Thanks to IMalyugin.

raineorshine/npm-check-updates@v13.1.5...v14.0.0

[13.0.0] - 2022-05-15

Breaking

• node >= 14 is now required
• Several options which have long been deprecated have been removed:
  • --greatest - Instead use --target greatest

... (truncated)

Commits

• b391673 16.7.4
• 2b140bc Remove install hint from deno mode.
• 3bd1e5c 16.7.3
• fdf68f2 Add jsonc support for deno config.
• 9e73471 16.7.2
• 9cdc0ad Bump dependencies
• 8c25aac 16.7.1
• 38c4053 Re-add patch target for pnpm (#1268).
• d925a0e 16.7.0
• 3cab70a Add support for deno (#1267)
• 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.