Implementations may not deprecate a field that the interface hasn't deprecated

At a glance

• Identifier: #1053
• Stage: RFC 3 / Accepted
• Champion: @benjie
• Latest activity: Spec PR merged on 2025-05-01
• Spec PR: https://github.com/graphql/graphql-spec/pull/1053
• Related:
  • wg#1331

Spec PR description

This PR addresses a spec validation omission; if an interface field is not deprecated then any implementation of that interface field should also not be deprecated. I.e. the following schema should be invalid, but before this PR it is valid:

interface Node {
  id: ID!
}

type Foo implements Node {
  id: ID! @deprecated(reason: "...")
}

type Query {
  foo: Foo
}

To solve this, either the deprecation should be removed, or the id field on Node should also be deprecated:

interface Node {
  id: ID! @deprecated(reason: "...")
}

Relevant action item: https://github.com/graphql/graphql-wg/issues/1331

GraphQL.js Implementation: https://github.com/graphql/graphql-js/pull/3986