dependabot[bot] opened a new pull request, #32: URL: https://github.com/apache/james-site/pull/32
Bumps [cacheable-request](https://github.com/jaredwray/cacheable-request) to 10.2.7 and updates ancestor dependencies [cacheable-request](https://github.com/jaredwray/cacheable-request), [@antora/site-generator-default](https://gitlab.com/antora/antora) and [npm-check-updates](https://github.com/raineorshine/npm-check-updates). These dependencies need to be updated together. Updates `cacheable-request` from 6.1.0 to 10.2.7 <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/jaredwray/cacheable-request/releases">cacheable-request's releases</a>.</em></p> <blockquote> <h2>v10.2.6</h2> <h1>Fix for memory leak on Listeners</h1> <p>The listener was not being removed on <code>response</code> and just error but new handlers were being added causing a memory leak.</p> <p><a href="https://github.com/jaredwray/cacheable-request/blob/c4815689be40854a3d748a3927959354c09b0ebb/src/index.ts#L220-L225">line 220 in src/index.ts was modified to remove the listener on response also </a></p> <pre><code> 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)); } </code></pre> <h2>What's Changed</h2> <ul> <li>upgrading jest and components to latest by <a href="https://github.com/jaredwray"><code>@jaredwray</code></a> in <a href="https://github-redirect.dependabot.com/jaredwray/cacheable-request/pull/220">jaredwray/cacheable-request#220</a></li> <li>upgrading <code>@types/jest</code> to 29.2.6 by <a href="https://github.com/jaredwray"><code>@jaredwray</code></a> in <a href="https://github-redirect.dependabot.com/jaredwray/cacheable-request/pull/221">jaredwray/cacheable-request#221</a></li> <li>fixing listener memory leak - issue <a href="https://github-redirect.dependabot.com/jaredwray/cacheable-request/issues/222">#222</a> by <a href="https://github.com/jaredwray"><code>@jaredwray</code></a> in <a href="https://github-redirect.dependabot.com/jaredwray/cacheable-request/pull/223">jaredwray/cacheable-request#223</a></li> </ul> <p><strong>Full Changelog</strong>: <a href="https://github.com/jaredwray/cacheable-request/compare/v10.2.5...v10.2.6">https://github.com/jaredwray/cacheable-request/compare/v10.2.5...v10.2.6</a></p> <h2>v10.2.5</h2> <p>Types definition issue with http-cache-sematics as that type definition needs to be in dependencies. Thanks <a href="https://github.com/Maxim-Mazurok"><code>@Maxim-Mazurok</code></a></p> <h2>What's Changed</h2> <ul> <li>Move <code>@types/http-cache-semantics</code> from dev to deps by <a href="https://github.com/Maxim-Mazurok"><code>@Maxim-Mazurok</code></a> in <a href="https://github-redirect.dependabot.com/jaredwray/cacheable-request/pull/219">jaredwray/cacheable-request#219</a></li> </ul> <p><strong>Full Changelog</strong>: <a href="https://github.com/jaredwray/cacheable-request/compare/v10.2.4...v10.2.5">https://github.com/jaredwray/cacheable-request/compare/v10.2.4...v10.2.5</a></p> <h1>v10.2.4</h1> <p>Minor updates with one exception is that we removed <code>@types/http-cache-semantics</code> from the main dependencies as it does not look to be needed.</p> <h2>What's Changed</h2> <ul> <li>upgrading typescript to 4.9.4 by <a href="https://github.com/jaredwray"><code>@jaredwray</code></a> in <a href="https://github-redirect.dependabot.com/jaredwray/cacheable-request/pull/214">jaredwray/cacheable-request#214</a></li> <li>upgrading jest types and eslint for jest to latest by <a href="https://github.com/jaredwray"><code>@jaredwray</code></a> in <a href="https://github-redirect.dependabot.com/jaredwray/cacheable-request/pull/215">jaredwray/cacheable-request#215</a></li> <li>upgrading sqlite3 to 5.1.4 by <a href="https://github.com/jaredwray"><code>@jaredwray</code></a> in <a href="https://github-redirect.dependabot.com/jaredwray/cacheable-request/pull/216">jaredwray/cacheable-request#216</a></li> <li>removing <code>@types/http-cache-semantics</code> from the dependencies and moving… by <a href="https://github.com/jaredwray"><code>@jaredwray</code></a> in <a href="https://github-redirect.dependabot.com/jaredwray/cacheable-request/pull/217">jaredwray/cacheable-request#217</a></li> </ul> <p><strong>Full Changelog</strong>: <a href="https://github.com/jaredwray/cacheable-request/compare/v10.2.3...v10.2.4">https://github.com/jaredwray/cacheable-request/compare/v10.2.3...v10.2.4</a></p> <h1>v10.2.3 Maintenance Release</h1> <p>Upgrading core modules in the system such as keyv and also a minor fix to an uncaught exception that we were seeing referenced here: <a href="https://github-redirect.dependabot.com/sindresorhus/got/issues/1925">sindresorhus/got#1925</a></p> <p>Additional update is moving <code>normalize-url</code> to <code>8.0.0</code> which after testing it looks to not affect anything but will post the release notes here: <a href="https://github.com/sindresorhus/normalize-url/releases/tag/v8.0.0">https://github.com/sindresorhus/normalize-url/releases/tag/v8.0.0</a></p> <!-- raw HTML omitted --> </blockquote> <p>... (truncated)</p> </details> <details> <summary>Commits</summary> <ul> <li>See full diff in <a href="https://github.com/jaredwray/cacheable-request/commits">compare view</a></li> </ul> </details> <details> <summary>Maintainer changes</summary> <p>This version was pushed to npm by <a href="https://www.npmjs.com/~jaredwray">jaredwray</a>, a new releaser for cacheable-request since your current version.</p> </details> <br /> Updates `@antora/site-generator-default` from 2.3.4 to 3.1.2 <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://gitlab.com/antora/antora/blob/main/CHANGELOG.adoc"><code>@antora/site-generator-default</code>'s changelog</a>.</em></p> <blockquote> <p>== 3.1.2 (2022-10-28)</p> <p>=== Fixed</p> <ul> <li><em>playbook-builder</em>: Decouple logic to compute default log format from process environment (<a href="https://gitlab.com/antora/antora/issues/1022">#1022</a>)</li> <li><em>playbook-builder</em>: Allow content aggregator to parse value of <code>content.branches</code> and <code>content.tags</code> playbook keys (<a href="https://gitlab.com/antora/antora/issues/1025">#1025</a>)</li> <li><em>content-aggregator</em>: Fix infinite auth loop if credentials embedded in content source URL are empty and repository requires auth (<a href="https://gitlab.com/antora/antora/issues/1010">#1010</a>)</li> <li><em>content-aggregator</em>: Fix crash if value of <code>worktrees</code> key on content source is <code>~</code> (<code>null</code>) and at least one branch is specified (<a href="https://gitlab.com/antora/antora/issues/1018">#1018</a>)</li> <li><em>content-classifier</em>: Add guard to prevent <code>ContentCatalog#registerSiteStartPage</code> from registering alias loop (<a href="https://gitlab.com/antora/antora/issues/1020">#1020</a>)</li> <li><em>redirect-producer</em>: Preserve target when creating static route if target is an absolute URL (<a href="https://gitlab.com/antora/antora/issues/1024">#1024</a>)</li> <li><em>site-generator</em>: Look for IS_TTY on <code>playbook.env</code> in site generator to decouple check from process environment</li> <li>release process: Automatically populate version and release attributes during release (<a href="https://gitlab.com/antora/antora/issues/1011">#1011</a>)</li> </ul> <p>== 3.1.1 (2022-09-20)</p> <p>=== Changed</p> <ul> <li><em>logger</em>: Use pretty log format by default if <code>IS_TTY</code> environment variable is set to <code>true</code> (<a href="https://gitlab.com/antora/antora/issues/1004">#1004</a>)</li> <li><em>site-generator</em>: Print success message if <code>IS_TTY</code> environment variable is set to <code>true</code> (<a href="https://gitlab.com/antora/antora/issues/1004">#1004</a>)</li> </ul> <p>=== Fixed</p> <ul> <li><em>asciidoc-loader</em>: Define public export <code>@antora/asciidoc-loader/include/resolve-include-file</code> for requiring <code>resolveIncludeFile</code> function</li> <li><em>asciidoc-loader</em>: Prevent message from ignored log message from overwriting message from next reported log message (<a href="https://gitlab.com/antora/antora/issues/1003">#1003</a>)</li> <li><em>site-generator</em>: Don't require custom output provider to return a report object</li> <li><em>cli</em>: If logger cannot be found, print error message to stderr instead of crashing during shutdown</li> </ul> <p>== 3.1.0 (2022-08-22)</p> <p>=== Added</p> <ul> <li><em>logger</em>: Add <code>reftype</code> key with value of branch or tag to source object in structured log message (<a href="https://gitlab.com/antora/antora/issues/988">#988</a>)</li> <li><em>logger</em>: Add <code>remote</code> key with value of remote tracking branch to source object in structured log message, if applicable (<a href="https://gitlab.com/antora/antora/issues/988">#988</a>)</li> <li><em>logger</em>: Add <code>local</code> key with path of local repository to source object in structured log message, if applicable (<a href="https://gitlab.com/antora/antora/issues/988">#988</a>)</li> <li><em>playbook-builder</em>: Resolve attribute references in value of AsciiDoc attribute defined in playbook (<a href="https://gitlab.com/antora/antora/issues/981">#981</a>)</li> <li><em>playbook-builder</em>: Honor escaped attribute references in value of AsciiDoc attribute defined in playbook (<a href="https://gitlab.com/antora/antora/issues/989">#989</a>)</li> <li><em>content-aggregator</em>: Add <code>reftype</code> property to origin object to explicitly identify type of ref (branch or tag) (<a href="https://gitlab.com/antora/antora/issues/988">#988</a>)</li> <li><em>content-aggregator</em>: Add <code>remote</code> property to origin object to identify a remote tracking branch (<a href="https://gitlab.com/antora/antora/issues/988">#988</a>)</li> <li><em>content-aggregator</em>: Add <code>origins</code> property containing unique origin objects to each entry in content aggregate (<a href="https://gitlab.com/antora/antora/issues/978">#978</a>)</li> <li><em>content-aggregator</em>: Attach parsed component version descriptor to <code>descriptor</code> property on origin object (<a href="https://gitlab.com/antora/antora/issues/525">#525</a>)</li> <li><em>content-aggregator</em>: Log info message if no references are found for content source (<a href="https://gitlab.com/antora/antora/issues/221">#221</a>)</li> <li><em>ui-loader</em>: Include target in error message for broken or cyclic symbolic link (<a href="https://gitlab.com/antora/antora/issues/900">#900</a>)</li> <li><em>ui-loader</em>: Add <code>removeFile</code> method to <code>UiCatalog</code> for removing file (<a href="https://gitlab.com/antora/antora/issues/814">#814</a>)</li> <li><em>content-classifier</em>: Resolve attribute references in value of AsciiDoc attribute defined in component descriptor (<a href="https://gitlab.com/antora/antora/issues/981">#981</a>)</li> <li><em>content-classifier</em>: Honor escaped attribute references in value of AsciiDoc attribute defined in component descriptor (<a href="https://gitlab.com/antora/antora/issues/989">#989</a>)</li> <li><em>content-classifier</em>: Add <code>removeFile</code> method to <code>ContentCatalog</code> for removing file (<a href="https://gitlab.com/antora/antora/issues/814">#814</a>)</li> <li><em>asciidoc-loader</em>: Define <code>page-component-latest-version</code> attribute with value of version string from latest component version (<a href="https://gitlab.com/antora/antora/issues/921">#921</a>)</li> <li><em>asciidoc-loader</em>: Define boolean <code>page-component-version-is-latest</code> attribute if page is in latest version of component (<a href="https://gitlab.com/antora/antora/issues/921">#921</a>)</li> <li><em>asciidoc-loader</em>: Assign edit URL of current page, if set, to <code>page-edit-url</code> attribute (<a href="https://gitlab.com/antora/antora/issues/354">#354</a>)</li> <li><em>asciidoc-loader</em>: Define boolean <code>page-origin-private</code> attribute if origin of page is private (<a href="https://gitlab.com/antora/antora/issues/354">#354</a>)</li> </ul> <!-- raw HTML omitted --> </blockquote> <p>... (truncated)</p> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://gitlab.com/antora/antora/commit/f09e3ac1f8597430a46c7e44ad280a927b42d184"><code>f09e3ac</code></a> release 3.1.2</li> <li><a href="https://gitlab.com/antora/antora/commit/937c40c4bc4ffb6098e10f338c31847d71933a63"><code>937c40c</code></a> upgrade dependencies that can be upgraded and refresh dependency lock file</li> <li><a href="https://gitlab.com/antora/antora/commit/5af8e49bf2114824ac1e4439b67470bcc0fd9212"><code>5af8e49</code></a> refresh dependency lock file</li> <li><a href="https://gitlab.com/antora/antora/commit/cdd7223392d466f7469a785acd46503b3fa45cb4"><code>cdd7223</code></a> update release process; automate management of release and tool version attri...</li> <li><a href="https://gitlab.com/antora/antora/commit/a8d8e729ba8527bfda4b5f336c66e6f41c556506"><code>a8d8e72</code></a> merge !964</li> <li><a href="https://gitlab.com/antora/antora/commit/911ae5400ed7b46545e6f1fd54068679a27e0d75"><code>911ae54</code></a> update What's New for Antora 3.1.2</li> <li><a href="https://gitlab.com/antora/antora/commit/f6fc688f04fe8daaf6d0395b200d371dc205d99a"><code>f6fc688</code></a> replace raise event with emit event</li> <li><a href="https://gitlab.com/antora/antora/commit/1975bd2c88c7dec8d037503bc59d6c2730ff7ed1"><code>1975bd2</code></a> backport fix for <a href="https://gitlab.com/antora/antora/issues/1025">#1025</a> allow content aggregator to parse value of content.bra...</li> <li><a href="https://gitlab.com/antora/antora/commit/7a398956f93029da3e1125aa9ed91ec2498f38c6"><code>7a39895</code></a> reclassify CHANGELOG entries</li> <li><a href="https://gitlab.com/antora/antora/commit/34ac3e2d886826befd6b049757508f2b444ae336"><code>34ac3e2</code></a> backport fix for <a href="https://gitlab.com/antora/antora/issues/1024">#1024</a> preserve target when creating static route if target i...</li> <li>Additional commits viewable in <a href="https://gitlab.com/antora/antora/compare/v2.3.4...v3.1.2">compare view</a></li> </ul> </details> <br /> Updates `npm-check-updates` from 7.0.2 to 16.7.4 <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/raineorshine/npm-check-updates/releases">npm-check-updates's releases</a>.</em></p> <blockquote> <h2>v16.4.0</h2> <h3>Feature</h3> <p>Added <code>--cacheClear</code> option for—you guessed it—clearing the cache 🫥.</p> <p>This brings the suite of cache-related options to:</p> <ul> <li><code>--cache</code> : Cache versions to the cache file.</li> <li><code>--cacheClear</code> : Clear the default cache, or the cache file specified by --cacheFile.</li> <li><code>--cacheExpiration <min></code> : Cache expiration in minutes (default: 10).</li> <li><code>--cacheFile <path></code> : Filepath for the cache file (default: "~/.ncu-cache.json").</li> </ul> <p>Thanks to <a href="https://github.com/ly3xqhl8g9"><code>@ly3xqhl8g9</code></a> whose code is gratefully more lucid than his username.</p> <h2>v16.3.0</h2> <h2>Feature</h2> <ul> <li>Added workspace support! 🚢</li> </ul> <p>Upgrade all workspaces:</p> <pre><code>ncu --workspaces ncu -ws </code></pre> <p>Upgrade a single workspace:</p> <pre><code>ncu --workspace a ncu -w a </code></pre> <p>Upgrade more than one workspace:</p> <pre><code>ncu --workspace a --workspace b ncu -w a -w b </code></pre> <p>Upgrade all workspaces AND the root project:</p> <pre><code>ncu --workspaces --root </code></pre> <p>Upgrade a single workspace AND the root project:</p> <pre><code>ncu --workspace a --root </tr></table> </code></pre> </blockquote> <p>... (truncated)</p> </details> <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/raineorshine/npm-check-updates/blob/main/CHANGELOG.md">npm-check-updates's changelog</a>.</em></p> <blockquote> <h1>Changelog</h1> <p>This file documents all <strong>major version</strong> releases. For other releases, please read the <a href="https://github.com/raineorshine/npm-check-updates/commits/main">commit history</a>.</p> <h2>[16.0.0] - 2022-07-23</h2> <h3>Breaking</h3> <ul> <li>Automatic detection of package data on stdin has been removed. This feature was deprecated in <code>v14.0.0</code>. Add <code>--stdin</code> for old behavior.</li> <li>Wild card filters now apply to scoped packages. Previously, <code>ncu -f '*vite*'</code> would not include <code>@vitejs/plugin-react</code>. Now, filters will match any part of the package name, including the scope. Use a more specific glob or regex expression for old behavior.</li> </ul> <p><a href="https://github.com/raineorshine/npm-check-updates/compare/v15.3.4...v16.0.0">https://github.com/raineorshine/npm-check-updates/compare/v15.3.4...v16.0.0</a></p> <h2>[15.0.0] - 2022-06-30</h2> <h3>Breaking</h3> <ul> <li>node >= 14.14 is now required (<a href="https://github-redirect.dependabot.com/raineorshine/npm-check-updates/issues/1145">#1145</a>) <ul> <li>Needed to upgrade <code>update-notifier</code> with has a moderate severity vulnerability</li> </ul> </li> <li>yarn autodetect has been improved (<a href="https://github-redirect.dependabot.com/raineorshine/npm-check-updates/issues/1148">#1148</a>) <ul> <li>This is a patch, though <em>technically</em> it is breaking. In the obscure case where <code>--packageManager</code> is not given, there is no <code>package-lock.json</code> in the current folder, and there is a <code>yarn.lock</code> in an ancestor directory, npm-check-updates will now use yarn.</li> <li>More practically, if you needed to specify <code>--packageManager yarn</code> explicitly before, you may not have to now</li> </ul> </li> </ul> <p><a href="https://github.com/raineorshine/npm-check-updates/compare/v14.1.1...v15.0.0">https://github.com/raineorshine/npm-check-updates/compare/v14.1.1...v15.0.0</a></p> <h2>[14.0.0] - 2022-06-16</h2> <h3>Breaking</h3> <p>Prerelease versions are now "upgraded" to versions with a different <a href="https://docs.npmjs.com/cli/v8/commands/npm-version#preid">preid</a>.</p> <p>For example, if you have a dependency at <code>1.3.3-next.1</code> and the version fetched by ncu is <code>1.2.3-dev.2</code>, ncu <strong>will</strong> suggest an "upgrade" to <code>1.2.3-dev.2</code>. This is because prerelease versions with different preids are incomparable. Since they are incomparable, ncu now assumes the fetched version is desired.</p> <p>Since this change affects only prereleases, there is no impact on default <code>ncu</code> usage that fetches the <code>latest</code> version. With <code>--pre 1</code> or <code>--target newest</code> or <code>--target greatest</code>, this change could affect which version is suggested if versions with different preids are published. The change was made to support the new <code>--target @[tag]</code> feature.</p> <p>If you have a use case where this change is not what is desired, please <a href="https://github.com/raineorshine/npm-check-updates/issues/new">report an issue</a>. The intention is for zero disruption to current usage.</p> <h3>Features</h3> <ul> <li>You can now upgrade to a specific tag, e.g. <code>--target @next</code>. Thanks to <a href="https://github.com/IMalyugin">IMalyugin</a>.</li> </ul> <p><a href="https://github.com/raineorshine/npm-check-updates/compare/v13.1.5...v14.0.0">https://github.com/raineorshine/npm-check-updates/compare/v13.1.5...v14.0.0</a></p> <h2>[13.0.0] - 2022-05-15</h2> <h3>Breaking</h3> <ul> <li>node >= 14 is now required</li> <li>Several options which have long been deprecated have been removed: <ul> <li><code>--greatest</code> - Instead use <code>--target greatest</code></li> </ul> </li> </ul> <!-- raw HTML omitted --> </blockquote> <p>... (truncated)</p> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/raineorshine/npm-check-updates/commit/b39167336966ffa954638c71be9932832e40e16d"><code>b391673</code></a> 16.7.4</li> <li><a href="https://github.com/raineorshine/npm-check-updates/commit/2b140bc0d3051772edb8b8d102d8150df72ed2c3"><code>2b140bc</code></a> Remove install hint from deno mode.</li> <li><a href="https://github.com/raineorshine/npm-check-updates/commit/3bd1e5c7c1a3ed8f452cb9f28fc385a1ce5744b5"><code>3bd1e5c</code></a> 16.7.3</li> <li><a href="https://github.com/raineorshine/npm-check-updates/commit/fdf68f27fd3b443a6db0b1701516fed0f5f61f24"><code>fdf68f2</code></a> Add jsonc support for deno config.</li> <li><a href="https://github.com/raineorshine/npm-check-updates/commit/9e73471f74fd02da46131b589eb49e0df186e66e"><code>9e73471</code></a> 16.7.2</li> <li><a href="https://github.com/raineorshine/npm-check-updates/commit/9cdc0ad189d0465fd79fc8cf0f8658569e2df2b9"><code>9cdc0ad</code></a> Bump dependencies</li> <li><a href="https://github.com/raineorshine/npm-check-updates/commit/8c25aac695f05d7528d2c5adc30bb70cdc01d853"><code>8c25aac</code></a> 16.7.1</li> <li><a href="https://github.com/raineorshine/npm-check-updates/commit/38c40536a24b9cf4f6b804781279c8f8ffbb1faa"><code>38c4053</code></a> Re-add patch target for pnpm (<a href="https://github-redirect.dependabot.com/raineorshine/npm-check-updates/issues/1268">#1268</a>).</li> <li><a href="https://github.com/raineorshine/npm-check-updates/commit/d925a0e5af756401715c69f477636ef1e6b9df8c"><code>d925a0e</code></a> 16.7.0</li> <li><a href="https://github.com/raineorshine/npm-check-updates/commit/3cab70a545d3f06b18ca5d54daa012cd816ed5b2"><code>3cab70a</code></a> Add support for deno (<a href="https://github-redirect.dependabot.com/raineorshine/npm-check-updates/issues/1267">#1267</a>)</li> <li>Additional commits viewable in <a href="https://github.com/raineorshine/npm-check-updates/compare/v7.0.2...v16.7.4">compare view</a></li> </ul> </details> <br /> 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-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> 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](https://github.com/apache/james-site/network/alerts). </details> -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
