NewYour coding agent can read the release notes before it upgrades.Set up the MCP server →
npm, #3292 most downloaded on npm
A set of utils for faster development of GraphQL tools
Latest stable
12.3.3
Last release 12 days ago
10 Nov 2026
Ships fairly regularly
a new release about every 2 weeks
Nearly every release is documented
notes for 60 of the last 60 stable releases
Nothing withdrawn
no release was ever pulled
7 years old
3721 releases · first in 2020
Drag across the ruler to compare, or tap a release to open it.
Nothing published for this version
Nothing published for this version
Nothing published for this version
When you have an argument in a nested field that uses the variable from the gateway request like below;
Your coding agent can read these notes before it upgrades. Set up the MCP server →
#1971 4065b7f Thanks @ardatan! - Reuse the existing variables from the gateway request correctly
When you have an argument in a nested field that uses the variable from the gateway request like below;
query GetArticles($date: Datetime!) {
view {
articlesByDate(date: $date) {
id
title
publishedAt
}
}
}
And if Datetime is renamed from DateTime in the original schema, the transform wasn't applied correctly to the variable definitions, and the delegation failed with an error in the subgraph like Datetime is not known.
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
If the argument uses a variable definition on the gateway request, keep and re-use it as-is.
#1948 584a293 Thanks @Tolsee! - Respect existing variable definitions from the gateway request;
query ($var1: String = "default") {
rootField(arg1: $var1)
}
query ($arg1: String = "default") {
rootField(arg1: 2) {
someField(arg2: $arg1)
}
}
In that case it should be delegated as:
query ($arg1: String = "default", $rootField_arg1: String = "default") {
rootField(arg1: $rootField_arg1) {
someField(arg2: $arg1)
}
}
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Do not pass percent(x) labels to the progressive override handler
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
If you have a subgraph schema like below;
#1901 e92c5a9 Thanks @ardatan! - Do not add required fields if they are already present in the original selection set.
For example in Federation;
If you have a subgraph schema like below;
type Book @key(fields: "upc otherUpc shop { id }") {
upc: ID!
otherUpc: ID!
shop: Shop!
}
type Shop @key(fields: "id") {
id: ID!
name: String!
location: Location!
}
And when you send a mutation like below;
mutation {
buyBook(input: { bookUpc: "test" }) {
book {
upc
otherUpc
shop {
id
name
location {
address1
city
state
}
}
}
}
}
Previously, the gateway would add the required key fields again to the selection set when resolving the type like below;
mutation {
buyBook(input: { bookUpc: "test" }) {
book {
upc
otherUpc
- upc
- otherUpc
- shop { id } # from the key fields
shop {
id
name
location {
address1
city
state
}
}
}
}
}
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Updated dependency `@graphql-tools/utils@^11.0.0` ↗︎ (from ^10.10.3, in dependencies)
#1842 93aa767 Thanks @dependabot! - dependencies updates:
@graphql-tools/utils@^11.0.0 ↗︎ (from ^10.10.3, in dependencies)Updated dependencies [93aa767]:
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
One column per quarter.