changesets for branch dev

[neo4j-team-graphql]

This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to dev, this PR will be updated.

Releases

@neo4j/[email protected]

Minor Changes

• #5746 c581f9e Thanks @mjfwebb! - Add filtering on 1 to 1 relationship custom cypher fields

Patch Changes

• #5738 c6ea37d Thanks @angrykoala! - Add deprecation warning when using @unique

• #5788 62a9f61 Thanks @angrykoala! - Deprecate single element relationships:

  type Movie {
      director: Person @relationship(type: "DIRECTED", direction: "IN")
  }

  In favor of list relationships:

  type Movie {
      director: [Person!]! @relationship(type: "DIRECTED", direction: "IN")
  }

  1-1 relationships cannot be reliably enforced, leading to a data inconsistent between the schema and the database. For this reason, these have been removed in favor of the more accurate list relationships.

• #5771 c56f9b0 Thanks @MacondoExpress! - Deprecate implicit SET:

  mutation {
      updateMovies(update: { id: "2" }) {
          movies {
              id
          }
      }
  }

  in favour of the explicit _SET version:

  mutation {
      updateMovies(update: { id_SET: "2" }) {
          movies {
              id
          }
      }
  }

• #5771 f624668 Thanks @MacondoExpress! - Added implicitSet to the excludeDeprecatedFields setting, to disable generation of the deprecated mutation field without the suffix _SET.

• #5758 7521476 Thanks @angrykoala! - Argument overwrite in connect operations has been deprecated

• #5748 f23bb91 Thanks @darrellwarde! - The connectOrCreate operation has been deprecated and will be removed in the next major version of the Neo4j GraphQL Library. Its implementation has always been more limited than the other operations, so the decision has been taken to remove it for the time being with a view of potentially refocussing on it again in the future.

• #5764 1ec1bd3 Thanks @darrellwarde! - Fix issues Sorting vector search results by score without score in selection set results in error #5759 and Ordering of sorting criteria not honoured in vector search query #5760 to do with sorting vector search results