@neo4j/graphql@5.11.5

Patch Changes

• #5996 a5962ea Thanks @angrykoala! - Fix error "SchemaModel not available on subscription mechanism" with some subscriptions engines when used with Federation

• #5969 80fb066 Thanks @angrykoala! - Add addVersionPrefix to cypherQueryOptions in context to add a Cypher version with CYPHER before each query:

  {
      cypherQueryOptions: {
          addVersionPrefix: true,
      },
  }

  This prepends all Cypher queries with a CYPHER [version] statement:

  CYPHER 5
  MATCH (this:Movie)
  WHERE this.title = $param0
  RETURN this { .title } AS this

@neo4j/graphql-ogm@5.11.5

Patch Changes

• Updated dependencies [a5962ea, 80fb066]:
  • @neo4j/graphql@5.11.5

@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.