Skip to content

Conversation

@dependabot
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github May 7, 2024

Bumps org.neo4j:neo4j-cypher from 3.5.0 to 5.19.0.

Release notes

Sourced from org.neo4j:neo4j-cypher'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

Dependabot compatibility score

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)
    You can disable automated security fix PRs for this repo from the Security Alerts page.

pallakartheekreddy and others added 4 commits September 8, 2023 16:56
* Issue #IQ-45 feat: CSP changes

* Issue #KN-585 feat: Single click local installation of knowledge platform

* Issue #KN-603 fix: CSP changes

* Issue #KN-603 fix: remove gcloud hard dependency

* Issue #KN-15 fix:Postman search-service API positive test cases -

* feat (doc): local setup using kubernetes.

Setup of DBs and Taxonomy-Service.

* Issue #KN-15 fix:Postman search-service API Negative test cases

* feat (doc): local setup using kubernetes.

* Issue #KN-439 feat: Handles domain agnostic for Neo4J.

* Issue #KN-439 feat: Handles domain agnostic for Neo4J.

* Issue #KN-439 feat: Handles domain agnostic for Neo4J.

* Issue #KN-439 test: Added the config for unit test.

* Issue #KN-439 feat: Fixed the replacement issue.

* Issue #KN-439 feat: Handles domain agnostic for Cassandra.

* Issue #KN-439 feat: Handles domain agnostic for Cassandra.

* Issue #KN-579 feat: Properties update

* Issue #KN-579 feat: Properties update

* Issue #KN-439 fix: Fixed update scenario where response is return with metadata without reading it again.

* Issue #KN-439 test: Fixed update scenario where response is return with metadata without reading it again.

* Issue #KN-439 merge: csp-migration to release-5.2.0 (#900)

* Issue #KN-439 fix: Fixed saveExternalRelativePath issue for ArrayList
* Issue #KN-439 feat: Added the variable for relative_path_prefix
Co-authored-by: anilgupta <anil.gupta@tarento.com>
Co-authored-by: vinukumar-vs <vinukumar_vs@yahoo.com>

* Issue #KN-427 feat: Test case update

* Issue #KN-427 feat: Test case update

* Issue #KN-439 feat: Fixed ClassCast issue.

* Issue #KN-439 feat: Fixed the NullPointer issue

* Issue #IQ-193 fix: updated code for cname

* Issue #IQ-193 fix: updated code

* Issue #IQ-193 feat: added test cases

* Issue #KN-439 chore: added the migrationVersion in asset, content and collection schema.json

* Issue #KN-439 chore: Added the more fields in metadata list

* Issue #KN-667 fix:  Search-service: Search API - Part 2

* Issue #CO-173 debug: Adding debug statements

* Issue #CO-173 debug: Adding debug statements

* Issue #CO-173 debug: Adding debug statements

* Issue #CO-173 debug: Adding debug statements

* Issue #CO-173 fix: Schema validation fix

* Issue #CO-173 fix: Schema validation fix

* Issue #CO-173 fix: Schema validation fix

* Issue #KN- fix: relational metadata backward compatibility fix

* Issue #KN-730 fix: QR Code and QRRequired inconsistency debug

* Issue #KN-751 fix: Content and collection image publish issue

* Issue #KN-754 feat: Postman DOCS publishing.

* Issue #KN-754 fix: Sunbird License API collection name updated

* Issue KN-767 feat (doc): content service local setup using kubernetes

* Issue KN-767 feat (doc): content service local setup using kubernetes

* Issue KN-767 feat (doc): content service local setup using kubernetes

* Issue KN-767 fix: content service config map updated

* Corrected the typo in line 20

Refer to https://github.com/orgs/Sunbird-inQuiry/discussions/62

* feat : Updated scala version to 2.12

* Issue KN-767 feat: Added Terraform scripts and Helmcharts for one click installation

* Issue KN-767 feat: Removed the unused helmcharts

* Issue KN-767 feat: Updated Readme file .

* Issue KN-767 feat: Updated Readme file .

* Issue KN-767 feat: Removed Unused files .

* Issue KN-767 feat: Added gitignore.

* Issue KN-767 feat: Added Helm chart and terraform file for content-service and added few changes to taxonomy-service.

* Issue KN-767 feat: Added Helm chart and terraform file for search-service

* Issue KN-767 feat: Added Helm chart and terraform file for learning-service ,added configmaps and updated changes in the helmcharts.

