Bumping CI Neo4j version to 5.19 #300
Draft
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
grolt or py2neo fails with neo4j >= 5.19
|
We should wait to merge any solution to #291 until after we have resolved this, otherwise it's possible that our changes pass our tests for 5.18 but don't actually work for e.g. 5.22. |
|
Blocking #292. |
|
@ianmkenney can we characterize these failure further? Do we know why we see test suite failures when we set neo4j > 5.18? |
|
It's not clear to me why the failures are happening right now. I agree we need to figure these out fairly soon. |
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.
grolt or py2neo fails with neo4j >= 5.19