Main merge dev #386
Merged
Main merge dev #386
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
To align with changes in neo-technology/neo4j#29493
Instead of PR neo4j#253 --------- Co-authored-by: Louise Söderström <[email protected]>
Co-authored-by: Louise Berglund <[email protected]>
Co-authored-by: Louise Berglund <[email protected]>
This error's link (https://neo4j.com/docs/status-codes/current/errors/gql-errors/#_42n26) is not working because it's not listed in the content-nav file due to a typo.
I hope I did this right - here is the accompanying implementation neo-technology/neo4j#29934
Co-authored-by: Lasse Heemann <[email protected]>
…22N06, 42N08, 51N12, 51N27 (neo4j#282) Co-authored-by: Louise Berglund <[email protected]> Co-authored-by: Reneta Popova <[email protected]>
New error used for parsing the vector value constructor function --------- Co-authored-by: Louise Berglund <[email protected]>
As this change will not be visible to the user when they get the error, I opted for not including it in changelog/mark as changed in 2025.04. Let me know if you think otherwise. Co-authored-by: Reneta Popova <[email protected]>
Adapting to neo-technology/neo4j#30353 Co-authored-by: Reneta Popova <[email protected]>
Causing broken link. It's also being addressed in the main branch using this PR neo4j#293, so no need to cherry-pick it.
Co-authored-by: Louise Berglund <[email protected]>
To reflect change made in neo-technology/neo4j#30521
Codes needed to cover errors left over in deperected constructors. [Monorepo PR](neo-technology/neo4j#30680). --------- Co-authored-by: Reneta Popova <[email protected]>
Introduced in neo-technology/neo4j#30884 --------- Co-authored-by: Reneta Popova <[email protected]>
Co-authored-by: Reneta Popova <[email protected]>
This came out of a discussion here neo-technology/neo4j#31828 (comment) --------- Co-authored-by: Reneta Popova <[email protected]>
Co-authored-by: Lidia Zuin <[email protected]> Co-authored-by: Louise Berglund <[email protected]> Co-authored-by: NataliaIvakina <[email protected]> Co-authored-by: JoelBergstrand <[email protected]> Co-authored-by: Hannes Voigt <[email protected]> Co-authored-by: Nick Giles <[email protected]> Co-authored-by: Therese Magnusson <[email protected]> Co-authored-by: ConorNeo <[email protected]> Co-authored-by: Balazs Lendvai <[email protected]> Co-authored-by: Satia Herfert <[email protected]>
Added a new error: neo-technology/neo4j#31206 --------- Co-authored-by: Reneta Popova <[email protected]>
The errors have already been merged. The deprecations come from neo-technology/neo4j#31541 --------- Co-authored-by: Reneta Popova <[email protected]>
Adds error for [PR](neo-technology/neo4j#31952) - unsupported aggregation in NEXT.
Related [PR](neo-technology/neo4j#31804) --------- Co-authored-by: Reneta Popova <[email protected]>
See neo-technology/neo4j#31623 --------- Co-authored-by: Reneta Popova <[email protected]>
Introduced in neo-technology/neo4j#31849 --------- Co-authored-by: Reneta Popova <[email protected]>
…to the corresponding constraint errors (neo4j#338) Updated in neo-technology/neo4j#31435 (merged the day after cutoff for 2025.06) --------- Co-authored-by: Reneta Popova <[email protected]>
Rename 42I64 to unsupported operation [Neo4j PR](neo-technology/neo4j#32037) --------- Co-authored-by: Reneta Popova <[email protected]>
Introduced in: neo-technology/neo4j#31819 --------- Co-authored-by: Natalia Ivakina <[email protected]>
Error codes introduced in [PR Formatting temporals](neo-technology/neo4j#32184) --------- Co-authored-by: Reneta Popova <[email protected]>
Adds error 42I67 introduced in [PR](https://github.com/pulls) --------- Co-authored-by: Reneta Popova <[email protected]>
Since text-2.0 index provider is legacy now. Also, fix the message:) --------- Co-authored-by: Natalia Ivakina <[email protected]> Co-authored-by: Reneta Popova <[email protected]>
Co-authored-by: Reneta Popova <[email protected]>
This status represents invalid elements on Packstream messages. --------- Co-authored-by: Reneta Popova <[email protected]>
|
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
19 participants
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.