GraphQLConf 2026

@deprecated is usually treated as a client-facing hint. However, in federated GraphQL, it can evolve into a set of patterns that shape governance, runtime behavior, observability, and even gateway planning. In this lightning talk, I’ll take @deprecated on a five-stop journey across the federation lifecycle — 1) schema hint, 2) schema shaping, 3) runtime feedback, 4) client-aware telemetry, and 5) gateway power. I’ll close with a brief developer experience bonus — how structured deprecation metadata can feed code-gen/IDE tooling to suggest non-deprecated alternatives while queries are being written. The goal of the talk is to share a practical mental model and guardrails for keeping large federated graphs evolvable, observable, and safe.