changesets for branch 7.x

[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 7.x, this PR will be updated.

Releases

@neo4j/[email protected]

Major Changes

• #5755 9c75f92 Thanks @angrykoala! - Remove support for connectOrCreate operations

• #5778 56022ba Thanks @darrellwarde! - The deprecated directed argument has been removed, and queryDirection now only accepts two possible values - DIRECTED (default) and UNDIRECTED.

  Additionally, the directedArgument setting of excludeDeprecatedFields has been removed as these deprecated fields have been removed.

• #5762 87e416b Thanks @darrellwarde! - There have been major changes to the way that full-text search operates.

  The directive now requires the specification of an index name, query name, and indexed fields.

  input FulltextInput {
      indexName: String!
      queryName: String!
      fields: [String]!
  }
  
  """
  Informs @neo4j/graphql that there should be a fulltext index in the database, allows users to search by the index in the generated schema.
  """
  directive @fulltext(indexes: [FulltextInput]!) on OBJECT

  Here is an example of how this might be used:

  type Movie @node @fulltext(indexName: "movieTitleIndex", queryName: "moviesByTitle", fields: ["title"]) {
      title: String!
  }

  Full-text search was previously available in two different locations.

  The following form has now been completely removed:

  # Removed
  {
      movies(fulltext: { movieTitleIndex: { phrase: "The Matrix" } }) {
          title
      }
  }

  The following form as a root-level query has been changed:

  # Old query
  query {
      moviesByTitle(phrase: "The Matrix") {
          score
          movies {
              title
          }
      }
  }
  
  # New query
  query {
      moviesByTitle(phrase: "The Matrix") {
          edges {
              score
              node {
                  title
              }
          }
      }
  }

  The new form is as a Relay connection, which allows for pagination using cursors and access to the pageInfo field.

• #5755 9c75f92 Thanks @angrykoala! - Remove support for @unique directive

• #5768 e338590 Thanks @angrykoala! - Remove overwrite field in connect operations

• #5777 0ecfd71 Thanks @darrellwarde! - The deprecated options argument has been removed.

  Consider the following type definitions:

  type Movie {
      title: String!
  }

  The migration is as below:

  # Old syntax
  {
      movies(options: { first: 10, offset: 10, sort: [{ title: ASC }] }) {
          title
      }
  }
  
  # New syntax
  {
      movies(first: 10, offset: 10, sort: [{ title: ASC }]) {
          title
      }
  }

  The deprecatedOptionsArgument of excludeDeprecatedFields has been removed as it is now a no-op.

• #5789 1a07d40 Thanks @darrellwarde! - The Neo4j GraphQL Library and Introspector now required Node.js 22 or greater.

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

@neo4j/[email protected]

Major Changes

• #5789 1a07d40 Thanks @darrellwarde! - The Neo4j GraphQL Library and Introspector now required Node.js 22 or greater.