1 Release published by 1 person

• v17.0.0-alpha.9

  published Jun 11, 2025

4 Pull requests merged by 3 people

• Suggestions for federation links

  #4436 merged Jun 11, 2025

• feat: pass abortSignal to resolvers via GraphQLResolveInfo

  #4425 merged Jun 10, 2025

• Implement schema coordinate spec as of 2025-06-06

  #4432 merged Jun 9, 2025

• Updates to schema coordinates (#3044)

  #4422 merged Jun 5, 2025

7 Pull requests opened by 6 people

• pass assumeValid to constructors

  #4427 opened Jun 5, 2025

• Keep order of specified definitions consistent with the spec

  #4428 opened Jun 5, 2025

• Descriptions on executable documents

  #4430 opened Jun 6, 2025

• move name validation in production to separate validation step

  #4431 opened Jun 6, 2025

• docs: move migrate from express graphql guide to graphqlJS docs

  #4433 opened Jun 9, 2025

• Prevents injecting Node.js globals like process, which can break browser features when loading graphql from ESM-based CDN like esm.sh

  #4434 opened Jun 10, 2025

• Subscriptions docs suggestions

  #4435 opened Jun 10, 2025

7 Unresolved conversations

Sometimes conversations happen on old items that aren’t yet closed. Here is a list of all the Issues and Pull Requests with unresolved conversations.

• Schema Coordinates

  #3044 commented on Jun 10, 2025 • 15 new comments

• Add coordinate field to schema element definitions

  #3808 commented on Jun 10, 2025 • 2 new comments

• GraphQLSchema does not completely validate names

  #4362 commented on Jun 8, 2025 • 0 new comments

• feat(mergeAST): add mergeAST utility

  #4359 commented on Jun 9, 2025 • 0 new comments

• docs: testing graphQL servers

  #4374 commented on Jun 5, 2025 • 0 new comments

• buildClientSchema: build enum type value maps lazily

  #4424 commented on Jun 6, 2025 • 0 new comments

• Use no-op for production instanceOf

  #4426 commented on Jun 10, 2025 • 0 new comments