* Issue KN-767 feat:Added changes in Neo4j to connect with logstash

* Delete terraform.tfstate

* Delete terraform.tfstate.backup

* Issue KN-767 feat:Added learning service terraform script

* Issue #KN-767 fix: knowlg one click installation for azure added

* Issue #KN-767 fix: dial services helm charts added

* Issue #KN-767 fix: Updated README.md  file

* Issue #KN-767 fix:Added Flink Helm Chart and Terraform script

* Issue #KN-767 fix: knowlg one click installation for flink jobs in azure added

* Revert "Merge branch 'Sunbird-Knowlg:master' into KN-848"

This reverts commit 9c7c619, reversing
changes made to 59e42ec.

* Delete schema.json

* Issue KN-848 fix: Removed the deprecated import and added the alternative

* Issue #KN-767 fix: search service config updated

* Issue #KN-10 feat: Added create framework API

* Issue #KN-10 fix: Updated youtubeurl

* Delete StorageService.scala

* Revert "Delete StorageService.scala"

This reverts commit f633e69.

* Updated Cloud-store-sdk version

* Update YouTubeUrlUtilTest.java

* Update YouTubeURLManagerImplTest.java

* Updated YoutubeUrls

* Issue #KN-10 feat: Added framework cache for read framework

* Issue #KN-10 feat: Updated create framework API

* Undo logger changes

* Update DataNode.scala

* Update DataNode , DefinitionNode

* Updated Youtube URLs

* Update schema

* Issue #KN-10 feat: Added update framework API

* Issue #KN-10 feat: retire framework API added

* Issue #KN-10 feat: Added copy framework API

* Issue #KN-10 fix: create framework API fixes

* Issue #KN-10 feat: Added update and retire framework APIs

* Issue #KN-10 feat: Added update and retire framework APIsIssue #KN-10 feat: Added Publish framework APIs

* Issue #KN-10 feat: framework publish and read API changes

* feat: refactoring jacoco version update

* Issue #KN-10 feat: category, categoryInstance and term APIs Added

* Issue #KN-848 fix: updated scala version and test dependencies

* Issue #KN-848 fix: updated jsonschemavalidator

* Issue #KN-848 fix: updated schema path

* Issue #KN-848 fix: updated schema path

* Issue #KN-848 fix: updated schema path

* Issue #KN-10 feat:Added TestCases for Master Category

* feat: handle in-relationship metadata to set the index

For FrameworkCategory create it uses in relation with Framework. This is not handled properly to set the index value... This commit has the required changes.

* Issue #KN-10 feat:Bug fix in Create Category API

* Issue #KN-10 feat:Added TestCases for CategoryInstance ,Framework Term

* Issue KN-10 fix: get node inRelations data issue fix

* KN-10 fix: index value populating in relation metadata

* Issue IQ-436 feat: code changes for question & questionset v2 api's

* Issue #IQ-436 fix: fixed HttpUrlUtilTest tests

* KN-10 fix: index value populating in relation metadata for term api

* Issue KN-10 fix: Validate translations and bug fix in category

* Issue #IQ-436 fix: updated code to handle NullPointerException

* Issue #IQ-436 fix: fixed build issue

* Issue #IQ-436 fix: fixed build issue

* Issue #KN-848 fix: updated test cases

* Issue #IQ-436 feat: added test cases

* Issue #IQ-436 fix: updated test cases

* Issue #IQ-436 fix: updated test case

* Issue KN-848 feat: taxonomy service migration to SBT.

* Issue #IQ436 feat: updated code for test

* Issue #KN-848 fix: updated test cases

* Issue KN-10 fix: Added Master Category Validation in Category Instance Create API

* Issue KN-10 fix: Added Test Cases

* Issue KN-10 fix: framework read initial commit

* Issue KN-10 fix: read and publish API changes

* Issue KN-10 fix: read framework hierarchy fix

* Issue KN-10 fix: Test Cases for Framework

* Issue KN-10 feat: category terms set in redis on publish

* Issue KN-10 fix: framework copy API changes

* Issue KN-10 fix: master category required schema properties added

* Issue KN-10 fix: Test Cases for Framework

* Issue KN-10 fix: category instance validation issue fix

* Issue #KN-848 fix: updated test cases

* Issue KN-10 fix: framework copy API validation issue fix

* Issue #KN-848 fix: updated application.conf

