Bump org.neo4j.test:neo4j-harness from 5.26.1 to 5.26.2

[dependabot]

Bumps org.neo4j.test:neo4j-harness from 5.26.1 to 5.26.2.

Release notes

Sourced from org.neo4j.test:neo4j-harness's releases.

Neo4j 1.9.0 stable release

The 1.9 release of Neo4j builds upon the previous 1.8 releases and brings extensive improvements in stability and performance. In addition, Neo4j 1.9 Enterprise introduces auto-clustering support, with dramatically simplified configuration and deployment for high demand production use.

• Support for auto-clustering in Neo4j Enterprise, which replaces the previous Zookeeper based HA clustering, provides a streamlined deployment process and is much safer and more resilient in failure scenarios.
• New neo4j-arbiter tool, which acts as a voting instance in a Neo4j cluster but does not keep a data store or handle transactions.
• Addition of string manipulation, timestamp and other functions to the Cypher query language.
• Improvements to memory utilization, which reduces working memory requirements and improves overall performance.
• New REST endpoints for inspecting cluster status information (master, slave, etc).
• Correction of several concurrency and performance issues.
• Improvements to Online Backup in Neo4j Enterprise, including auto-detection of full vs incremental backup based on existing content at the backup location.
• Updates to Neo4j server webadmin, including welcome pages for new users.

It is recommended to upgrade all previous Neo4j installations to this release. Neo4j 1.9 does not require any explicit upgrade to persistent stores created using Neo4j 1.7 and 1.8 installations, however current users of Neo4j Enterprise must consult the documentation and update the cluster configuration. Please see the deployment and cluster upgrade sections of the Neo4j manual for more detail. Also note that Neo4j 1.9 is tested and supported with Oracle JRE 7. Users of previous Java versions should upgrade to Oracle JRE 7 when deploying Neo4j 1.9.

As part of the Neo4j 1.9 release, multiple behaviours and features of Neo4j have been declared as deprecated, in order to help users prepare for the removal of these in the next major Neo4j release. A list of deprecations can be found in the Neo4j manual.

For a full summary of changes in this release, please review the CHANGES.TXT file contained within the distribution.

Neo4j 1.8.0 stable release

The 1.8 release of Neo4j provides extensive improvements in stability and performance. As an incremental service release, Neo4j 1.8 builds upon the previous 1.6 and 1.7 releases and provides full backward compatibility.

This release includes the following corrections and improvements:

• Correction of several concurrency issues affecting performance in multi- threaded configurations.
• Correction of several concurrency issues that infrequently affect consistency of persisted data.
• Optimization of high-availability (HA) protocols to increase write performance.
• Support for zero-downtime rolling upgrades in HA clusters.
• Improvements to transaction distribution in HA clusters, providing greater resistance to branching.
• Configurable rotation of logical logs.
• Support for streamed responses to REST API requests.
• Support for bi-directional traversals, branch state and path expanders in the traversal framework.
• Performance improvements to several graph algorithms.
• Support in the Cypher language for writing graph data and updating auto-indexes (manual indexes are not supported).
• Extensions to the Cypher language to allow the use of patterns as expressions and predicates.
• Correction of several issues in the Cypher parser when using collections and when aggregating.
• Improved error reporting in Cypher and more reliable statement parsing.
• Support for explicit transactions in neo4j-shell.

It is recommended to upgrade all previous Neo4j installations to this release. Neo4j 1.8 does not require any explicit upgrade to persistent stores created using Neo4j 1.6 and 1.7 installations. Please see the deployment section of the Neo4j manual for more detail.

For a full summary of changes in this release, please review the CHANGES.TXT file contained within the distribution.

Commits

• ea56d44 Revert "Bump Lucene to 9.12.1"
• 80a11fd Bump Lucene to 9.12.1
• b13aad2 Fix code-gen issue with value population
• ff1d5e1 Introduce a dedicated channel modification API ()
• 2362e9f Fix browser loading ()
• 770e13c Fixed a race condition when reconfiguring network pipelines ()
• 35277fb fix: don't move WITH with subquery expressions past MATCH
• 6ddc5bc Fix value population bug for cached rel properties
• 92bb7b7 Make sure ErrorGqlStatusObjectImplementation is serializable. ()
• 5b9927c Jetty 12 Upgrade () ()
• 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 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)

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud