upgrade executor to non-duplicating incremental delivery format

.changeset/@graphql-tools_utils-6243-dependencies.md

@@ -0,0 +1,5 @@
+---
+"@graphql-tools/utils": patch
+---
+dependencies updates:
+  - Added dependency [`dlv@^1.1.3` ↗︎](https://www.npmjs.com/package/dlv/v/1.1.3) (to `dependencies`)

.changeset/@graphql-tools_utils-6790-dependencies.md

@@ -0,0 +1,5 @@
+---
+"@graphql-tools/utils": patch
+---
+dependencies updates:
+  - Added dependency [`dlv@^1.1.3` ↗︎](https://www.npmjs.com/package/dlv/v/1.1.3) (to `dependencies`)

.changeset/chatty-dryers-breathe.md

@@ -0,0 +1,5 @@
+---
+'@graphql-tools/utils': minor
+---
+
+Add helper function `memoize3of4` for memoizing values.

.changeset/fifty-bobcats-jog.md

@@ -0,0 +1,43 @@
+---
+'@graphql-tools/executor': major
+---
+
+Support the new non-duplicating Incremental Delivery format.
+
+GraphQL Incremental Delivery is moving to a [new response format without duplication](https://github.com/graphql/defer-stream-wg/discussions/69).
+
+This PR updates the executor within graphql-tools to avoid any duplication of fields as per the new format, a BREAKING CHANGE, (released in graphql-js `v17.0.0-alpha.3`). The original version of incremental delivery was released in graphql-js `v17.0.0-alpha.2`.
+
+The new format also includes new `pending` and `completed` entries where the `pending` entries assign `ids` to `defer` and `stream` entries, and the `completed` entries are sent as deferred fragments or streams complete. In the new format, the `path` and `label` are only sent along with the `id` within the `pending` entries. Also, incremental errors (i.e. errors that bubble up to a position that has already been sent) are sent within the `errors` field on `completed` entries, rather than as `incremental` entries with `data` or `items` set to `null`. The missing `path` and `label` fields and different mechanism for reporting incremental errors are also a BREAKING CHANGE.
+
+Along with the new format, the GraphQL Working Group has also decided to disable incremental delivery support for subscriptions (1) to gather more information about use cases and (2) explore how to interleaving the incremental response streams generated from different source events into one overall subscription response stream. This is also a BREAKING CHANGE.
+
+Library users can explicitly opt in to the older format by call `execute` with the following option:
+
+```ts
+import {execute, IncrementalDeliveryPresetLegacy} from 'graphql'
+
+const result = await execute({
+  ...,
+  incrementalPreset: IncrementalDeliveryPresetLegacy,
+});
+```
+
+The default value for `incrementalPreset` when omitted is `IncrementalDeliveryPreset2023_06_22`, which enables the new behaviors described above. The new behaviors can also be disabled granularly as follows:
+
+```ts
+import {execute, IncrementalDeliveryPreset2023_06_22} from 'graphql'
+
+const result = await execute({
+  ...,
+  incrementalPreset: {
+    ...IncrementalDeliveryPreset2023_06_22,
+    allowSubscription: true
+  }
+});
+```
+
+Setting `deferWithoutDuplication` to `false` will re-enable deduplication according to the older format.
+Setting `useIncrementalNotifications` to `false` will (1) omit the `pending` entries, (2) send `path` and `label` on every `incremental` entry, (3) omit `completed` entries, and (4) send incremental errors within `incremental` entries along with a `data` or `items` field set to `null`.
+Setting `allowSubscription` to `false` will re-enable the use of incremental delivery with subscriptions.
+```

.changeset/mean-parents-do.md

@@ -0,0 +1,15 @@
+---
+'@graphql-tools/utils': minor
+---
+
+Support the new incremental protocol for `mergeIncrementalResult`.
+
+The `mergeIncrementalResult` function can now merge the [new response format without duplication](https://github.com/graphql/defer-stream-wg/discussions/69).
+
+```ts
+const executionResult = { data: { user: { name: 'John' } }, pending: [{ id: '0', path: [] }] };
+const incrementalResult = { incremental: [{ id: '0', data: { user: { age: 42 } } }] };
+
+console.log(mergeIncrementalResult({ incrementalResult, executionResult }));
+// logs: { user: { age: 42, name: 'John' } }
+```

.changeset/thirty-bees-know.md

@@ -0,0 +1,7 @@
+---
+'@graphql-tools/utils': minor
+---
+
+Add new incremental delivery fields to the `ExecutionResult` type.
+
+The `id`, `subPath`, `pending` and `completed` properties specified by [in the following proposal](https://github.com/graphql/defer-stream-wg/discussions/69) are now defined within `ExecutionResult`.

.eslintrc.cjs

@@ -102,6 +102,7 @@ module.exports = {
         'prefer-rest-params': 'off',
         'no-throw-literal': 'off',
         'promise/param-names': 'off',
+        camelcase: ['error', { allow: ['IncrementalDeliveryPreset2023_06_22'] }],
       },
     },
     {

.github/workflows/pr.yml

@@ -4,6 +4,9 @@ on:
     branches:
       - master
 
+concurrency:
+  group: ${{ github.workflow }}-${{ github.ref }}
+
 jobs:
   dependencies:
     uses: the-guild-org/shared-config/.github/workflows/changesets-dependencies.yaml@main
@@ -20,7 +23,7 @@ jobs:
     with:
       npmTag: alpha
       buildScript: build
-      nodeVersion: 18
+      nodeVersion: 22
     secrets:
       githubToken: ${{ secrets.GUILD_BOT_TOKEN }}
       npmToken: ${{ secrets.NODE_AUTH_TOKEN }}

.github/workflows/release.yml

@@ -4,6 +4,9 @@ on:
     branches:
       - master
 
+concurrency:
+  group: ${{ github.workflow }}-${{ github.ref }}
+
 jobs:
   stable:
     permissions:
@@ -12,7 +15,7 @@ jobs:
     uses: the-guild-org/shared-config/.github/workflows/release-stable.yml@main
     with:
       releaseScript: release
-      nodeVersion: 18
+      nodeVersion: 22
     secrets:
       githubToken: ${{ secrets.GUILD_BOT_TOKEN }}
       npmToken: ${{ secrets.NODE_AUTH_TOKEN }}