Merge pull request #103 from mdoleh/federation-package-upgrade

[SPXCORE-19] Upgrade federation for Node 18 compatibility

Author: tlivings

.github/workflows/nodejs.yml

@@ -10,7 +10,7 @@ jobs:
     runs-on: ubuntu-latest
     strategy:
       matrix:
-        node-version: [12.x]
+        node-version: [18.x]
     steps:
     - uses: actions/checkout@v2
     - name: Use Node.js ${{ matrix.node-version }}

CHANGELOG.md

@@ -1,3 +1,8 @@
+### v4.0.0
+
+- Updated @apollo/federation dependency for Node 18 compatibility.
+- Drop Node 12 compatibility.
+
 ### v3.1.0
 
 - Updated graphql-tools dependency to fix security vulnerabilities
@@ -10,7 +15,7 @@
 
 - [FIXED] - imported components directives are merged into final schema
 
-### v3.0.2 
+### v3.0.2
 
 - schema pruning and remove broken makeExecutableSchema override
 
@@ -41,7 +46,7 @@
 
 ### v2.1.4
 
-- [REVERT] - reverting both fixes in [2.1.2](https://github.com/ExpediaGroup/graphql-component/releases/tag/v2.1.2). The change made to unify exclusions and return pre-computed results from non-root resolvers resulted in non-root resolvers not executing when they should have.  Being able to exclude non-root resolvers (not their types) is a valid work around in certain situations.
+- [REVERT] - reverting both fixes in [2.1.2](https://github.com/ExpediaGroup/graphql-component/releases/tag/v2.1.2). The change made to unify exclusions and return pre-computed results from non-root resolvers resulted in non-root resolvers not executing when they should have. Being able to exclude non-root resolvers (not their types) is a valid work around in certain situations.
 
 ### v2.1.3
 
@@ -72,7 +77,7 @@
 ### v2.0.3
 
 - [FIXED] individual field exclusions during import - individual field exclusions will no longer modify the original resolver map that is being imported.
-- [FIXED] tightened up argument forwarding when using `delegateToComponent()` - only arguments the target field is expecting   will be extracted from the calling resolver or from the `args` object provided to `delegateToComponent()` depending on the situation. Previously, there were some unintended argument leakage in certain edge cases.
+- [FIXED] tightened up argument forwarding when using `delegateToComponent()` - only arguments the target field is expecting will be extracted from the calling resolver or from the `args` object provided to `delegateToComponent()` depending on the situation. Previously, there were some unintended argument leakage in certain edge cases.
 
 ### v2.0.2
 

package.json

@@ -1,6 +1,6 @@
 {
   "name": "graphql-component",
-  "version": "3.1.0",
+  "version": "4.0.0",
   "description": "Build, customize and compose GraphQL schemas in a componentized fashion",
   "keywords": [
     "graphql",
@@ -21,7 +21,7 @@
   "repository": "https://github.com/ExpediaGroup/graphql-component",
   "license": "MIT",
   "dependencies": {
-    "@apollo/federation": "^0.28.0",
+    "@apollo/federation": "^0.38.1",
     "@graphql-tools/delegate": "^8.8.1",
     "@graphql-tools/merge": "^8.3.1",
     "@graphql-tools/mock": "^8.7.1",