Skip to content

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.

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 orderLinkSecret on the framework’s PaymentModule, the same secret as on OrderModule. The gateway then appends returnToken to every payment return URL. This needs a framework that serves sessionOrder and PaymentTargetInput.token.
  • Stop using orderByPublicId in your own documents. The persisted documents change: OrderConfirmationById, OrderLookupByPublicId and OrderPaymentMethodsByPublicId are gone, and OrderConfirmationBySignedLink, OrderConfirmationBySession, OrderLookupBySession and OrderPaymentMethodsBySession are new. Register them again where documents are persisted.
  • Hand the returnToken on from the return route. resolvePaymentReturn calls the lookup as lookupOrder(id, returnToken) and puts returnToken on the order, confirmation and resume destinations.
  • Pass it to the confirmation: readOrderConfirmation(gqlClient, id, returnToken), orderConfirmationQueryOptions({ …, returnToken }) or useAwaitedOrderConfirmation(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 }).
  • readOrderPaymentMethods takes { 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?: string is now defaultRoleIds?: string[]. Pass associate.roles.map((role) => role.id).
  • onValidSubmit receives { roleIds: string[] } instead of { roleId: string }. Pass roleIds to useUpdateAssociateRoles as is.
  • EditRolesFormContextValue has defaultRoleIds and roleError in place of defaultRoleId.
  • The messages Organization.form.role-label, role-placeholder and roleId-error are removed; the fields read roles-label and roleIds-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_ENABLED gets the renewed tokens back on the response as X-Access-Token, X-Refresh-Token and X-Data-Token, and has to store them.
  • The package is built on @modelcontextprotocol/server instead of @modelcontextprotocol/sdk.
  • setSessionStoreContext holds for the rest of a request over HTTP, and no longer for later requests.
  • shutdownHttpServer is removed, along with recordSessionCreated, recordSessionClosed and the metrics mcp.sessions.active, mcp.sessions.created and mcp.sessions.closed.
  • Rate limiting no longer keys on a session. With OAuth it keys on the connected client, with RATE_LIMIT_ADDRESS_MAX for requests without a valid token, and otherwise on the IP address. Behind a proxy, set trustProxy on the application.

To upgrade:

  1. Replace @modelcontextprotocol/sdk with McpServer from @evolve-framework/mcp-core, or build the server with createMcpServerFactory.
  2. Remove calls to shutdownHttpServer and to the session metrics.
  3. Send store and token headers on every request, not only on initialize. A proxy with PROXY_AUTH_ENABLED forwards the customer’s tokens each time, and stores the tokens a response returns in place of those it sent. Keep them server-side.
  4. 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.
  5. Keep state a tool needs in a tool argument or the gateway, not in getSessionContext between requests.
  6. To keep carts and let customers sign in, set MCP_OAUTH_SECRETS, MCP_INTERACTION_SECRET, MCP_PUBLIC_URL and MCP_LOGIN_URL, and pass oauth to createMcpModule.

In: mcp-core 2.0.0

  • createHealthcheckHandler is removed. Compose a HealthModule instead.
  • registerMcpRoutes no longer serves /healthcheck, and its healthcheck option is gone. Compose a HealthModule next to it.
  • createMcpModule takes health: false in place of healthcheck: false.
  • The /healthcheck body 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-separated STOREFRONT_ORIGINS, and pass it to PaymentModule and to every AdyenPaymentAdapter, PaynlPaymentAdapter, StripePaymentAdapter and BuckarooPaymentAdapter. 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 localhost for 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 });

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.createTransaction refuses a payment the cart, order or invoice does not hold, and charges the payment’s amountPlanned instead 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. /rebuild refuses a concurrency outside 1 to maxConcurrency, 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:

  1. Turn on authentication on the push subscription: a service account to sign as, and an audience (by default the push endpoint’s URL).

  2. 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,
    },
    });
  3. Only where something in front of the route already authenticates, such as Cloud Run’s IAM check, set allowUnauthenticated: true instead.

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 as prd_product_nl_price_asc, without the store. Two stores in one Algolia application must both pass resolveIndexName: storeIndexName, or they overwrite each other’s records.
  • objectID is the product key, or the id for a product without one. categoryIds holds readable category paths (clothing > men) and categoryPageId is gone. startingPrice and a variant’s price are the lowest gross price per currency in major units, { "EUR": 19.95 }; facet on startingPrice.EUR. description is no longer written.
  • toAlgoliaRecord takes the scope as its second argument, and toProductDocument throws for a record without _doc. StoredAlgoliaProductRecord, AlgoliaProductPrice and AlgoliaAttributeValue are removed.
  • A ProductSearchQuery with a categoryId must carry its categoryKeys. The commercetools DocumentSearchProvider fills them in.
  • A full reindex applies the settings in code (productIndexSettings). Facets, synonyms and rules set in the dashboard are kept.

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:

  1. Add @payloadcms/plugin-multi-tenant to your dependencies, unless the config had multiTenant: false.
  2. Set blocks: payloadBlocks(blocks), and pass the same list to the collections that take one and to PayloadModule.
  3. List the collections: usersCollection(true), tenantsCollection, contentPageCollection(blocks), catalogPageCollection(blocks), articlePageCollection(blocks), articleOverviewPageCollection(blocks), topicCollection, authorCollection, contentSnippetCollection(blocks), mediaCollection(media), navigationCollection, redirectCollection, siteCollection, siteSettingsCollection and messagesCollection.
  4. Move the options: keyPatterns to configureKeyPatterns(keyPatterns), markets to configureMarkets(markets), contentEvents to the contentEvents(options) plugin, and catalog to the catalogPickers(catalog) plugin. For users: false, multiTenant: false or collections: false, leave out what they turned off.
  5. End plugins with adminLayout() and then multiTenantPlugin({ userHasAccessToAllTenants, collections: tenantScopedCollections }).
  6. Run payload migrate:create. A config that composes what evolveCms() 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 RecurringOrderForm as recurrencePolicies, from useRecurrencePolicies(). sourceOptions takes carts and shopping lists only. The form only creates: recurringOrder, addresses, minOrderDate and onCancel are gone. onValidSubmit hands over { cartId | shoppingListId, recurrencePolicyKey, validFrom?, validUntil? }, and error takes the mutation’s Error.
  • RecurringOrderDetail: onPlaceNow/isPlacingNow become onOrderNow/isRequestingOrderNow, with hasRequestedOrderNow for the notice, and onEnd/isEnding become onCancel/isCanceling.
  • RecurringOrderStatusBadge and RecurringOrderDetailActions take state instead of status: ACTIVE, PAUSED, FAILED, EXPIRED or CANCELED.
  • Query options and cache keys take scope (the business unit’s id, or "customer") instead of businessUnitId, and so does invalidateRecurringOrders. useRecurringOrders no longer takes status.
  • Messages: RecurringOrder.status is RecurringOrder.state, and the detail and form keys follow the new views. Copy your overrides again from messages/en.json.
  • Removed: useUpdateRecurringOrder, useSkipRecurringOrder, useSetOccurrencePurchaseOrderNumber, usePlaceRecurringOrderNow (use useRequestRecurringOrderNow) and useEndRecurringOrder (use useCancelRecurringOrder), their documents, and the components RecurringOrderUpcoming, RecurringOrderOccurrenceReference, RecurringOrderHistory, RecurringOrderDetailEnd and RecurringOrderDetailSettings. 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-desc replica ranked on desc(rating), then reindex.
  • Meilisearch: reindex.
  • In the storefront, change the default sort you pass to readFilterState from "POPULARITY" to "RELEVANCE", and the same for a defaultSort on ProductListing or ProductListingSort. A site that composes ProductListingSort itself passes options={listing.sortOrders}.
  • KnownProductSortOrder loses the name sorts. Drop overrides of the ProductListing.sort.NAME_ASCENDING and NAME_DESCENDING messages, add RELEVANCE if you override the sort labels, and check that your POPULARITY label reads as rating.

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, reverseChargeLine and exportLine in the applyVatRules options with legacyLineSlugs, listing the old lines’ slugs (such as ["vat-shifting", "vat-exemption"]).
  • vatShifting and vatExemption on Cart, Order, Quote and QuoteRequest are deprecated and null on a new cart. Read vatOutcome and the taxed totals instead, also in end-to-end tests.
  • In the storefront, Cart, PlacedOrder, Order, Quote, QuoteRequest and QuoteListEntry no longer have vatShifting and vatExemption; read vatOutcome.treatment. quoteNetTotal takes only total. 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 Columns with that one entry, and rich text there as a RichText of its own. Select ... on RichText in your body blocks.
  • @evolve-framework/schemas no longer exports the schemas of the removed types, nor markPageHeading. 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 slug per locale and a parent, and its path is the parent’s path plus the slug; catalog_page.path is renamed to slug. Give each page its slug and parent. A page mapper of your own reads its paths with pagePathsOf instead of options.translatedPaths. An article needs a parent before it can be published again.
  • Payload: on a deployed database, run payload migrate:create --file @evolve-framework/payload/migrations/drop-removed-schema, then payload migrate:create, then payload migrate. A database kept in shape by schema push needs a migration generated with the previous release first. Give every page a slug and, where it sits below another page, a parent; an article needs a parent. Rebuild the menus in the new navigation shape. @payloadcms/richtext-lexical is now a peer dependency. Run payload generate:importmap.
  • Storyblok: apply the new Terraform, then recreate the content in the new components: menus in site, teasers as promo_list, the FAQ with inline faq_items, snippets as content_snippet, and the settings story as site_settings. The hero and buttons are gone. contentSnippet(key) finds a snippet by its key field instead of its slug. mapSingleBlok is 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/storyblok and ./rich-text/contentful entry points are removed, with StoryblokRichText and ContentfulRichText. Drop the registration and use the built-in RichText. Uninstall storyblok-rich-text-react-renderer or @contentful/rich-text-react-renderer if nothing else uses them.
  • RichTextRenderer and richTextParagraphs are removed, and ContentBlocksRichTextTreeFields is gone; remove its spread from a page query of your own.
  • Rich text is no longer styled with the prose class. Drop @tailwindcss/typography rules 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 }) }).

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.

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.

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.

  • Return has returnNumber instead of reference, and ReturnResult is { items, pagination }. ReturnStatusBadge takes resolution.
  • ReturnRequestForm takes orderId, lines (from useReturnableLines), reasons (from useReturnReasons) and pickupAddresses. requireEvidence is gone: a reason’s requiresPhotos decides.
  • ReturnItemsPicker takes lines, reasons, and value/onValueChange; onChange is gone. ReturnDetailAttachments is gone.
  • ReturnableLine has a required exchangeable; fixtures and mocks need it.
  • The default createCapability is REQUEST_RETURNS instead of return:create. The Return.reason messages are gone, since reason labels come from the server.
  • ReturnStatus gains IN_TRANSIT and ReturnShippingMethod gains DROP_OFF, so an exhaustive map over either needs them.
  • The package depends on @evolve-storefront/commerce-ui. Import its styles.css if 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.