2025.01 publish #1181
Merged
2025.01 publish #1181
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Bumps the prod-dependencies group with 2 updates: [@antora/cli](https://gitlab.com/antora/antora) and [@antora/site-generator-default](https://gitlab.com/antora/antora). Updates `@antora/cli` from 3.1.9 to 3.1.10 <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://gitlab.com/antora/antora/blob/main/CHANGELOG.adoc"><code>@antora/cli</code>'s changelog</a>.</em></p> <blockquote> <p>= Antora Changelog</p> <p>This document provides a summary of all notable changes to the core Antora components by release. For a detailed view of what's changed, refer to the repository's <a href="https://gitlab.com/antora/antora/commits/main%5Bcommit">https://gitlab.com/antora/antora/commits/main[commit</a> history].</p> <p>This project utilizes semantic versioning.</p> <p>== 3.2.0-alpha.8 (2024-12-05)</p> <p>=== Changed</p> <ul> <li><em>content-aggregator</em>: Don't apply camelCase transformation to descendant keys of the <code>ext</code> key in component version descriptor (<a href="https://gitlab.com/antora/antora/issues/1145">#1145</a>)</li> <li><em>content-aggregator</em>: Include <code>-</code> segment in edit URL for file hosted on gitlab.com to avoid redirct</li> <li>Apply code formatting changes to comply with biome toolchain (<a href="https://gitlab.com/antora/antora/issues/1157">#1157</a>)</li> <li>Add directory property to repository entry in package files</li> <li>Upgrade <code>@antora/expand-path-helper</code> to 3.0.x (content-aggregator, ui-loader, file-publisher, logger)</li> <li>Upgrade <code>@antora/user-require-helper</code> to 3.0.x (content-aggregator, asciidoc-loader, file-publisher, site-generator, cli)</li> </ul> <p>=== Fixed</p> <ul> <li><em>content-aggregator</em>: Gracefully handle case when value of nav key in component version descriptor is not an array (<a href="https://gitlab.com/antora/antora/issues/1147">#1147</a>)</li> <li><em>page-composer</em>: Use navtitle as content of orphan breadcrumb entry instead of doctitle (aka page title) (<a href="https://gitlab.com/antora/antora/issues/1159">#1159</a>)</li> <li><em>site-generator</em>: Fully support static register method on Class or Object exported by extension (<a href="https://gitlab.com/antora/antora/issues/1158">#1158</a>)</li> </ul> <p>== 3.2.0-alpha.7 (2024-12-05)</p> <p><em>Release failed.</em></p> <p>== 3.2.0-alpha.6 (2024-07-23)</p> <p>=== Changed</p> <ul> <li>Replace "AsciiDoc extension" with "Asciidoctor extension" in log messages</li> </ul> <p>=== Fixed</p> <ul> <li><em>file-publisher</em>: Wrap legacy stream on file when preparing files for output providers; remove listeners limit (<a href="https://gitlab.com/antora/antora/issues/1139">#1139</a>)</li> </ul> <p>== 3.2.0-alpha.5 (2024-06-25)</p> <p>=== Added</p> <ul> <li><em>playbook-builder</em>: Add <code>git.fetch_depth</code> key to control how many recent commits Antora fetches from a remote repository (<a href="https://gitlab.com/antora/antora/issues/1090">#1090</a>)</li> <li><em>content-classifier</em>: Allow component name and version to be referenced by attributes in antora.yml as <code>antora-component-name</code> and <code>antora-component-version</code> attributes, respectively (<a href="https://gitlab.com/antora/antora/issues/1106">#1106</a>)</li> <li><em>asciidoc-loader</em>: Detect (and skip) Antora extension that's been registered as an AsciiDoc extension and log a warning (<a href="https://gitlab.com/antora/antora/issues/1084">#1084</a>)</li> <li><em>site-generator</em>: Detect (and skip) AsciiDoc extension registered as an Antora extension and log a warning (<a href="https://gitlab.com/antora/antora/issues/1104">#1104</a>)</li> </ul> <p>=== Changed</p> <ul> <li><em>content-aggregator</em>: Use worktree from local repository even if repository has no commits (<a href="https://gitlab.com/antora/antora/issues/298">#298</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/854ac81ffb4387f9cd6d869d3ee5729a978f63c7"><code>854ac81</code></a> release 3.1.10</li> <li><a href="https://gitlab.com/antora/antora/commit/af08e082ae27a2ddbb8b5dd6a81be19487595216"><code>af08e08</code></a> fix issue references on what's new page</li> <li><a href="https://gitlab.com/antora/antora/commit/43cdee8610e3433de3cae0f131ee4eb1fdf6cc4f"><code>43cdee8</code></a> fix broken internal reference on images page</li> <li><a href="https://gitlab.com/antora/antora/commit/36207a59daec2bdfbc7102163f285f3d31d69751"><code>36207a5</code></a> add section to images page to document how to make a link to an image</li> <li><a href="https://gitlab.com/antora/antora/commit/ca6a33d5d5e5871c5b5e405a7322cfb72abeb58b"><code>ca6a33d</code></a> improve introduction of images and attachment by mentioning use of xref macro</li> <li><a href="https://gitlab.com/antora/antora/commit/3bab6c658e089a184675fe268acca945d78507e6"><code>3bab6c6</code></a> mention that xref can be used to create a link to an image</li> <li><a href="https://gitlab.com/antora/antora/commit/c741759f797a3713c273d676eb629700053a4994"><code>c741759</code></a> update what's new page for upcoming 3.1.10 release</li> <li><a href="https://gitlab.com/antora/antora/commit/5742a22b65d1577d71d1fb59d014ba2df607717b"><code>5742a22</code></a> fix issue references in CHANGELOG [skip ci]</li> <li><a href="https://gitlab.com/antora/antora/commit/6b67ddcddb0da15b4035cca44b1b2b87496a2d36"><code>6b67ddc</code></a> allow coverage npm script to be run per package and document how to invoke it...</li> <li><a href="https://gitlab.com/antora/antora/commit/62806873a55a245beaae5f96d9ab83a3003d000e"><code>6280687</code></a> use curl to fetch the release script instead of wget [skip ci]</li> <li>Additional commits viewable in <a href="https://gitlab.com/antora/antora/compare/v3.1.9...v3.1.10">compare view</a></li> </ul> </details> <br /> Updates `@antora/site-generator-default` from 3.1.9 to 3.1.10 <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>= Antora Changelog</p> <p>This document provides a summary of all notable changes to the core Antora components by release. For a detailed view of what's changed, refer to the repository's <a href="https://gitlab.com/antora/antora/commits/main%5Bcommit">https://gitlab.com/antora/antora/commits/main[commit</a> history].</p> <p>This project utilizes semantic versioning.</p> <p>== 3.2.0-alpha.8 (2024-12-05)</p> <p>=== Changed</p> <ul> <li><em>content-aggregator</em>: Don't apply camelCase transformation to descendant keys of the <code>ext</code> key in component version descriptor (<a href="https://gitlab.com/antora/antora/issues/1145">#1145</a>)</li> <li><em>content-aggregator</em>: Include <code>-</code> segment in edit URL for file hosted on gitlab.com to avoid redirct</li> <li>Apply code formatting changes to comply with biome toolchain (<a href="https://gitlab.com/antora/antora/issues/1157">#1157</a>)</li> <li>Add directory property to repository entry in package files</li> <li>Upgrade <code>@antora/expand-path-helper</code> to 3.0.x (content-aggregator, ui-loader, file-publisher, logger)</li> <li>Upgrade <code>@antora/user-require-helper</code> to 3.0.x (content-aggregator, asciidoc-loader, file-publisher, site-generator, cli)</li> </ul> <p>=== Fixed</p> <ul> <li><em>content-aggregator</em>: Gracefully handle case when value of nav key in component version descriptor is not an array (<a href="https://gitlab.com/antora/antora/issues/1147">#1147</a>)</li> <li><em>page-composer</em>: Use navtitle as content of orphan breadcrumb entry instead of doctitle (aka page title) (<a href="https://gitlab.com/antora/antora/issues/1159">#1159</a>)</li> <li><em>site-generator</em>: Fully support static register method on Class or Object exported by extension (<a href="https://gitlab.com/antora/antora/issues/1158">#1158</a>)</li> </ul> <p>== 3.2.0-alpha.7 (2024-12-05)</p> <p><em>Release failed.</em></p> <p>== 3.2.0-alpha.6 (2024-07-23)</p> <p>=== Changed</p> <ul> <li>Replace "AsciiDoc extension" with "Asciidoctor extension" in log messages</li> </ul> <p>=== Fixed</p> <ul> <li><em>file-publisher</em>: Wrap legacy stream on file when preparing files for output providers; remove listeners limit (<a href="https://gitlab.com/antora/antora/issues/1139">#1139</a>)</li> </ul> <p>== 3.2.0-alpha.5 (2024-06-25)</p> <p>=== Added</p> <ul> <li><em>playbook-builder</em>: Add <code>git.fetch_depth</code> key to control how many recent commits Antora fetches from a remote repository (<a href="https://gitlab.com/antora/antora/issues/1090">#1090</a>)</li> <li><em>content-classifier</em>: Allow component name and version to be referenced by attributes in antora.yml as <code>antora-component-name</code> and <code>antora-component-version</code> attributes, respectively (<a href="https://gitlab.com/antora/antora/issues/1106">#1106</a>)</li> <li><em>asciidoc-loader</em>: Detect (and skip) Antora extension that's been registered as an AsciiDoc extension and log a warning (<a href="https://gitlab.com/antora/antora/issues/1084">#1084</a>)</li> <li><em>site-generator</em>: Detect (and skip) AsciiDoc extension registered as an Antora extension and log a warning (<a href="https://gitlab.com/antora/antora/issues/1104">#1104</a>)</li> </ul> <p>=== Changed</p> <ul> <li><em>content-aggregator</em>: Use worktree from local repository even if repository has no commits (<a href="https://gitlab.com/antora/antora/issues/298">#298</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/854ac81ffb4387f9cd6d869d3ee5729a978f63c7"><code>854ac81</code></a> release 3.1.10</li> <li><a href="https://gitlab.com/antora/antora/commit/af08e082ae27a2ddbb8b5dd6a81be19487595216"><code>af08e08</code></a> fix issue references on what's new page</li> <li><a href="https://gitlab.com/antora/antora/commit/43cdee8610e3433de3cae0f131ee4eb1fdf6cc4f"><code>43cdee8</code></a> fix broken internal reference on images page</li> <li><a href="https://gitlab.com/antora/antora/commit/36207a59daec2bdfbc7102163f285f3d31d69751"><code>36207a5</code></a> add section to images page to document how to make a link to an image</li> <li><a href="https://gitlab.com/antora/antora/commit/ca6a33d5d5e5871c5b5e405a7322cfb72abeb58b"><code>ca6a33d</code></a> improve introduction of images and attachment by mentioning use of xref macro</li> <li><a href="https://gitlab.com/antora/antora/commit/3bab6c658e089a184675fe268acca945d78507e6"><code>3bab6c6</code></a> mention that xref can be used to create a link to an image</li> <li><a href="https://gitlab.com/antora/antora/commit/c741759f797a3713c273d676eb629700053a4994"><code>c741759</code></a> update what's new page for upcoming 3.1.10 release</li> <li><a href="https://gitlab.com/antora/antora/commit/5742a22b65d1577d71d1fb59d014ba2df607717b"><code>5742a22</code></a> fix issue references in CHANGELOG [skip ci]</li> <li><a href="https://gitlab.com/antora/antora/commit/6b67ddcddb0da15b4035cca44b1b2b87496a2d36"><code>6b67ddc</code></a> allow coverage npm script to be run per package and document how to invoke it...</li> <li><a href="https://gitlab.com/antora/antora/commit/62806873a55a245beaae5f96d9ab83a3003d000e"><code>6280687</code></a> use curl to fetch the release script instead of wget [skip ci]</li> <li>Additional commits viewable in <a href="https://gitlab.com/antora/antora/compare/v3.1.9...v3.1.10">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 show <dependency name> ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore <dependency name> major version` will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself) - `@dependabot ignore <dependency name> minor version` will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself) - `@dependabot ignore <dependency name>` will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself) - `@dependabot unignore <dependency name>` will remove all of the ignore conditions of the specified dependency - `@dependabot unignore <dependency name> <ignore condition>` will remove the ignore condition of the specified dependency and ignore conditions </details> Signed-off-by: dependabot[bot] <[email protected]> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
…o4j#1134) Bumps the dev-dependencies group with 2 updates in the / directory: [express](https://github.com/expressjs/express) and [nodemon](https://github.com/remy/nodemon). Updates `express` from 4.21.1 to 4.21.2 <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/expressjs/express/releases">express's releases</a>.</em></p> <blockquote> <h2>4.21.2</h2> <h2>What's Changed</h2> <ul> <li>Add funding field (v4) by <a href="https://github.com/bjohansebas"><code>@bjohansebas</code></a> in <a href="https://redirect.github.com/expressjs/express/pull/6065">expressjs/express#6065</a></li> <li>deps: [email protected] by <a href="https://github.com/blakeembrey"><code>@blakeembrey</code></a> in <a href="https://redirect.github.com/expressjs/express/pull/5956">expressjs/express#5956</a></li> <li>deps: bump [email protected] by <a href="https://github.com/jonchurch"><code>@jonchurch</code></a> in <a href="https://redirect.github.com/expressjs/express/pull/6209">expressjs/express#6209</a></li> <li>Release: 4.21.2 by <a href="https://github.com/UlisesGascon"><code>@UlisesGascon</code></a> in <a href="https://redirect.github.com/expressjs/express/pull/6094">expressjs/express#6094</a></li> </ul> <p><strong>Full Changelog</strong>: <a href="https://github.com/expressjs/express/compare/4.21.1...4.21.2">https://github.com/expressjs/express/compare/4.21.1...4.21.2</a></p> </blockquote> </details> <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/expressjs/express/blob/4.21.2/History.md">express's changelog</a>.</em></p> <blockquote> <h1>4.21.2 / 2024-11-06</h1> <ul> <li>deps: [email protected] <ul> <li>Fix backtracking protection</li> </ul> </li> <li>deps: [email protected] <ul> <li>Throws an error on invalid path values</li> </ul> </li> </ul> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/expressjs/express/commit/1faf228935aa0a13111f92c28ee795be64ce3f0f"><code>1faf228</code></a> 4.21.2</li> <li><a href="https://github.com/expressjs/express/commit/2e0fb646d03184dd9a5285813460210c0e7ae654"><code>2e0fb64</code></a> deps: bump [email protected] (<a href="https://redirect.github.com/expressjs/express/issues/6209">#6209</a>)</li> <li><a href="https://github.com/expressjs/express/commit/59fc27028ec5d212be653d35d7e3f73a2c3ac3c0"><code>59fc270</code></a> deps: [email protected] (<a href="https://redirect.github.com/expressjs/express/issues/5956">#5956</a>)</li> <li><a href="https://github.com/expressjs/express/commit/51fc39ccf834eec44547b0f4fed8027e7c05a009"><code>51fc39c</code></a> docs: add funding (<a href="https://redirect.github.com/expressjs/express/issues/6065">#6065</a>)</li> <li>See full diff in <a href="https://github.com/expressjs/express/compare/4.21.1...4.21.2">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/~jonchurch">jonchurch</a>, a new releaser for express since your current version.</p> </details> <br /> Updates `nodemon` from 3.1.7 to 3.1.9 <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/remy/nodemon/releases">nodemon's releases</a>.</em></p> <blockquote> <h2>v3.1.9</h2> <h2><a href="https://github.com/remy/nodemon/compare/v3.1.8...v3.1.9">3.1.9</a> (2024-12-13)</h2> <h3>Bug Fixes</h3> <ul> <li>maintain backward support for <code>exitcrash</code> (<a href="https://github.com/remy/nodemon/commit/9c9de6eb075c62650145bfebfac3680923f172d6">9c9de6e</a>)</li> </ul> <h2>v3.1.8</h2> <h2><a href="https://github.com/remy/nodemon/compare/v3.1.7...v3.1.8">3.1.8</a> (2024-12-13)</h2> <h3>Bug Fixes</h3> <ul> <li>types updated (<a href="https://github.com/remy/nodemon/commit/cb91187ef6243d76d9fb641af7acd2a5fbd1e406">cb91187</a>)</li> </ul> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/remy/nodemon/commit/9c9de6eb075c62650145bfebfac3680923f172d6"><code>9c9de6e</code></a> fix: maintain backward support for <code>exitcrash</code></li> <li><a href="https://github.com/remy/nodemon/commit/880fc4201e722f36f581b7a2817339dbc052b02e"><code>880fc42</code></a> chore: fix merge conflict</li> <li><a href="https://github.com/remy/nodemon/commit/cb91187ef6243d76d9fb641af7acd2a5fbd1e406"><code>cb91187</code></a> fix: types updated</li> <li><a href="https://github.com/remy/nodemon/commit/a021683f7a6c4eca4f674f9c97b1a1b4e4c03a31"><code>a021683</code></a> chore: website</li> <li><a href="https://github.com/remy/nodemon/commit/701a950c5c38ecc272f22614ab0b7eca377945bc"><code>701a950</code></a> chore: website</li> <li><a href="https://github.com/remy/nodemon/commit/5bd54896489c1b6868e26041c71652dc5b1994ae"><code>5bd5489</code></a> chore: website</li> <li><a href="https://github.com/remy/nodemon/commit/d6e5bddd6ef37ab55f319292fc6b2dea6a93888e"><code>d6e5bdd</code></a> chore: website</li> <li><a href="https://github.com/remy/nodemon/commit/c629667d029722e13fc9c941f45c82bc65a7ed11"><code>c629667</code></a> Merge branch 'main' of github.com:remy/nodemon</li> <li><a href="https://github.com/remy/nodemon/commit/ea9595343277d60f85ac84a84ac9836f2ced6bac"><code>ea95953</code></a> chore: web site</li> <li><a href="https://github.com/remy/nodemon/commit/ecea25b9d9e09fa5d3df90cf55b1af8803935714"><code>ecea25b</code></a> chore: update website / fix jq</li> <li>Additional commits viewable in <a href="https://github.com/remy/nodemon/compare/v3.1.7...v3.1.9">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 show <dependency name> ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore <dependency name> major version` will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself) - `@dependabot ignore <dependency name> minor version` will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself) - `@dependabot ignore <dependency name>` will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself) - `@dependabot unignore <dependency name>` will remove all of the ignore conditions of the specified dependency - `@dependabot unignore <dependency name> <ignore condition>` will remove the ignore condition of the specified dependency and ignore conditions </details> Signed-off-by: dependabot[bot] <[email protected]> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> Co-authored-by: Jens Pryce-Åklundh <[email protected]>
…prod-dependencies group (neo4j#1142) Bumps the prod-dependencies group with 1 update: @neo4j-antora/antora-modify-sitemaps. Updates `@neo4j-antora/antora-modify-sitemaps` from 0.4.4 to 0.5.0 [](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) 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 show <dependency name> ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore <dependency name> major version` will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself) - `@dependabot ignore <dependency name> minor version` will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself) - `@dependabot ignore <dependency name>` will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself) - `@dependabot unignore <dependency name>` will remove all of the ignore conditions of the specified dependency - `@dependabot unignore <dependency name> <ignore condition>` will remove the ignore condition of the specified dependency and ignore conditions </details> Signed-off-by: dependabot[bot] <[email protected]> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
neo4j#1145) Co-authored-by: Jens Pryce-Åklundh <[email protected]>
Co-authored-by: Jens Pryce-Åklundh <[email protected]>
…j#1151) The examples in Patterns / Syntax and semantics / shortestPaths / Examples mix legacy shortest path and QPPs, which is disallowed. This PR changes them to variable-length relationships. It also improves the header "Restricted to variable length". QPPs are disallowed but also variable length. What they are not are variable-length relationships.
…th() functions (neo4j#1146) Document that the shortestPath() and allShortestPath() functions can only have a lower bound of 0 or 1 for its variable length pattern. This is not allowed: ` MATCH p=shortestPath((a:A)-[:R*2..]->(b:B)) RETURN 1` A lower bound can be specified using a filter, but might lead to executing a possibly very slow fallback plan. ` MATCH p=shortestPath((a:A)-[:R*]->(b:B)) WHERE length(p)>2 RETURN 1` The possibly very slow fallback plan is this part: ``` | | +Top | 3 | anon_1 ASC LIMIT 1 | 1 | In Pipeline 6 | | | | +----+-------------------------------------------------------+----------------+---------------------+ | | +Projection | 4 | length(p) AS anon_1 | 1 | | | | | +----+-------------------------------------------------------+----------------+ | | | +Filter | 5 | length(p) > $autoint_0 | 1 | | | | | +----+-------------------------------------------------------+----------------+ | | | +Projection | 6 | (a)-[anon_0*]->(b) AS p | 4 | | | | | +----+-------------------------------------------------------+----------------+ | | | +VarLengthExpand(Into) | 7 | (a)-[anon_0:R*]->(b) | 4 | | | | | +----+-------------------------------------------------------+----------------+ | | | +Argument | 8 | a, b | 100 | Fused in Pipeline 5 | | | +----+-------------------------------------------------------+----------------+---------------------+ ``` Within this query plan: ``` +--------------------------+----+-------------------------------------------------------+----------------+---------------------+ | Operator | Id | Details | Estimated Rows | Pipeline | +--------------------------+----+-------------------------------------------------------+----------------+---------------------+ | +ProduceResults | 0 | `1` | 30 | | | | +----+-------------------------------------------------------+----------------+ | | +Projection | 1 | $autoint_1 AS `1` | 30 | | | | +----+-------------------------------------------------------+----------------+ | | +AntiConditionalApply | 2 | | 30 | Fused in Pipeline 7 | | |\ +----+-------------------------------------------------------+----------------+---------------------+ | | +Top | 3 | anon_1 ASC LIMIT 1 | 1 | In Pipeline 6 | | | | +----+-------------------------------------------------------+----------------+---------------------+ | | +Projection | 4 | length(p) AS anon_1 | 1 | | | | | +----+-------------------------------------------------------+----------------+ | | | +Filter | 5 | length(p) > $autoint_0 | 1 | | | | | +----+-------------------------------------------------------+----------------+ | | | +Projection | 6 | (a)-[anon_0*]->(b) AS p | 4 | | | | | +----+-------------------------------------------------------+----------------+ | | | +VarLengthExpand(Into) | 7 | (a)-[anon_0:R*]->(b) | 4 | | | | | +----+-------------------------------------------------------+----------------+ | | | +Argument | 8 | a, b | 100 | Fused in Pipeline 5 | | | +----+-------------------------------------------------------+----------------+---------------------+ | +Apply | 9 | | 100 | | | |\ +----+-------------------------------------------------------+----------------+---------------------+ | | +Optional | 10 | a, b | 100 | In Pipeline 4 | | | | +----+-------------------------------------------------------+----------------+---------------------+ | | +ShortestPath | 11 | p = (a)-[anon_0:R*]->(b) WHERE length(p) > $autoint_0 | 30 | | | | | +----+-------------------------------------------------------+----------------+ | | | +Argument | 12 | a, b | 100 | Fused in Pipeline 3 | | | +----+-------------------------------------------------------+----------------+---------------------+ | +CartesianProduct | 13 | | 100 | In Pipeline 2 | | |\ +----+-------------------------------------------------------+----------------+---------------------+ | | +NodeByLabelScan | 14 | b:B | 10 | In Pipeline 1 | | | +----+-------------------------------------------------------+----------------+---------------------+ | +NodeByLabelScan | 15 | a:A | 10 | In Pipeline 0 | +--------------------------+----+-------------------------------------------------------+----------------+---------------------+ ``` Better is to use the keyword-based SHORTEST. `MATCH p = SHORTEST 1 (a:A)-[:R]->{2,}(b:B) RETURN 1` --------- Co-authored-by: Jens Pryce-Åklundh <[email protected]>
Docs update regarding neo-technology/neo4j#28493 (plus a little clarification w.r.t. variable scope in subqueries). --------- Co-authored-by: Richard Sill <[email protected]> Co-authored-by: Jens Pryce-Åklundh <[email protected]>
Co-authored-by: Therese Magnusson <[email protected]>
…prod-dependencies group (neo4j#1158) Bumps the prod-dependencies group with 1 update: @neo4j-antora/antora-modify-sitemaps. Updates `@neo4j-antora/antora-modify-sitemaps` from 0.5.0 to 0.6.0 [](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) 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 show <dependency name> ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore <dependency name> major version` will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself) - `@dependabot ignore <dependency name> minor version` will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself) - `@dependabot ignore <dependency name>` will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself) - `@dependabot unignore <dependency name>` will remove all of the ignore conditions of the specified dependency - `@dependabot unignore <dependency name> <ignore condition>` will remove the ignore condition of the specified dependency and ignore conditions </details> Signed-off-by: dependabot[bot] <[email protected]> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> Co-authored-by: Jens Pryce-Åklundh <[email protected]>
Co-authored-by: Jens Pryce-Åklundh <[email protected]>
…prod-dependencies group (neo4j#1171) Bumps the prod-dependencies group with 1 update: @neo4j-antora/antora-table-footnotes. Updates `@neo4j-antora/antora-table-footnotes` from 0.3.2 to 0.3.3 [](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) 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 show <dependency name> ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore <dependency name> major version` will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself) - `@dependabot ignore <dependency name> minor version` will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself) - `@dependabot ignore <dependency name>` will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself) - `@dependabot unignore <dependency name>` will remove all of the ignore conditions of the specified dependency - `@dependabot unignore <dependency name> <ignore condition>` will remove the ignore condition of the specified dependency and ignore conditions </details> Signed-off-by: dependabot[bot] <[email protected]> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
The page-version attribute between Cypher and other manuals wont work with the release of 2025.01
Reverts changes made here: neo4j#1166 due to a rolback in product
|
Thanks for the documentation updates. The preview documentation has now been torn down - reopening this PR will republish it. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.