GraphQL @deprecated Directive vs Apollo Server Introspection: Compatibility Across Versions

In Apollo Server 3.1.0 and newer, introspection queries correctly report @deprecated fields according to the GraphQL specification. A field annotated with @deprecated(reason: "use newField") will return isDeprecated: true and the matching deprecationReason string in the introspection result.

Version Consistency

The regression observed in the 3.0.0-beta series was addressed in subsequent patches. In current stable versions of 3.x and 4.x, the behavior is consistent regardless of how the schema is constructed:

• SDL-First: When using makeExecutableSchema with string templates, the parser correctly maps the @deprecated directive to the __type introspection-fields.
• Code-First: When using object-based definitions (e.g., GraphQLObjectType), setting the deprecated and deprecationReason properties on the field definition yields the same introspection output.

Verification Steps

To verify this in your specific environment, execute the following introspection query against your Apollo Server instance:

query CheckDeprecation {
  __type(name: "YourTypeName") {
    fields {
      name
      isDeprecated
      deprecationReason
    }
  }
}

If isDeprecated returns false despite the directive being in your code, check for the following:

• Schema Stitching/Merging: If you are merging multiple schemas, the deprecation metadata may not be passing through the gateway merge layer.
• Custom Directives: Ensure no custom directive is shadowing the standard @deprecated name, which could prevent the default parser from processing the metadata.

To provide a more specific diagnosis, please confirm if you are using schema stitching, federation, or a monolithic schema defined via makeExecutableSchema.