GraphQL Specification Update

• Added changes to support the Sept '25 update to the specification.
• Notable Changes
  • Added support for the @oneOf directive (see documentation for details)
  • Added support for the schema coordinates labeling system where applicable in error messages etc.
    • Supporting objects in the type system now expose a SchemaCoordinates property
  • Expanded query document description support to include operations, fragments and variable declarations
  • Expanded deprecation labeling support across schema elements
  • Updated unicode handling to support the full range of unicode characters (including emojis)

Bug Fix

• Fixed a bug where an invalid, escaped unicode sequence may assume additional characters were part of the sequence

Forward Compatability Notice

• WARNING: Library version v1.5.x will be the last version to support .NET Standard 2.0.

Other

• Published dedicated build targets for .NET 10

Bug Fix

• Fixed a bug with the subscription library where some clients with strict protocol enforcement were unable to deserialize some messages.

Other

• Published dedicated build targets for .NET 9

What's Changed

• Updated a System.Text.Json dependency based on a published security advisory.
• This release includes no internal code changes

What's Changed

• Updated several Microsoft dependencies based on a published security advisory.
• This release includes no internal code changes

What's Changed

• Removed .NET 7.0 support due to it being end of life.
• Added editable message properties on IGraphMessage (Code, Message, Exception)
• Minor bug fix to apply the correct default error code when a graph message is generated without a code
  • -unknown- has been corrected to UNKNOWN (constant value: Constants.ErrorCodes.Default)

Full Changelog: v1.3.2...v1.4.0

Bug Fixes

• Fixed a bug where input fields marked with [GraphSkip] were not ignored early enough during schema generation and were causing naming conflicts with included fields.
• Fixed an issue where an input object with a field of a list of items of the same object type would cause a exception. Self referencing lists of input objects should now properly resolve.

Full Changelog: v1.3.1...v1.3.2

Bug Fixes

• Fixed a bug where by calling .AddGraphQL() for the same schema type across different IServiceCollection instances would result in an erroneous duplicate registration error message. You can now successfully add the same schema type to different DI instances. (@Fgruntjes)
• Fixed a validation bug where when a field set with multiple spread fragments with invalid graph type references would cause a 500 internal server error instead of triggering rule 5.5.1.2 . The invalid graph type name(s) will now be correctly identified and an appropriate response will be generated.

Major Changes

• Added support for minimal api style resolvers
• Added support for method-level DI resolution and the [FromServices] attribute
• Added a new nullability format strategy to support programmatic formatting of schema items during startup
  • Added built-in support for declaring strings, lists and reference types as non-nullable by default
• Added support for "schema-level scalars". Scalar implementations can now vary per registered schema

Breaking Changes

• Removed support for the GraphNameFormatter and merged its functionality into the new GraphSchemaFormatStrategy object
• v2.0 contains several large scale internal code and namespace refactors including a number of breaking changes to ISchemaItem and related interfaces. See the related PRs for a full change log of items affected if you have done any heavy customization to the type system.
• Don't hesitate to reach out with any questions.

Related PRs: #143, #141

See related PRs for sample code and a complete list of changes

.NET 8 Support

• Added support for .NET 8
• Removed .NET 6 star wars api, added .NET 8 version

Bug Fixes

• Fixed an issue with SchemaItemPath causing a race condition when attempting to build multiple test server instances simultaniously (@Fgruntjes)
• Fixed a bug with records not being allowed to used as OBJECT graph types in some scenarios
• Fixed a bug with using the [GraphType] attribute on structs. You should now be able to supply a properly customized the name for a graph type built from a struct.
• Fixed a bug where by a [BatchTypeExtension] or [TypeExtension] may fail to build introspection data properly when referencing a graph type with a customized name.
• Fixed a bug where field executions would not always obey schema isolation rules in some scenarios.

Other Changes

• Made the message parameter on GraphController.NotFound(message) optional. A default, generic message will be included in the query errors when not supplied.

Related PRs: #132, #135, #137, #138, #139, #140

Bug Fixes

• Fixed a bug where the authentication and authorization middleware components would log erroneous warning messages if their functionality was bypassed via a custom component earlier in the pipeline. Both middleware components will now only initiate a logging session if they perform work for the current request.

• Fixed a bug where the authorization middlware was using a globally scoped IAuthorizationService causing an authorization failure in some non-traditional security configurations. The authorization middleware will now use an auth service scoped to the active request.