@neo4j/graphql@3.24.4

Important

This is an important patch release which ensures compatibility with the upcoming Neo4j 2025 release. Before you upgrade to Neo4j 2025, please ensure that you have applied this patch upgrade.

Patch Changes

• #5966 a369ffb60 Thanks @angrykoala! - Add support for CalVer editions of neo4j

@neo4j/graphql-ogm@3.24.4

Important

This is an important patch release which ensures compatibility with the upcoming Neo4j 2025 release. Before you upgrade to Neo4j 2025, please ensure that you have applied this patch upgrade.

Patch Changes

• Updated dependencies [a369ffb60]:
  • @neo4j/graphql@3.24.4

@neo4j/graphql@4.4.8

Important

This is an important patch release which ensures compatibility with the upcoming Neo4j 2025 release. Before you upgrade to Neo4j 2025, please ensure that you have applied this patch upgrade.

Patch Changes

• #5965 f623c7e Thanks @angrykoala! - Add support for CalVer editions of neo4j

@neo4j/graphql-ogm@4.4.8

Important

This is an important patch release which ensures compatibility with the upcoming Neo4j 2025 release. Before you upgrade to Neo4j 2025, please ensure that you have applied this patch upgrade.

Patch Changes

• Updated dependencies [f623c7e]:
  • @neo4j/graphql@4.4.8

@neo4j/graphql@6.3.0

Important

This is an important patch release which ensures compatibility with the upcoming Neo4j 2025 release. Before you upgrade to Neo4j 2025, please ensure that you have applied this patch upgrade.

Minor Changes

• #5934 c666adc Thanks @MacondoExpress! - Introduced the typename filter that superseded the typename_IN filter.
  As part of the change, the flag typename_IN has been added to the excludeDeprecatedFields setting.

  const neoSchema = new Neo4jGraphQL({
      typeDefs,
      features: { excludeDeprecatedFields: { typename_IN: true } },
  });

Patch Changes

• #5937 7f1bc65 Thanks @MacondoExpress! - Aggregations on ID fields are now deprecated.
  As part of the change, the flag idAggregations has been added to the excludeDeprecatedFields setting.

  const neoSchema = new Neo4jGraphQL({
      typeDefs,
      features: { excludeDeprecatedFields: { idAggregations: true } },
  });

• #5943 6153d68 Thanks @darrellwarde! - Fix Cypher when filtering by aggregations over different relationship properties types

• #5953 ebbb921 Thanks @angrykoala! - Add support for CalVer editions of neo4j

@neo4j/graphql@5.11.4

Important

This is an important patch release which ensures compatibility with the upcoming Neo4j 2025 release. Before you upgrade to Neo4j 2025, please ensure that you have applied this patch upgrade.

Patch Changes

• #5954 dbd5e40 Thanks @angrykoala! - Add support for CalVer editions of neo4j

@neo4j/graphql-ogm@5.11.4

Important

This is an important patch release which ensures compatibility with the upcoming Neo4j 2025 release. Before you upgrade to Neo4j 2025, please ensure that you have applied this patch upgrade.

Patch Changes

• Updated dependencies [dbd5e40]:
  • @neo4j/graphql@5.11.4

@neo4j/graphql@7.0.0-alpha.2

Important

This is an important patch release which ensures compatibility with the upcoming Neo4j 2025 release. Before you upgrade to Neo4j 2025, please ensure that you have applied this patch upgrade.

Major Changes

• #5936 d48ea32 Thanks @mjfwebb! - Changes the result projection where there are multiple relationships between two nodes.

  In the case of using the connection API then multiple relationships will still be represented, as there is the ability to select the relationship properties. In the non-connection API case, the duplicate results will only return distinct results.

• #5931 5ce7d1d Thanks @darrellwarde! - DateTime and Time values are now converted from strings into temporal types in the generated Cypher instead of in server code using the driver. This could result in different values when the database is in a different timezone to the GraphQL server.

• #5933 8bdcf6b Thanks @mjfwebb! - When performing a connect operation, new relationships are always created.

@neo4j/graphql@7.0.0-alpha.1

Major Changes

• #5927 530d8cd Thanks @MacondoExpress! - The typename_IN filter has been renamed to typename.

• #5898 a912404 Thanks @MacondoExpress! - Aggregations are no longer generated for ID fields.

Minor Changes

• #5868 46ab2fa Thanks @angrykoala! - Add suport for generic update operators:

  mutation {
      updateMovies(update: { name: { set: "The Matrix" } }) {
          movies {
              id
              name
          }
      }
  }

• #5873 17911fc Thanks @MacondoExpress! - Introduce a new style for filtering relationships and connections.
  The quantifiers SOME | NONE | SINGLE | ALL are now available as a nested input object.

  Relationship

  {
      movies(where: { genres: { some: { name: { equals: "some genre" } } } }) {
          actorCount
      }
  }

  Connection

  {
      movies(where: { genresConnection: { some: { node: { name: { equals: "some genre" } } } } }) {
          actorCount
      }
  }

Patch Changes

• #5871 722c650 Thanks @angrykoala! - Deprecate individual mutations in favor of generic mutations

  • _SET
  • _POP
  • _PUSH
  • _INCREMENT
  • _ADD
  • _DECREMENT
  • _SUBTRACT
  • _MULTIPLY
  • _DIVIDE

• #5882 7254acf Thanks @angrykoala! - Deprecates old aggregation filters for relationships in favor of more generic filters:

  Before:

  query Movies {
    movies(
      where: { actorsAggregate: { node: { lastRating_AVERAGE_GT: 6 } } }
    ) {
      title
    }
  }

  Now:

  query Movies {
    movies(
      where: {
        actorsAggregate: { node: { lastRating: { average: { gt: 6 } } } }
      }
    ) {
      title
    }
  }

• #5897 4f3b068 Thanks @MacondoExpress! - Deprecate relationship filtering using the non-generic version such as actors_SOME: { title_EQ: "The Matrix" } in favor of the generic input actors: { some: { title: { eq: "The Matrix" } } }.
  The setting excludeDeprecatedFields now contains the option relationshipFilters to remove these deprecated filters.

• #5897 917482b Thanks @MacondoExpress! - Deprecate attribute filtering using the non-generic version such as title_EQ: "The Matrix" in favor of the generic input title: { eq: "The Matrix" }.
  The setting excludeDeprecatedFields now contains the option attributeFilters to remove these deprecated filters.

• #5879 5c7ba22 Thanks @angrykoala! - Add generic filters for aggregations:

  {
      posts(where: { likesAggregate: { node: { rating: { average: { eq: 3.2 } } } } }) {
          title
      }
  }

• #5882 7254acf Thanks @angrykoala! - Introduce the flag "aggregationFilters" to remove deprecated aggregation filters:

  const neoSchema = new Neo4jGraphQL({
      typeDefs,
      features: { excludeDeprecatedFields: { aggregationFilters: true } },
  });

@neo4j/graphql@6.2.3

Patch Changes

• #5904 64d4da1 Thanks @a-alle! - Fix error message for wrong requireAuthentication argument on @authorization directive

• #5906 80df6f3 Thanks @Masadow! - Fixed a bug that appears when filtering on interface relationships