November 2026
The changes in the November 2026 releases that ask something of your project, newest first. Each one names the first version of each package that has it: you need the change only when you move from below that version to it or above. Each one is the change since the October 2026 release, as it stood on 18 November 2026. Releases later this month are added here.
On 5 November every @evolve-framework/* and @evolve-storefront/* package left 0.x. From that release on, a breaking change is a major version.
Orders are read with a signed link or the session
Section titled “Orders are read with a signed link or the session”In: feature-order 2.0.0
orderByPublicId is no longer used. An order is read with the payment’s
returnToken (orderBySignedLink), or with sessionOrder, which answers only
an order the current session placed, as a signed-in buyer or as a guest. An
order id on its own no longer reads a stranger’s order.
- Configure
orderLinkSecreton the framework’sPaymentModule, the same secret as onOrderModule. The gateway then appendsreturnTokento every payment return URL. This needs a framework that servessessionOrderandPaymentTargetInput.token. - Stop using
orderByPublicIdin your own documents. The persisted documents change:OrderConfirmationById,OrderLookupByPublicIdandOrderPaymentMethodsByPublicIdare gone, andOrderConfirmationBySignedLink,OrderConfirmationBySession,OrderLookupBySessionandOrderPaymentMethodsBySessionare new. Register them again where documents are persisted. - Hand the
returnTokenon from the return route.resolvePaymentReturncalls the lookup aslookupOrder(id, returnToken)and putsreturnTokenon theorder,confirmationandresumedestinations. - Pass it to the confirmation:
readOrderConfirmation(gqlClient, id, returnToken),orderConfirmationQueryOptions({ …, returnToken })oruseAwaitedOrderConfirmation(id, { returnToken }). Without it, a payment-first return cannot find the order the cart became. - Read an order page as
readOrder(gqlClient, returnToken ? { signedLink: returnToken } : { id }). readOrderPaymentMethodstakes{ id }instead of{ publicId }.- Pay again with
pay.mutate({ order, paymentMethod, returnToken }).
Changing a member’s roles takes several roles
Section titled “Changing a member’s roles takes several roles”In: feature-organization 2.0.0
EditRolesFormFields renders a checkbox per role instead of a single-role
select. For a site that composes EditRolesForm itself:
defaultRoleId?: stringis nowdefaultRoleIds?: string[]. Passassociate.roles.map((role) => role.id).onValidSubmitreceives{ roleIds: string[] }instead of{ roleId: string }. PassroleIdstouseUpdateAssociateRolesas is.EditRolesFormContextValuehasdefaultRoleIdsandroleErrorin place ofdefaultRoleId.- The messages
Organization.form.role-label,role-placeholderandroleId-errorare removed; the fields readroles-labelandroleIds-error.
A product page’s quote request needs the purchase reference
Section titled “A product page’s quote request needs the purchase reference”In: feature-product 2.0.0
QuoteRequestSchema refuses a request without purchaseOrderNumber, and
QuoteRequestInput["purchaseOrderNumber"] is a string rather than
string | undefined. A server action that parses the posted form with the
schema returns its error to the sheet. Code that builds a QuoteRequestInput
itself passes the reference.
The message ProductBusiness.quote.reference lost its “(optional)” suffix,
and required, reference-description and reference-error are new. An
override of reference drops the suffix it copied.
The warehouse stock message is split in two
Section titled “The warehouse stock message is split in two”In: feature-product 2.0.0
ProductBusiness.warehouse-stock.in-stock is replaced by in-stock-count
("{count} in stock", inside the stock tag) and in-warehouse
("in {warehouse}", after it). Move an override of in-stock to the two new
keys and delete the old one.
The MCP endpoint is stateless and can sign customers in with OAuth
Section titled “The MCP endpoint is stateless and can sign customers in with OAuth”In: mcp-core 2.0.0
The HTTP server keeps nothing between requests. There is no Mcp-Session-Id,
GET and DELETE /mcp answer 405, and a server is built per request. A
client that follows the MCP protocol needs no change.
- A call without credentials runs in a guest session that ends with the call,
so a cart does not survive it. Enable OAuth to keep a session, or send one
with
PROXY_AUTH_ENABLED. - A session refreshed during a call is no longer kept by the server. A caller
with
PROXY_AUTH_ENABLEDgets the renewed tokens back on the response asX-Access-Token,X-Refresh-TokenandX-Data-Token, and has to store them. - The package is built on
@modelcontextprotocol/serverinstead of@modelcontextprotocol/sdk. setSessionStoreContextholds for the rest of a request over HTTP, and no longer for later requests.shutdownHttpServeris removed, along withrecordSessionCreated,recordSessionClosedand the metricsmcp.sessions.active,mcp.sessions.createdandmcp.sessions.closed.- Rate limiting no longer keys on a session. With OAuth it keys on the
connected client, with
RATE_LIMIT_ADDRESS_MAXfor requests without a valid token, and otherwise on the IP address. Behind a proxy, settrustProxyon the application.
To upgrade:
- Replace
@modelcontextprotocol/sdkwithMcpServerfrom@evolve-framework/mcp-core, or build the server withcreateMcpServerFactory. - Remove calls to
shutdownHttpServerand to the session metrics. - Send store and token headers on every request, not only on
initialize. A proxy withPROXY_AUTH_ENABLEDforwards the customer’s tokens each time, and stores the tokens a response returns in place of those it sent. Keep them server-side. - A flow without OAuth that needs one guest across calls, such as one that
fills a cart, starts the guest session through the gateway itself and sends
it with
PROXY_AUTH_ENABLED. - Keep state a tool needs in a tool argument or the gateway, not in
getSessionContextbetween requests. - To keep carts and let customers sign in, set
MCP_OAUTH_SECRETS,MCP_INTERACTION_SECRET,MCP_PUBLIC_URLandMCP_LOGIN_URL, and passoauthtocreateMcpModule.
MCP health goes through HealthModule
Section titled “MCP health goes through HealthModule”In: mcp-core 2.0.0
createHealthcheckHandleris removed. Compose aHealthModuleinstead.registerMcpRoutesno longer serves/healthcheck, and itshealthcheckoption is gone. Compose aHealthModulenext to it.createMcpModuletakeshealth: falsein place ofhealthcheck: false.- The
/healthcheckbody is{ componentName, ok, release }instead of{ componentName, message: "OK" }. The status code is unchanged.
createMcpModule also serves GET /readiness, which answers 503 until the
gateway in GATEWAY_ENDPOINT answers.
Payment return URLs must lie on an allowed storefront origin
Section titled “Payment return URLs must lie on an allowed storefront origin”In: commercetools 2.0.0, commercetools-adyen 2.0.0,
commercetools-buckaroo 2.0.0, commercetools-paynl 2.0.0,
commercetools-stripe 2.0.0
paymentCreate answers a successUrl, failureUrl or cancelUrl outside
the allowed origins with a ValidationError whose fields carry
ORIGIN_NOT_ALLOWED, and creates no payment. The /redirect routes of Adyen,
Pay.nl, Stripe and Buckaroo answer such a URL with a 400. Buckaroo no longer
follows the legacy next query parameter on POST /redirect.
- Build one
ReturnOrigins(from@evolve-framework/commercetools/payments), conventionally from a comma-separatedSTOREFRONT_ORIGINS, and pass it toPaymentModuleand to everyAdyenPaymentAdapter,PaynlPaymentAdapter,StripePaymentAdapterandBuckarooPaymentAdapter. Where the providers run in a separate payment service, that service and the graph service need the same list. - List every origin a shopper can pay from: each market and brand domain, a
portal domain, staging, and
localhostfor development. Wildcards are not supported, so a preview deployment on a generated hostname fails. - A payment adapter of your own with its own redirect route calls
returnOrigins.allows()on the URL before redirecting. - Mollie, pay-on-account and gift cards need nothing.
import { ReturnOrigins } from "@evolve-framework/commercetools/payments";
const returnOrigins = new ReturnOrigins( process.env.STOREFRONT_ORIGINS!.split(","),);
new PaymentModule({ clientFactory, customTypes, payments, returnOrigins });new AdyenPaymentAdapter({ clientFactory, config, messagePublisher, returnOrigins });Payment webhooks need their secret
Section titled “Payment webhooks need their secret”In: commercetools-adyen 2.0.0, commercetools-buckaroo 2.0.0,
commercetools-paynl 2.0.0, commercetools-stripe 2.0.0
Each adapter’s init() throws when the secret it verifies webhooks with is
empty: Adyen hmacKey, Stripe webhookSecret, Buckaroo
credentials.secretKey, and Pay.nl credentials.apiToken and
credentials.serviceSecret. Set them from your provider’s dashboard before
you upgrade.
A Pay.nl exchange call must be signed with SHA-256 for the configured
serviceId; anything else is answered 403. A Buckaroo push updates only the
transaction its Transaction.Key names.
Internal routes refuse calls without a secret
Section titled “Internal routes refuse calls without a secret”In: commercetools 2.0.0, sfcc 2.0.0, sitemap 2.0.0
Routes that were open when no secret was set now answer 401 to every call,
and the module logs an error when it mounts them. Set the secret, or, only
where something in front of the route already authenticates, set
allowUnauthenticated: true.
| Route | Upgrade |
|---|---|
The HTTP route of ApiExtensionModule (and createHttpHandler, createFastifyHandler) |
Set secret to the token the commercetools extension sends: an AuthorizationHeader authentication with headerValue Bearer <secret>. A Lambda that commercetools invokes directly is unaffected |
The internal routes of PaymentProviderModule and RemotePaymentPublisher |
Pass secret to PaymentProviderModule, and the same secret to the RemotePaymentAdapter that calls it |
POST /token/anonymous and POST /api/create-session of the SFCC AuthModule |
Pass secret and send authorization: Bearer <secret> from the server that calls them |
/rebuild and /rebuild/partitions of SitemapModule |
Pass secret and send authorization: Bearer <secret> from the scheduler, or set routes: false where the job only runs on a schedule |
Also in these releases:
BasePaymentAdapter.createTransactionrefuses a payment the cart, order or invoice does not hold, and charges the payment’samountPlannedinstead of the amount in the request.- An SFCC token refresh reads the session type from the access token SLAS returns, not from the refresh token.
- One sitemap rebuild runs at a time; a second answers 409.
/rebuildrefuses aconcurrencyoutside 1 tomaxConcurrency, which defaults to 8.
The Pub/Sub push handler verifies its token
Section titled “The Pub/Sub push handler verifies its token”In: cloud-adapter-gcp 2.0.0
createPubSubHandler answers every delivery with 401 unless it is told how to
verify the push subscription’s OIDC token. For every service that runs it:
-
Turn on authentication on the push subscription: a service account to sign as, and an audience (by default the push endpoint’s URL).
-
Pass the same values to the handler:
createPubSubHandler(handler).start({path: "/events",auth: {audience: process.env.PUBSUB_PUSH_AUDIENCE,serviceAccountEmail: process.env.PUBSUB_PUSH_SERVICE_ACCOUNT,},}); -
Only where something in front of the route already authenticates, such as Cloud Run’s IAM check, set
allowUnauthenticated: trueinstead.
A Medusa cart mutation acts only on the session’s carts
Section titled “A Medusa cart mutation acts only on the session’s carts”In: medusa 2.0.0
A cart is the session’s when it is its active cart, belongs to its signed-in
customer, or is a cart of the company the session acts for. Any other cart is
answered as a cart that does not exist, in every cart mutation, the delivery
mutations, cartRename, cartSetCurrent, and orderPlace and
paymentCreate on a cart.
A storefront that keeps a cart id itself, such as in a cookie, and sends it without the session that created the cart gets “cart not found”. Rely on the session’s active cart, or pass the id of one of the signed-in customer’s own carts.
Algolia follows the Evolve Algolia data model
Section titled “Algolia follows the Evolve Algolia data model”In: search-algolia 2.0.0, commercetools 2.0.0, search 1.1.0
The index names and the record shape change. Reindex every index after you upgrade, and update InstantSearch code or dashboard configuration that reads the old fields.
- Both adapters take a required
environment(tst,acc,prd). Pass the same value to both. - Index names are
<environment>_<type>[_<language>][_<sort>], such asprd_product_nl_price_asc, without the store. Two stores in one Algolia application must both passresolveIndexName: storeIndexName, or they overwrite each other’s records. objectIDis the product key, or the id for a product without one.categoryIdsholds readable category paths (clothing > men) andcategoryPageIdis gone.startingPriceand a variant’spriceare the lowest gross price per currency in major units,{ "EUR": 19.95 }; facet onstartingPrice.EUR.descriptionis no longer written.toAlgoliaRecordtakes the scope as its second argument, andtoProductDocumentthrows for a record without_doc.StoredAlgoliaProductRecord,AlgoliaProductPriceandAlgoliaAttributeValueare removed.- A
ProductSearchQuerywith acategoryIdmust carry itscategoryKeys. The commercetoolsDocumentSearchProviderfills them in. - A full reindex applies the settings in code (
productIndexSettings). Facets, synonyms and rules set in the dashboard are kept.
A Payload project composes its own config
Section titled “A Payload project composes its own config”In: payload 2.0.0
evolveCms() and EvolveCmsOptions are removed.
@evolve-framework/payload/config exports the collections, blocks, fields,
hooks and plugins the plugin assembled. Replace
plugins: [...evolveCms(options)] with the composed config in the package
README’s Usage section:
- Add
@payloadcms/plugin-multi-tenantto your dependencies, unless the config hadmultiTenant: false. - Set
blocks: payloadBlocks(blocks), and pass the same list to the collections that take one and toPayloadModule. - List the collections:
usersCollection(true),tenantsCollection,contentPageCollection(blocks),catalogPageCollection(blocks),articlePageCollection(blocks),articleOverviewPageCollection(blocks),topicCollection,authorCollection,contentSnippetCollection(blocks),mediaCollection(media),navigationCollection,redirectCollection,siteCollection,siteSettingsCollectionandmessagesCollection. - Move the options:
keyPatternstoconfigureKeyPatterns(keyPatterns),marketstoconfigureMarkets(markets),contentEventsto thecontentEvents(options)plugin, andcatalogto thecatalogPickers(catalog)plugin. Forusers: false,multiTenant: falseorcollections: false, leave out what they turned off. - End
pluginswithadminLayout()and thenmultiTenantPlugin({ userHasAccessToAllTenants, collections: tenantScopedCollections }). - Run
payload migrate:create. A config that composes whatevolveCms()gave produces an empty migration; delete it.
Recurring orders follow commercetools’ native model
Section titled “Recurring orders follow commercetools’ native model”In: feature-recurring-order 2.0.0
A recurring order is a cart’s or shopping list’s lines ordered again on a recurrence policy. What the native model does not have is removed.
- Pass the shop’s schedules to
RecurringOrderFormasrecurrencePolicies, fromuseRecurrencePolicies().sourceOptionstakes carts and shopping lists only. The form only creates:recurringOrder,addresses,minOrderDateandonCancelare gone.onValidSubmithands over{ cartId | shoppingListId, recurrencePolicyKey, validFrom?, validUntil? }, anderrortakes the mutation’sError. RecurringOrderDetail:onPlaceNow/isPlacingNowbecomeonOrderNow/isRequestingOrderNow, withhasRequestedOrderNowfor the notice, andonEnd/isEndingbecomeonCancel/isCanceling.RecurringOrderStatusBadgeandRecurringOrderDetailActionstakestateinstead ofstatus:ACTIVE,PAUSED,FAILED,EXPIREDorCANCELED.- Query options and cache keys take
scope(the business unit’s id, or"customer") instead ofbusinessUnitId, and so doesinvalidateRecurringOrders.useRecurringOrdersno longer takesstatus. - Messages:
RecurringOrder.statusisRecurringOrder.state, and thedetailandformkeys follow the new views. Copy your overrides again frommessages/en.json. - Removed:
useUpdateRecurringOrder,useSkipRecurringOrder,useSetOccurrencePurchaseOrderNumber,usePlaceRecurringOrderNow(useuseRequestRecurringOrderNow) anduseEndRecurringOrder(useuseCancelRecurringOrder), their documents, and the componentsRecurringOrderUpcoming,RecurringOrderOccurrenceReference,RecurringOrderHistory,RecurringOrderDetailEndandRecurringOrderDetailSettings. The package changelog lists the removed fields and types.
Stopping a recurring order waits on the framework’s recurringOrderCancel;
leave onCancel off until the framework serves it.
Auth form hooks call their pending state isPending
Section titled “Auth form hooks call their pending state isPending”In: feature-auth 2.0.0
The formProps of useLoginForm, useRegisterForm, usePasswordResetForm
and usePasswordResetRequestForm call the pending state isPending instead of
pending. Rename formProps.pending where you read it.
createRequestContext answers one client address
Section titled “createRequestContext answers one client address”In: core 1.11.0
ipAddress is one address, read from the trusted end of X-Client-IP,
instead of the whole header. createRequestContext(request, { trustedHops })
takes the entry trustedHops places from the right, 1 by default. Count the
client’s own entry and every proxy address after it: behind a Google Cloud
load balancer, pass trustedHops: 2. A trustedHops that is not a positive
integer is rejected.
commercetools product search applies prefilters
Section titled “commercetools product search applies prefilters”In: commercetools 1.0.0, medusa 1.0.0, schemas 1.0.0,
search 1.0.0, search-algolia 1.0.0, search-meilisearch 1.0.0
commercetools’ own product search used to ignore prefilters. It now applies
them, and refuses a prefilter on a key no configured facet covers with
BAD_USER_INPUT. Configure a facet for every prefilter key, or drop the
prefilter.
FilterCondition.value is deprecated in favour of the new values.
RELEVANCE is the default sort, and POPULARITY sorts by rating
Section titled “RELEVANCE is the default sort, and POPULARITY sorts by rating”In: commercetools 1.0.0, contentful 1.0.0, medusa 1.0.0,
payload 1.0.0, schemas 1.0.0, search 1.0.0, search-algolia 1.0.0,
search-meilisearch 1.0.0, sfcc 1.0.0, storyblok 1.0.0,
feature-product 1.0.0
ProductSortOrderType gains RELEVANCE, the engine’s own ranking, and the
default where no sort is named, which used to be POPULARITY. POPULARITY
sorts by average review rating. NAME_ASCENDING and NAME_DESCENDING are
deprecated and no longer offered by productSortOrders.
- Algolia: add a
<index>-rating-descreplica ranked ondesc(rating), then reindex. - Meilisearch: reindex.
- In the storefront, change the default sort you pass to
readFilterStatefrom"POPULARITY"to"RELEVANCE", and the same for adefaultSortonProductListingorProductListingSort. A site that composesProductListingSortitself passesoptions={listing.sortOrders}. KnownProductSortOrderloses the name sorts. Drop overrides of theProductListing.sort.NAME_ASCENDINGandNAME_DESCENDINGmessages, addRELEVANCEif you override the sort labels, and check that yourPOPULARITYlabel reads as rating.
Two unused catalog fields are removed
Section titled “Two unused catalog fields are removed”In: commercetools 1.0.0, medusa 1.0.0, schemas 1.0.0, sfcc 1.0.0
Remove any fragment or generated type that names CategoryOverviewPage, and
drop enabledFacets from queries on ProductListingConfig. Neither was ever
filled.
Reverse charge and export are taxed at 0% per line
Section titled “Reverse charge and export are taxed at 0% per line”In: commercetools 1.0.0, schemas 1.0.0, feature-cart 1.1.0,
feature-order 1.0.0, feature-quote 1.0.0
applyVatRules sets a reverse-charged or exported cart to the External tax
mode with a 0% rate on every line and on shipping. The buyer pays the shelf
price at 0%, also in a shop whose prices include VAT. A negative custom line no
longer takes the VAT off. This has not been reviewed by a tax advisor.
- Replace
taxCategoryKey,reverseChargeLineandexportLinein theapplyVatRulesoptions withlegacyLineSlugs, listing the old lines’ slugs (such as["vat-shifting", "vat-exemption"]). vatShiftingandvatExemptiononCart,Order,QuoteandQuoteRequestare deprecated and null on a new cart. ReadvatOutcomeand the taxed totals instead, also in end-to-end tests.- In the storefront,
Cart,PlacedOrder,Order,Quote,QuoteRequestandQuoteListEntryno longer havevatShiftingandvatExemption; readvatOutcome.treatment.quoteNetTotaltakes onlytotal. Take these storefront versions together with this framework release.
The old content blocks, siteLayout and AbstractPage are gone
Section titled “The old content blocks, siteLayout and AbstractPage are gone”In: contentful 1.0.0, payload 1.0.0, schemas 1.0.0,
storyblok 1.0.0
A storefront query that names a removed type or field fails validation.
| Removed | Read instead |
|---|---|
OneColumnBlock, TwoColumnsBlock, ThreeColumnsBlock |
Columns |
HeroBlock, ContentPage.hero, CatalogPage.hero |
The page’s heading, intro and leadImage; a CampaignBanner for a campaign |
PageTitle |
The page’s heading |
Button, Buttons |
Link |
Teaser, TeaserBlock, TeasersBlock |
Promo, ContentTeaser, PromoList |
CatalogBlock |
CategoryList |
UspBlock |
UspList |
ProductBlock |
ProductList |
CatalogPage.teaserRow |
CatalogPage.promos |
Divider, ImagePositionType |
Nothing |
Query.siteLayout |
Query.site: headerNavigation, footerNavigation, usps, trustRating, paymentMethods and socials |
NavigationMenuItem, MenuBlock |
MenuItem |
RichText.content, RichText.renderer |
RichText.document, embeds and links |
AbstractPage |
Page |
- A column entry placed straight in a page body is answered as
Columnswith that one entry, and rich text there as aRichTextof its own. Select... on RichTextin your body blocks. @evolve-framework/schemasno longer exports the schemas of the removed types, normarkPageHeading. A project block declared against one of them declares it against the replacement.- The package changelogs list the removed exports per CMS.
Contentful, Payload and Storyblok take the content model’s types
Section titled “Contentful, Payload and Storyblok take the content model’s types”In: contentful 1.0.0, payload 1.0.0, storyblok 1.0.0
Content types, collections and blocks take the content model’s snake_case ids,
such as content_page, catalog_page, article_page, rich_text and
site_settings, and the types the model renames or retires follow it.
Existing content of the changed and removed types no longer matches, and is not
migrated. Recreate it after the steps below, and move the storefront over in
the same upgrade.
- Contentful: apply the content types’ Terraform. Every page has a
slugper locale and aparent, and its path is the parent’s path plus the slug;catalog_page.pathis renamed toslug. Give each page its slug and parent. A page mapper of your own reads its paths withpagePathsOfinstead ofoptions.translatedPaths. An article needs aparentbefore it can be published again. - Payload: on a deployed database, run
payload migrate:create --file @evolve-framework/payload/migrations/drop-removed-schema, thenpayload migrate:create, thenpayload migrate. A database kept in shape by schema push needs a migration generated with the previous release first. Give every page aslugand, where it sits below another page, aparent; an article needs aparent. Rebuild the menus in the newnavigationshape.@payloadcms/richtext-lexicalis now a peer dependency. Runpayload generate:importmap. - Storyblok: apply the new Terraform, then recreate the content in the
new components: menus in
site, teasers aspromo_list, the FAQ with inlinefaq_items, snippets ascontent_snippet, and the settings story assite_settings. The hero and buttons are gone.contentSnippet(key)finds a snippet by itskeyfield instead of its slug.mapSingleBlokis no longer exported.
The content blocks render the vendor-neutral rich text
Section titled “The content blocks render the vendor-neutral rich text”In: feature-cart 1.1.0, feature-content-blocks 1.0.0
Rich text renders from RichText.document only, and no longer selects
RichText.content, which the framework 1.0.0 packages remove. A gateway
without RichText.document fails the whole page query, so upgrade the gateway
first.
- The
./rich-text/storyblokand./rich-text/contentfulentry points are removed, withStoryblokRichTextandContentfulRichText. Drop the registration and use the built-inRichText. Uninstallstoryblok-rich-text-react-rendereror@contentful/rich-text-react-rendererif nothing else uses them. RichTextRendererandrichTextParagraphsare removed, andContentBlocksRichTextTreeFieldsis gone; remove its spread from a page query of your own.- Rich text is no longer styled with the
proseclass. Drop@tailwindcss/typographyrules for it, or restyle with[data-component="rich-text"] …selectors. - The tree does not yet carry superscript and subscript, a link’s anchor and new-tab setting, or Storyblok’s code blocks, inline images and emoji.
Content block fields are selected under aliases
Section titled “Content block fields are selected under aliases”In: feature-content-blocks 1.0.0
The older blocks’ fields are selected under an alias, so a union selection gives same-named fields one shape. A component of your own reads the new name, and a page query of your own uses the same alias, or validation fails with a fields-conflict error.
| Field | Alias |
|---|---|
HeroBlock.title |
heroBlockTitle |
TeaserBlock.title, link |
teaserBlockTitle, teaserBlockLink |
TeasersBlock.title, items |
teasersBlockTitle, teasersBlockItems |
ProductBlock.title |
productBlockTitle |
CatalogBlock.title, items |
catalogBlockTitle, catalogBlockItems |
TwoColumnsBlock.ratio |
twoColumnsBlockRatio |
Video.title |
videoTitle |
ContentTeaser.title, text, image |
contentTeaserTitle, contentTeaserText, contentTeaserImage |
content-model-documents.ts is now messages-documents.ts, and
ContentBlocksTipFields moved to documents.ts.
The page heading is rendered by PageHeading
Section titled “The page heading is rendered by PageHeading”In: feature-content-blocks 1.0.0
A site that renders its own h1 above the content renders
<PageHeading page={page} /> instead. PageHeading’s root is a
<header data-component="page-heading"> and the h1 inside it is
data-component="page-heading-title": move a selector or className meant
for the h1 there. ContentPage requires heading, so data built by hand
sets it.
The USP bar asks for a description and an icon
Section titled “The USP bar asks for a description and an icon”In: layout 1.0.0
LayoutGetSite selects Usp.description and Usp.icon, which a gateway
without them rejects, so take this together with the framework release that
serves them. SiteUsp gains both; a fixture that builds one adds them (null
is fine).
The listing needs quantityRule, and names lists by what they show
Section titled “The listing needs quantityRule, and names lists by what they show”In: analytics 1.0.0, feature-product 1.0.0
The listing documents select ProductVariant.quantityRule, so every listing
query fails against a gateway without it. Upgrade the framework first.
listingName takes { searchTerm, categoryName } and an optional
search(term) formatter, instead of returning “search results” or “product
listing page”. Pass the category name and word the search in the site’s
language, for example
listingName({ searchTerm, categoryName }, { search: (term) => t("search-list", { term }) }).
A cart line shows the SKU by layout
Section titled “A cart line shows the SKU by layout”In: feature-cart 1.1.0
CartLineItem takes a layout, business in a business unit’s cart and
consumer elsewhere. A consumer’s line no longer shows the SKU, and a business
line starts with “Art. {sku}”. New messages: Cart.line.was, article,
split, split-later, next-tier and stock.*.
CartLineItem’s isPending now means only that this line’s removal is in
flight, and renderItem’s isUpdatingQuantity is per line.
An approval’s order can be null in the storefront
Section titled “An approval’s order can be null in the storefront”In: feature-organization 1.0.0
OrderApproval.order is ApprovalOrder | null | undefined. Code of your own
that reads it handles null.
statusBadgeVariants is removed
Section titled “statusBadgeVariants is removed”In: feature-order 1.0.0, ui 1.0.0
The badge colors live in styles.css, keyed on
[data-component="status-badge"][data-tone]. Render a StatusBadge instead
of using the class string. The new tones info and warning read the brand
tokens --color-info and --color-warning.
An icons alias takes effect
Section titled “An icons alias takes effect”In: ui 1.0.0
A site that aliases @evolve-storefront/ui/icons and spreads the base map
imports the base from @evolve-storefront/ui/default-icons. Importing it from
@evolve-storefront/ui/icons makes the aliased file import itself, and the
build fails.
import { icons as base } from "@evolve-storefront/ui/default-icons";
export const icons = { ...base, cart: BrandCart } satisfies Record<IconName, IconComponent>;Returns become requests the seller approves
Section titled “Returns become requests the seller approves”In: feature-return 1.0.0
Returns are built against a proposed return schema that the framework does not serve yet.
ReturnhasreturnNumberinstead ofreference, andReturnResultis{ items, pagination }.ReturnStatusBadgetakesresolution.ReturnRequestFormtakesorderId,lines(fromuseReturnableLines),reasons(fromuseReturnReasons) andpickupAddresses.requireEvidenceis gone: a reason’srequiresPhotosdecides.ReturnItemsPickertakeslines,reasons, andvalue/onValueChange;onChangeis gone.ReturnDetailAttachmentsis gone.ReturnableLinehas a requiredexchangeable; fixtures and mocks need it.- The default
createCapabilityisREQUEST_RETURNSinstead ofreturn:create. TheReturn.reasonmessages are gone, since reason labels come from the server. ReturnStatusgainsIN_TRANSITandReturnShippingMethodgainsDROP_OFF, so an exhaustive map over either needs them.- The package depends on
@evolve-storefront/commerce-ui. Import itsstyles.cssif you do not yet.
createRefreshHandler resolves false on a client error
Section titled “createRefreshHandler resolves false on a client error”In: session 1.0.0
createRefreshHandler resolves false on a 4xx other than 429, where it used
to throw. A network error, 429, 5xx or unparseable answer keeps the
credentials: the auth route answers 503 with Retry-After instead of
redirecting.

