feat!: GraphCommerce 11 — drop Node 20, require Node 22+#2626
Open
paales wants to merge 2 commits into
Open
Conversation
- engines.node set to >=22.0.0 <27.0.0 across root + all examples and the hygraph-dynamic-rows-ui package. Drops Node 20 (EOL April 2026), requires Node 22 (Maintenance LTS) at minimum, and allows up to Node 26 (current). - CI: release-canary, release-main and pr-analysis now pin Node 24 (Active LTS, recommended). periodic-build matrix moved from [20, 22] to [22, 24] and actions/setup-node bumped from v3 to v4. - .gitpod.yml bootstrap moved from `nvm install 18` to `nvm install 24`. - Getting-started docs + example READMEs (graphcms, open-source, storyblok) now point at Node 22/24 instead of the various 16/18/20 references they had. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
🦋 Changeset detectedLatest commit: dbf640f The changes in this PR will be included in the next version bump. This PR includes changesets to release 86 packages
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
- Changeset bumps for magento-graphcms, magento-open-source, magento-storyblok and hygraph-dynamic-rows-ui changed from `minor` to `major` so the next release rolls over to GraphCommerce 11. - Added docs/upgrading/graphcommerce-10-to-11.md with the migration steps (Node 22+ minimum, CI/Vercel/Docker pins, reinstall). - Linked the new guide from docs/upgrading/readme.md. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
paales
changed the title
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Promotes the framework to GraphCommerce 11. Node.js 20 hit EOL in April 2026, so we drop it as a supported runtime. The
engines.node, CI matrix, gitpod and docs all now point at the versions Node actually supports.Marked as a breaking / major change (changeset bumps
majorfor the four versioned example/published packages) — under thefixed: [["@graphcommerce/*"]]group this rolls the whole@graphcommerce/*namespace over to11.0.0on the next stable release.There are no source-code or API breaking changes — only the supported Node runtime shifts.
Engine ranges
engines.nodenow>=22.0.0 <27.0.0across the root, all three examples (magento-graphcms,magento-open-source,magento-storyblok) andhygraph-dynamic-rows-ui:CI
release-canary.yml,release-main.yml,pr-analysis.yml:node-version: 20→24.periodic-build.yml: matrix[20, 22]→[22, 24];actions/setup-node@v3→@v4.Other
.gitpod.yml:nvm install 18→nvm install 24.docs/getting-started/create.md+ the three example READMEs: outdatednode 16/18/node 20references →node 22 or 24..devcontainer/devcontainer.jsonleft as-is —lts: trueresolves to v24 automatically.Upgrade guide
New
docs/upgrading/graphcommerce-10-to-11.mdcovering:engines.nodein consumer projectsyarn install && yarn codegen)Linked from
docs/upgrading/readme.md.Node.js status as of 2026-05-20
Test plan
pr-analysis(yarn install + codegen + yarn test) green on Node 24periodic-buildmatrix[22, 24]green for both examplesyarn workspace @graphcommerce/magento-graphcms devon Node 22 and Node 24release-canarykeeps publishing once merged🤖 Generated with Claude Code