A production incident was traced back to a seemingly innocuous GraphQL schema change. A field was renamed in one service
2023-10-27