All Versions
135
Latest Version
Avg Release Cycle
53 days
Latest Release
101 days ago

Changelog History
Page 2

  • v5.7.2 Changes

    April 20, 2026

    🛠 Fixes

    • 🚑 #512 - Updated HotChocolate.Language dependency from 13.9.14 to 13.9.16 to resolve critical vulnerability (GHSA-qr3m-xw4c-jqw3: stack overflow via deeply nested GraphQL documents)

  • v5.7.1 Changes

    August 12, 2025

    🛠 Fixes

    • #466 Include enum-typed input fields in introspection per GraphQL spec

    Full Changelog : 5.7.0...5.7.1

  • v5.7.0 Changes

    August 06, 2025

    🔄 Changes

    • 📇 QueryInfo Support: Added optional query execution information that can be included in the result extensions. Enable with ExecutionOptions.IncludeQueryInfo = true to get metadata about:

      • Operation type (Query, Mutation, Subscription)
      • Operation name
      • Types queried and their selected fields
      • Total number of types and fields queried
      • This is useful for query analysis, debugging, and monitoring GraphQL usage patterns

    • 🛠 Fix #441 (PR #455) - Have your argument class (including an InputType) class inherit ArgumentsTracker or implement IArgumentsTracker to be able to tell if a variable is just the dotnet default value or is set from the query (variable or inline) with args.IsSet. You can also include IArgumentsTracker as an argument in your mutations etc. This is useful if you method usings simple arguments e.g. MyMutation(Guid id, string name) vs. a [GraphQLArguments] object.

    • 👍 #461 - EntityGraphQLEndpointRouteExtensions.MapGraphQL now supports chunked requests

    • 🚚 RequiredAuthorization is not settable allowing you to change or overwrite it after creation. Also now has Clear() methods to remove authentication

    🛠 Fixes

    • Throw error on a query that has fragments with a cycle as per the GraphQL spec and to prevent infinite loops.
    • #442 - Fix issue when a service field with a bulk resolver is on a parent field named differently to the dotnet underlying object property

  • v5.6.1 Changes

    April 28, 2025

    🛠 Fixes

    • #443 - Allow */* & application/* Accept headers in followSpec option for MapGraphQL
    • #443 - Allow expected headers to not be listed first when using followSpec option for MapGraphQL
    • 👍 Better support for multiple items in a single Accept header when using followSpec option for MapGraphQL
    • #449 - Fix issues with self referencing query and connection paging

  • v5.6.0 Changes

    January 29, 2025

    🔄 Changes

    • ➕ Added additional framework target net9.0
    • ResolveWithService and ResolveWithServices methods are now marked obsolete. Please use Resolve in the same way
    • 0️⃣ #430 - MapGraphQL has new parameter followSpec which changes the behavior to follow https://github.com/graphql/graphql-over-http/blob/main/spec/GraphQLOverHTTP.md and is false by default in v5.x. If set to true it will follow the spec, the major change being that if the HTTP request was valid you'll get a 200 status code even if there may be GraphQL errors in the response. Note this will be the default behavior in version v6.
    • ➕ Add IsNullable to the IField interface to control setting the nullability of the field return type in the schema

    🛠 Fixes

    • #435 - fix isAny() in filter
    • 🛠 Fix issue selecting fields from an object a service field returns where the GraphQL field name differs from the dotnet property name.

    Example a field that returns a User type using a service and you are changing the field names in the schema like below

    schema.Type\<User\>().AddField("username",u=\>u.Name,"Username")
    • #439 - Fix using fields / properties with key words (null, true, false) at the start of the name in the filter expressions
    • Related to #430 - Make sure if the schema says a field is not nullable, that it is not returned as null when using null to exit a mutation or field on error.
    • 🛠 Fix issue where an expression extracted from a service field may clash with a existing field name

    🆕 New Contributors

    Full Changelog : 5.5.3...5.6.0

  • v5.5.3 Changes

    November 24, 2024

    🛠 Fixes

    • #432 - filter expression was incorrectly using bit-wise OR or OrElse

  • v5.5.2 Changes

    November 15, 2024

    🛠 Fixes

    • #418 - Fix issue where field expressions using ctx.Entities.FirstOrDefault(<filter>) (First*, Last*, Single* methods with a filter) would duplicate the filter expression on each execution (e.g. making ctx.Entities.Where(<filter>).Where(<filter>).FirstOrDefault()). This also caused EntityFramework not to use it's cache for the expression
    • 🛠 Fix issue with RequiresAnyRole() being called on a field with multiple roles added them as requiring all those roles vs. any role. This did not effect the [GraphQLAuthorize] attribute

  • v5.5.1 Changes

    November 14, 2024

    🛠 Fixes

    • 👍 #425 - As per GraphQL Spec, Interfaces are not supported for Input Types
    • #426 - Fix custom directives with no arguments.
    • 💅 #427/#428 - Fix issue with connection style paging field extension when using last and before arguments

  • v5.5.0 Changes

    October 25, 2024

    🔄 Changes

    • ➕ Add IgnoreAttributes to SchemaBuilderOptions - A list of Attribute types which will cause the builder to ignore the field/property when building the schema. These are additional to GraphQLIgnoreAttribute
    • ⚠ .Resolve<>() method on field changes return type to object? to avoid warnings when returning a valid nullable service call etc.
    • ➕ Add support for using a struct type as an object type in the schema, allowing you to query the fields on it. Previously it only worked if you added the struct as a Scalar Type
    • 👍 #419 - Add support for using isAny([]) on nullable types

    🛠 Fixes

    • 👉 Make sure top level types have access checked (Query, Mutation and Subscription)
    • 🛠 Fix #392 - Better handle null checks when executing against in-memory data
    • #363 - Only use ToListWithNullCheck when we know we are executing with services, or have been told not to separate the execution.

  • v4.2.0 Changes

    🔄 Changes

    • #281 - Implement allowed exceptions to allow exceptions to come into the error result when running with IsDevelopment == false as users not be able to modify the exceptions being thrown in order to have them implement IExposableException. Exceptions may be allowed with an exact type match, or allowed including all types that inherit it

    🛠 Fixes

    • Prevent double SQL (when using against EF) query on base type (4.1 regression)
    • 🚚 #279 - Remove duplicate fields when creating expressions
    • #280 - Fix for mutations that return interfaces/unions