* Issue #KN-848 fix: updated application.conf and error message

* Issue KN-10 fix: removed commented code

* Issue #KN-848 fix: removed imports

* Issue KN-10 fix: removed println statements

* Issue #KN-848 fix: removed imports

* Issue #KN-848 fix: dummy commit

* Issue #KN-848 fix: test commit

* Issue #KN-848 fix:  updated test

* fix: added connection exception scenario.

* fix: remove Matchers trait from BaseSpec

* fix: upgrade plowermock

* Issue KN-10 fix: DataSubGraph moved to correct folder

* Issue KN-10 fix: test cases issue fixed

* Issue KN-10 test: unit testes added for read & publish apis

* Issue KN-10 fix: Jackson dependency exclusion

* Issue #KN-10 fix: relation index issue fix

* Issue #KN-10 fix: logs added

* Issue #KN-10 fix: index issue fix for categoryInstance

Currently, Framework getting from cache. While creating categoryInstance disabling the cache and getting node from DB

* Issue #KN-10 fix: disable Cache true & false conditions handled

* Issue #KN-10 fix: framework response sort issue fixed

* Issue KN-10 fix: copy framework cache issue fix

* Issue KN-10 fix: framework name issue fix

* Issue KN-10 fix: DIAL code reserve issue fix

* Issue KN-10 fix: DIAL code reserve issue fix

* Issue KN-10 fix: DIAL code reserve issue fix

* Issue KN-10 fix: category cache issue fix

* Issue KN-10 fix: kafka version updated

* Merge Release 5.5.0 into Release-5.6.0 (#982)

* KN : CSP Changes

* KN : CSP Changes - Circle ci changes

* KN : CSP Changes - Circle ci changes

* Update HttpUrlUtilTest.java

* Issue #KN-920 fix: Jenkins Build changes

* Issue #KN-920 fix: Jenkins Build changes

* Issue #KN-920 fix: Jenkins Build changes

* Issue #KN-920 fix: Jenkins Build changes

* Issue #KN-920 fix: Jenkins Build changes

* Issue #KN-920 fix: Jenkins Build changes

* Issue #KN-920 fix: removed console logs

* OCI changes: Added formaturl for content service (#979)

* OCI changes Added formaturl for content service

* ignore test case

* CircleCi issue fix

* CircleCi issue fix

* Update StorageServiceTest.scala

---------

Co-authored-by: Aiman Sharief <aiman.sharief.17@gmail.com>
Co-authored-by: Mahesh Kumar Gangula <mahesh@sanketika.in>

---------

Co-authored-by: vinukumar-vs <vinu.kumar@tarento.com>
Co-authored-by: Anil Gupta <ani2824@gmail.com>
Co-authored-by: vinukumar-vs <vinukumar_vs@yahoo.com>
Co-authored-by: Gourav More <gourav_m@tekditechnologies.com>
Co-authored-by: Mahesh Kumar Gangula <maheshkumargangula@users.noreply.github.com>
Co-authored-by: anilgupta <anil.gupta@tarento.com>
Co-authored-by: Jayaprakash8887 <Jayaprakash.narayanaswamy@tarento.com>
Co-authored-by: Jayaprakash8887 <jayaprakash.n@tarento.com>
Co-authored-by: Kumar Gauraw <er.krgauraw@gmail.com>
Co-authored-by: Surendrasingh Sucharia <surendrasinghs@users.noreply.github.com>
Co-authored-by: aimansharief <110388201+aimansharief@users.noreply.github.com>
Co-authored-by: Aiman Sharief <aiman.sharief.17@gmail.com>
Co-authored-by: shourya-solanki <shourya.solanki@syngenta.com>
Co-authored-by: Mahesh Kumar Gangula <mahesh@sanketika.in>
Issue #KN fix: Updated the mvn command to build for content service
Bumps [org.neo4j:neo4j-cypher](https://github.com/neo4j/neo4j) from 3.5.0 to 5.19.0.
- [Release notes](https://github.com/neo4j/neo4j/releases)
- [Commits](https://github.com/neo4j/neo4j/commits)

---
updated-dependencies:
- dependency-name: org.neo4j:neo4j-cypher
  dependency-type: direct:development
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot bot added the dependencies Pull requests that update a dependency file label May 7, 2024
@sonarqubecloud
Copy link

sonarqubecloud bot commented Jun 5, 2025

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Pull requests that update a dependency file

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants