Release January 20, 2026#2582
Open
github-actions[bot] wants to merge 121 commits intomainfrom
Open
Conversation
fix: use immediate input value for Enter navigation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
fix: get redirectTo from the url params instead of the headers
github-actions
Bot
force-pushed
the
changeset-release/from-canary
branch
from
0fc4cb5 to
6629180
Compare
…ieve the flags in the middleware as well.
… for plugins. Disabledby default.
Feature/private catalog
Contains a Storyblok renderer on pages/index & pages/[…url] Includes multi language support and renderes for RowHeroBanner and RowLinks
…rror) halfway through Cursor: The issue was a TTY handling bug in graphql-codegen's CLI. When running in Cursor's terminal without a proper TTY: The spinner/progress output was suppressed The exit code was incorrectly set to 1 The fix was to pipe gc-gql-codegen through cat, which forces proper output handling
…er bug 1. pages/page/[...url].tsx used getCategoryStaticPaths to enumerate paths, feeding category URLs into the cmsPage query. Any category URL without a matching CMS page identifier triggered a redirect from getStaticProps, which Next.js rejects during prerender — crashing the build. Return empty paths with fallback: 'blocking'. 2. Layout.graphql queried cmsBlocks(["footer_links_block"]) but the prop was destructured-and-discarded in LayoutNavigation/LayoutMinimal. Footer is rendered from Storyblok's globalConfig. Removed the dead query.
The example had several leftovers from a half-completed migration off Magento CMS: - pages/page/[...url].tsx — CMS page handler whose getStaticPaths called getCategoryStaticPaths (returns Magento category URLs). Feeding those into cmsPage caused getStaticProps to redirect during prerender, which Next.js rejects — crashing next build. - Layout.graphql queried cmsBlocks(["footer_links_block"]) but the prop was destructured-and-discarded in both layout components — the Footer is fully driven by Storyblok's globalConfig. - pages/404.tsx rendered a Magento cms_no_route CMS page with a hardcoded fallback if absent. Remove the page route, the dead cmsBlocks query, the magento-cms fallback in 404 (hardcoded text remains), and the @graphcommerce/magento-cms dependency. The Storyblok example is now pure Storyblok for content. Projects that need Magento CMS pages alongside Storyblok can re-add the dep and a route.
proxy.ts had hardcoded LOCALES = ['en', 'nl'] for locale detection. Move the logic to plugins/LocaleRedirectProxy.ts using the FunctionPlugin system, reading locales from the storefront config so it works on any storefront combination. proxy.ts becomes the standard managed re-export.
Move the Storyblok Visual Editor locale-routing logic from the example into @graphcommerce/storyblok-ui as a function plugin with ifConfig: 'storyblok'. Now any project depending on @graphcommerce/storyblok-ui gets Visual Editor locale routing automatically — no manual plugins/ file in the project. The example's plugins/LocaleRedirectProxy.ts now only handles the generic Accept-Language root redirect (project-level opt-in).
Auto-loaded from packages/storyblok-ui/plugins/ for any project depending on @graphcommerce/storyblok-ui. ifConfig: 'storyblok' guards activation. Removed from the example since it's now inherited transitively.
If you depend on @graphcommerce/storyblok-ui you want this plugin.
…r-storyblok drop magento-cms from the Storyblok example
github-actions
Bot
force-pushed
the
changeset-release/from-canary
branch
2 times, most recently
from
6d5a7b4 to
029487f
Compare
feat(graphqlSsrClient): add instantiation with timestamp to apollo shared client
…sands group
Intl.NumberFormat.formatToParts() emits multiple parts with type: 'integer'
(one per thousands group), so key={part.type} collided. Switched to the
array index — parts are already wrapped in suppressHydrationWarning so
SSR/client divergence isn't a concern.
…licate-integer-key Fix duplicate React key warning in NumberFormat for thousands-grouped numbers
github-actions
Bot
force-pushed
the
changeset-release/from-canary
branch
from
029487f to
8bd47ae
Compare
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
3 participants
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.
Automated release PR from canary branch