@graphcommerce/docs 10.1.0-canary.9 → 11.0.0-canary.45

package/CHANGELOG.md

@@ -1,5 +1,77 @@
 # Change Log
 
+## 11.0.0-canary.45
+
+## 10.1.0-canary.44
+
+## 10.1.0-canary.43
+
+## 10.1.0-canary.42
+
+## 10.1.0-canary.41
+
+## 10.1.0-canary.40
+
+## 10.1.0-canary.39
+
+## 10.1.0-canary.38
+
+## 10.1.0-canary.37
+
+## 10.1.0-canary.36
+
+## 10.1.0-canary.35
+
+## 10.1.0-canary.34
+
+## 10.1.0-canary.33
+
+## 10.1.0-canary.32
+
+## 10.1.0-canary.31
+
+## 10.1.0-canary.30
+
+## 10.1.0-canary.29
+
+## 10.1.0-canary.28
+
+## 10.1.0-canary.27
+
+## 10.1.0-canary.26
+
+## 10.1.0-canary.25
+
+## 10.1.0-canary.24
+
+## 10.1.0-canary.23
+
+## 10.1.0-canary.22
+
+## 10.1.0-canary.21
+
+## 10.1.0-canary.20
+
+## 10.1.0-canary.19
+
+## 10.1.0-canary.18
+
+## 10.1.0-canary.17
+
+## 10.1.0-canary.16
+
+## 10.1.0-canary.15
+
+## 10.1.0-canary.14
+
+## 10.1.0-canary.13
+
+## 10.1.0-canary.12
+
+## 10.1.0-canary.11
+
+## 10.1.0-canary.10
+
 ## 10.1.0-canary.9
 
 ## 10.1.0-canary.8

package/framework/mesh.md

@@ -92,3 +92,35 @@ To make sure changes are picked up during development set the config value
 `graphqlMeshEditMode: true` in your graphcommerce.config.js or set the env
 variable `GC_GRAPHQL_MESH_EDIT_MODE=1`. This _will_ make the frontend
 considerably slower.
+
+## Routing Magento traffic over an internal network
+
+When the frontend runs next to Magento — e.g. both in the same Kubernetes
+cluster — the mesh's server-side Magento requests (GraphQL and REST) can be
+routed directly to an internal Service instead of hairpinning over the public
+load balancer. Set in the **runtime** environment (e.g. a Kubernetes
+ConfigMap):
+
+```
+GC_MAGENTO_ENDPOINT_SERVER=http://varnish.magento-namespace.svc.cluster.local
+```
+
+Every request whose URL starts with the origin of `GC_MAGENTO_ENDPOINT` is
+rewritten to this origin, so both the GraphQL endpoint and the REST endpoint
+are covered. `GC_MAGENTO_ENDPOINT` itself stays the public URL: it keeps
+feeding build-time schema introspection, `images.remotePatterns` and the media
+URLs Magento generates. The rewrite also sends `X-Forwarded-Proto: https`,
+which the TLS-terminating proxy would normally add — Magento needs it to keep
+generating `https://` URLs.
+
+Caveats:
+
+- Both `GC_MAGENTO_ENDPOINT_SERVER` and `GC_MAGENTO_ENDPOINT` must be present
+  in the runtime environment; the rewrite happens per request at runtime.
+- Do **not** set `GC_MAGENTO_ENDPOINT_SERVER` in the build environment: schema
+  introspection (`gc-mesh build`) and static generation run where the internal
+  endpoint is typically not reachable. Unset, the feature is a no-op.
+- Point it at the Varnish service (not the webserver directly) to keep
+  Magento's GraphQL full-page cache in the path.
+- When a NetworkPolicy guards the Magento namespace, allow ingress from the
+  frontend namespace to the Varnish pods.

package/getting-started/create.md

@@ -11,7 +11,7 @@ start building.
 ### Preparations
 
 - MacOS, Windows with WSL2 or Linux
-- Install and use node 20: `nvm install 20` or `nvm use 20`
+- Install and use node 22 or 24: `nvm install 24` or `nvm use 24`
 - Install yarn: `corepack enable`
 
 ## Step 1: Create a GraphCommerce app

package/package.json

@@ -2,10 +2,10 @@
   "name": "@graphcommerce/docs",
   "homepage": "https://www.graphcommerce.org/docs",
   "repository": "github:graphcommerce-org/graphcommerce/docs",
