Skip to content

Upgrade to Neo4j Ogm 3.1.1 #14132

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

Closed
wants to merge 1 commit into from
Closed

Upgrade to Neo4j Ogm 3.1.1 #14132

wants to merge 1 commit into from

Conversation

meistermeier
Copy link
Contributor

The Spring Data Neo4j version (Kay) used in this version
of Spring Boot (2.0.x) does expect Neo4j-OGM 3.0.x to work with.
Because Spring Boot defines a 3.1.x version and a downgrade
does not feel right, Neo4j-OGM 3.1.1 brings back the compatibility for SDN Kay.
Fixes #13999

The Spring Data Neo4j version (Kay) used in this version
of Spring Boot (2.0.x) does expect Neo4j-OGM 3.0.x to work with.
Because Spring Boot defines a 3.1.x version and a downgrade
does not feel right, Neo4j-OGM 3.1.1 brings back the compatibility for SDN Kay. 
Fixes #13999
@spring-projects-issues spring-projects-issues added the status: waiting-for-triage An issue we've not yet triaged label Aug 18, 2018
@snicoll snicoll changed the title Upgrade Neo4j-OGM dependency to 3.1.1 Upgrade to Neo4j Ogm 3.1.1 Aug 19, 2018
@snicoll snicoll added type: dependency-upgrade A dependency upgrade and removed status: waiting-for-triage An issue we've not yet triaged labels Aug 19, 2018
@snicoll snicoll added this to the 2.0.5 milestone Aug 19, 2018
snicoll added a commit that referenced this pull request Aug 19, 2018
* pr/14132:
  Upgrade to Neo4j Ogm 3.1.1
@snicoll snicoll closed this in 7e570ac Aug 19, 2018
@snicoll snicoll self-assigned this Aug 19, 2018
@meistermeier meistermeier deleted the patch-1 branch August 20, 2018 06:17
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type: dependency-upgrade A dependency upgrade
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants