- 
                Notifications
    You must be signed in to change notification settings 
- Fork 83
5.x merge dev #1740
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
          
     Merged
      
      
    
                
     Merged
            
            5.x merge dev #1740
Conversation
  
    
      This file contains hidden or 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
    
  
  
    
    It does not exist any more
Co-authored-by: NataliaIvakina <82437520+NataliaIvakina@users.noreply.github.com> Co-authored-by: Reneta Popova <reneta.popova@neo4j.com>
Cherry-picked from neo4j#1243 Co-authored-by: Michael Blum <mikeblum@users.noreply.github.com>
Co-authored-by: Reneta Popova <reneta.popova@neo4j.com> Co-authored-by: David Pond <davidpond@gmail.com>
Bumps @neo4j-antora/antora-add-notes from 0.1.6 to 0.3.1. [](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 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) </details> Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Bumps [nodemon](https://github.com/remy/nodemon) from 2.0.20 to 3.0.2. <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.0.2</h2> <h2><a href="https://github.com/remy/nodemon/compare/v3.0.1...v3.0.2">3.0.2</a> (2023-12-01)</h2> <h3>Bug Fixes</h3> <ul> <li>bump debug out of vuln range (<a href="https://github.com/remy/nodemon/commit/533ad9ccde0beb864c64d86dc62f6f54fb60769c">533ad9c</a>), closes <a href="https://redirect.github.com/remy/nodemon/issues/2146">#2146</a></li> </ul> <h2>v3.0.1</h2> <h2><a href="https://github.com/remy/nodemon/compare/v3.0.0...v3.0.1">3.0.1</a> (2023-07-09)</h2> <h3>Bug Fixes</h3> <ul> <li>restore default ext watch behaviour (<a href="https://github.com/remy/nodemon/commit/95bee008bfb4eb77d7826f193e9386812652f449">95bee00</a>), closes <a href="https://redirect.github.com/remy/nodemon/issues/2124">#2124</a> <a href="https://redirect.github.com/remy/nodemon/issues/1957">#1957</a></li> </ul> <h2>v3.0.0</h2> <h1><a href="https://github.com/remy/nodemon/compare/v2.0.22...v3.0.0">3.0.0</a> (2023-07-08)</h1> <h3>Bug Fixes</h3> <ul> <li>also watch cjs (<a href="https://github.com/remy/nodemon/commit/86d5f403a3e06e8aed48b37fa854730dc83257be">86d5f40</a>)</li> <li>node@10 support back in (<a href="https://github.com/remy/nodemon/commit/af3b9e237281beffd92ceee0e2411ef53edcf375">af3b9e2</a>)</li> <li>semver vuln dep (<a href="https://github.com/remy/nodemon/commit/6bb876666715e16464d48f98cd4bc2cba172a970">6bb8766</a>), closes <a href="https://redirect.github.com/remy/nodemon/issues/2119">#2119</a></li> </ul> <h3>Features</h3> <ul> <li>always use polling on IBM i (<a href="https://github.com/remy/nodemon/commit/3b5810463e7c39b0a8e2856c996faf454a6ca1f8">3b58104</a>)</li> </ul> <h3>BREAKING CHANGES</h3> <ul> <li>official support for node@8 dropped.</li> </ul> <p>However there's no function being used in semver that breaks node 8, so it's technically still possible to run with node 8, but it will no longer be supported (or tested in CI).</p> <h2>v2.0.22</h2> <h2><a href="https://github.com/remy/nodemon/compare/v2.0.21...v2.0.22">2.0.22</a> (2023-03-22)</h2> <h3>Bug Fixes</h3> <ul> <li>remove ts mapping if loader present (<a href="https://github.com/remy/nodemon/commit/f7816e445b61e77dd57d5c9ccf5fa0be4f9b18a7">f7816e4</a>), closes <a href="https://redirect.github.com/remy/nodemon/issues/2083">#2083</a></li> </ul> <h2>v2.0.21</h2> <h2><a href="https://github.com/remy/nodemon/compare/v2.0.20...v2.0.21">2.0.21</a> (2023-03-02)</h2> <!-- raw HTML omitted --> </blockquote> <p>... (truncated)</p> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/remy/nodemon/commit/0ebfaa5d1ce24faf1a2c0f1db31b56dbd0a82628"><code>0ebfaa5</code></a> chore: Update release.yml</li> <li><a href="https://github.com/remy/nodemon/commit/533ad9ccde0beb864c64d86dc62f6f54fb60769c"><code>533ad9c</code></a> fix: bump debug out of vuln range</li> <li><a href="https://github.com/remy/nodemon/commit/1779411cc1154cbd4f93641456bc94d0031cdfe9"><code>1779411</code></a> chore: website update</li> <li><a href="https://github.com/remy/nodemon/commit/b066c21606d5c499c5ff06fbce9b9ee5b20d8780"><code>b066c21</code></a> chore: web site render</li> <li><a href="https://github.com/remy/nodemon/commit/078ee659e21f39f063b6a3430626269c5c286145"><code>078ee65</code></a> chore: web site render</li> <li><a href="https://github.com/remy/nodemon/commit/8f2ff63b9329d0389361baeedd9ec223374d18c9"><code>8f2ff63</code></a> chore: web site render</li> <li><a href="https://github.com/remy/nodemon/commit/3b287f1d0c548cc37c592117fc546bbf98bd3866"><code>3b287f1</code></a> chore: web site render</li> <li><a href="https://github.com/remy/nodemon/commit/4fa02cf4ed0ae85a910734da4557e3808417f835"><code>4fa02cf</code></a> chore: web site render</li> <li><a href="https://github.com/remy/nodemon/commit/22d8f775f7db73fee410a21f4040b730fc557e1a"><code>22d8f77</code></a> chore: fix borked site</li> <li><a href="https://github.com/remy/nodemon/commit/66b728e2576e9f8cd3bda4cb37b6eb980ca29d1b"><code>66b728e</code></a> Merge branch 'main' of github.com:remy/nodemon</li> <li>Additional commits viewable in <a href="https://github.com/remy/nodemon/compare/v2.0.20...v3.0.2">compare view</a></li> </ul> </details> <br /> [](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 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) </details> Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
[//]: # (dependabot-start)⚠️ **Dependabot is rebasing this PR**⚠️ Rebasing might not happen immediately, so don't worry if this takes some time. Note: if you make any changes to this PR yourself, they will take precedence over the rebase. --- [//]: # (dependabot-end) Bumps [@antora/cli](https://gitlab.com/antora/antora) from 3.1.2 to 3.1.5. <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>== Unreleased</p> <p>=== Fixed</p> <ul> <li><em>logger</em>: Restore error stack in log output when using pino-std-serializers >= 6.1 (<a href="https://gitlab.com/antora/antora/issues/1049">#1049</a>)</li> <li><em>content-aggregator</em>: Consider local branches in non-managed bare repository that has at least one remote branch (<a href="https://gitlab.com/antora/antora/issues/1064">#1064</a>)</li> <li><em>ui-loader</em>: Correctly handle connection error when retrieving remote UI bundle</li> <li><em>asciidoc-loader</em>: Do not fail to load AsciiDoc if pub or pub.moduleRootPath properties are not set on virtual file</li> <li><em>asciidoc-loader</em>: Do not fail to load AsciiDoc if target of image macro resolves to an unpublished image (<a href="https://gitlab.com/antora/antora/issues/1092">#1092</a>)</li> <li><em>site-generator</em>: Retry loadUi in isolation after aggregateContent if network connection occurs when retrieving remote UI bundle (<a href="https://gitlab.com/antora/antora/issues/1095">#1095</a>)</li> <li><em>cli</em>: Remove empty default on description for <code>--extension</code> option</li> </ul> <p>=== Changed</p> <ul> <li><em>ui-loader</em>: Change gulp-vinyl-zip dependency to <code>@vscode/gulp-vinyl-zip</code> (no functional changes)</li> <li><em>asciidoc-loader</em>: Fix relative path computation when path is extensionless and to matches parent folder of from (<a href="https://gitlab.com/antora/antora/issues/1094">#1094</a>)</li> <li><em>page-composer</em>: Fix result of relativize helper when path is extensionless and to matches parent folder of from (<a href="https://gitlab.com/antora/antora/issues/1094">#1094</a>)</li> <li><em>file-publisher</em>: Change gulp-vinyl-zip dependency to <code>@vscode/gulp-vinyl-zip</code> (no functional changes)</li> </ul> <p>== 3.2.0-alpha.2 (2022-11-01)</p> <p>=== Added</p> <ul> <li><em>content-classifier</em>: Emit <code>componentsRegistered</code> event after all components and versions have been registered (<a href="https://gitlab.com/antora/antora/issues/1015">#1015</a>)</li> <li><em>content-classifier</em>: Store raw files, nav, and startPage data on partially constructed component version until processed (<a href="https://gitlab.com/antora/antora/issues/1015">#1015</a>)</li> <li><em>content-classifier</em>: Add readable property named <code>files</code> to component version in <code>ContentCatalog#registerComponentVersionStartPage</code> to get files for component version on access (<a href="https://gitlab.com/antora/antora/issues/1015">#1015</a>)</li> <li><em>content-classifier</em>: Add readable property named <code>startPage</code> to component version in <code>ContentCatalog#registerComponentVersionStartPage</code> to look up start page for component version on access (<a href="https://gitlab.com/antora/antora/issues/1015">#1015</a>)</li> <li><em>content-classifier</em>: Discover implicit site start page in component version promoted to site root (<a href="https://gitlab.com/antora/antora/issues/1021">#1021</a>)</li> <li><em>content-classifier</em>: Update <code>ContentCatalog#registerComponentVersionStartPage</code> to return start page</li> </ul> <p>=== Changed</p> <ul> <li><em>content-classifier</em>: Don't recompute resource ID on file from content aggregate if <code>src.family</code> is set (<a href="https://gitlab.com/antora/antora/issues/1026">#1026</a>)</li> <li><em>content-classifier</em>: Don't assign fallback value to url property on component version if property is already set</li> <li><em>site-generator</em>: Print site URL instead of file URI in completion message if CI=true</li> </ul> <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>: Use consistent formatting for error messages in playbook builder</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-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> </ul> <!-- raw HTML omitted --> </blockquote> <p>... (truncated)</p> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://gitlab.com/antora/antora/commit/5e09b0afc2e2540ce0bba3f68b2923fdd4115d87"><code>5e09b0a</code></a> release 3.1.5</li> <li><a href="https://gitlab.com/antora/antora/commit/c907ab8e369010e20275e933e13c1a9c5e359437"><code>c907ab8</code></a> update what's new for 3.1.5 release</li> <li><a href="https://gitlab.com/antora/antora/commit/083412bac363b5d1b84a025ed8811c3f487ed698"><code>083412b</code></a> backport fix for <a href="https://gitlab.com/antora/antora/issues/1095">#1095</a> retry loadUi in isolation after aggregateContent if ne...</li> <li><a href="https://gitlab.com/antora/antora/commit/ff2cf9839c2a23695753a9de8217e4f482dabebb"><code>ff2cf98</code></a> clarify that ~ is a shorthand in YAML for nil</li> <li><a href="https://gitlab.com/antora/antora/commit/4a53118e432f4e50fe2e122fe35502a2750fdd61"><code>4a53118</code></a> clarify that empty string should be used to set an attribute without an expli...</li> <li><a href="https://gitlab.com/antora/antora/commit/118a710f94cc78b1a9fb4c692c4d291f67a30004"><code>118a710</code></a> upgrade setup-node action in example GitHub Actions workflow</li> <li><a href="https://gitlab.com/antora/antora/commit/afe2a9be2b9311900476bacaf31b8b4dbab8bd9f"><code>afe2a9b</code></a> backport fix for <a href="https://gitlab.com/antora/antora/issues/1094">#1094</a> fix relative path computation when path is extensionle...</li> <li><a href="https://gitlab.com/antora/antora/commit/59d4d9cf9537323d43c702b7fcd4e0efbc21d675"><code>59d4d9c</code></a> update GitHub Actions workflows</li> <li><a href="https://gitlab.com/antora/antora/commit/af7213150687662ed0debb1e97645136b39f9cf6"><code>af72131</code></a> change gulp-vinyl-zip dependency to <code>@vscode/gulp-vinyl-zip</code> (no functional cha...</li> <li><a href="https://gitlab.com/antora/antora/commit/05202b220c0b5540eb3377d13ffed68385473eb2"><code>05202b2</code></a> remove empty default on description for --extension CLI option</li> <li>Additional commits viewable in <a href="https://gitlab.com/antora/antora/compare/v3.1.2...v3.1.5">compare view</a></li> </ul> </details> <br /> [](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 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) </details> Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Bumps @neo4j-antora/antora-page-roles from 0.3.1 to 0.3.2.
Bumps [@antora/cli](https://gitlab.com/antora/antora) from 3.1.2 to 3.1.6.
Bumps [@antora/site-generator-default](https://gitlab.com/antora/antora) from 3.1.2 to 3.1.6.
Co-authored-by: Reneta Popova <reneta.popova@neo4j.com>
The reason I moved the Note, was because it wasn't clear which section the Note refers to.
We have mismatches in the descriptions of the following procedures: * `db.index.fulltext.queryNodes()` * `db.index.fulltext.queryRelationships()` * `db.index.vector.createNodeIndex()` The proposed changes are taken from the code, and I suggest to modify them a little bit. When we update the descriptions in documentation, we have to update them in the codebase. --------- Co-authored-by: Matthew Parnell <matt@parnmatt.co.uk>
…rom Kafka, Spark, etc. (neo4j#1301)
There is a duplicated entry for that metric, with the only difference being one has the description spelled `canceled` and the other one `cancelled`. I merged both into the first entry just because because that matches the order of the metrics in the code-base.
Related to neo4j#1270
…unning neo4j-admin database migrate (neo4j#1679)
…certificates (neo4j#1688) Servers act as both servers and clients, and will complain if they only have one of the modes
…o4j#1700) Co-authored-by: Reneta Popova <reneta.popova@neo4j.com>
@yirensum additional context - https://neo4j.atlassian.net/wiki/spaces/Cluster/pages/511606802/Lighthouse+GA+plan --------- Co-authored-by: NataliaIvakina <82437520+NataliaIvakina@users.noreply.github.com> Co-authored-by: Reneta Popova <reneta.popova@neo4j.com> Co-authored-by: Neil Dewhurst <neil.dewhurst@neo4j.com>
Describe two new public metrics of lighthouse @yirensum additional context - https://neo4j.atlassian.net/wiki/spaces/Cluster/pages/511606802/Lighthouse+GA+plan --------- Co-authored-by: Reneta Popova <reneta.popova@neo4j.com>
@yirensum additional context - https://neo4j.atlassian.net/wiki/spaces/Cluster/pages/511606802/Lighthouse+GA+plan --------- Co-authored-by: NataliaIvakina <82437520+NataliaIvakina@users.noreply.github.com> Co-authored-by: Reneta Popova <reneta.popova@neo4j.com>
Docs of neo-technology/neo4j#26148. --------- Co-authored-by: Reneta Popova <reneta.popova@neo4j.com>
Beginning in 5.19 you need to put the database name ahead of the named arguments. Otherwise, you get a File 'neo4j' doesn't exist error Cherry-picked from neo4j#1689 Co-authored-by: Nathan Smith <nsmith_piano@hotmail.com>
      
  
    Collaborator
      
  
  | 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.