-  "version": "10.1.0-canary.9",
+  "version": "11.0.0-canary.45",
   "sideEffects": true,
   "peerDependencies": {
-    "@graphcommerce/prettier-config-pwa": "^10.1.0-canary.9"
+    "@graphcommerce/prettier-config-pwa": "^11.0.0-canary.45"
   },
   "prettier": "@graphcommerce/prettier-config-pwa"
 }

package/upgrading/graphcommerce-10-to-11.md

@@ -0,0 +1,94 @@
+# Upgrading from GraphCommerce 10 to 11
+
+GraphCommerce 11 drops support for Node.js 20 (EOL April 2026) and aligns the
+framework with the
+[Node.js release schedule](https://nodejs.org/en/about/previous-releases). The
+minimum supported version is now Node.js 22, and Node.js 24 is recommended.
+
+There are no source-code or API breaking changes in this release — only the
+supported runtime has shifted.
+
+## Step 1: Upgrade your local Node.js
+
+| Version              | Status as of May 2026                                 |
+| -------------------- | ----------------------------------------------------- |
+| Node.js 20 (Iron)    | **EOL** — no longer supported                         |
+| Node.js 22 (Jod)     | Maintenance LTS through ~April 2027 — **new minimum** |
+| Node.js 24 (Krypton) | Active LTS since Oct 2025 — **recommended**           |
+| Node.js 26           | Current since May 2026 — supported                    |
+
+Pick whichever LTS you prefer; `>=22.0.0 <27.0.0` is the accepted range.
+
+With `nvm`:
+
+```bash
+nvm install 24
+nvm use 24
+```
+
+Then re-enable corepack so the project's pinned yarn version is picked up:
+
+```bash
+corepack enable
+```
+
+## Step 2: Bump `engines.node` in your project
+
+If you copied the example's `engines.node` into your own `package.json`, update
+it from the old GC 10 value to the GC 11 range:
+
+```diff
+  "engines": {
+-   "node": ">=20 <24.0.0"
++   "node": ">=22.0.0 <27.0.0"
+  }
+```
+
+If your project doesn't set `engines.node` itself, nothing to do — the engine
+constraint is inherited from `@graphcommerce/magento-graphcms` (or whichever
+example you bootstrapped from).
+
+## Step 3: Update your CI / hosting
+
+Anywhere that pins a Node version, move from 20 to 22 or 24:
+
+- **GitHub Actions** (`.github/workflows/*.yml`):
+
+  ```diff
+  - uses: actions/setup-node@v4
+    with:
+  -   node-version: 20
+  +   node-version: 24
+  ```
+
+  If you use `actions/setup-node@v3`, bump it to `@v4` while you're there.
+
+- **Vercel** — set the project's "Node.js Version" to 22.x or 24.x under
+  Settings → General. Vercel's `20.x` option will be removed in line with Node's
+  own EOL.
+
+- **Docker images** — update any `FROM node:20…` to `FROM node:22-…` or
+  `FROM node:24-…` (alpine/slim/bookworm variants all work).
+
+- **Devcontainer / Gitpod / Codespaces** — Gitpod users can switch their
+  `.gitpod.yml` bootstrap from `nvm install 18` (or 20) to `nvm install 24`.
+  Devcontainer setups that use `"lts": true` resolve to v24 automatically and
+  need no change.
+
+## Step 4: Reinstall
+
+After upgrading Node:
+
+```bash
+rm -rf node_modules .next
+yarn install
+yarn codegen
+yarn dev
+```
+
+## Notes
+
+- Node 22 will move from Maintenance LTS to EOL around April 2027 — start
+  planning the move to Node 24 (or 26) before then.
+- Node 25/26 are non-LTS "current" releases. They're accepted by the engine
+  range, but production deployments should generally stay on the latest LTS.

package/upgrading/readme.md

@@ -110,6 +110,7 @@ After resolving the diff issues, manually process upgrade instructions:
 - [Upgrading to GraphCommerce 7 to 8](../upgrading/graphcommerce-7-to-8.md)
 - [Upgrading to GraphCommerce 8 to 9](../upgrading/graphcommerce-8-to-9.md)
 - [Upgrading to GraphCommerce 9 to 10](../upgrading/graphcommerce-9-to-10.md)
+- [Upgrading to GraphCommerce 10 to 11](../upgrading/graphcommerce-10-to-11.md)
 
 Run and validate your local environment: