2.4

One preset applied to every integration, so the tolerant settings one flaky vendor needed applied to the stable ones too.

CB_<INTEGRATION>_PRESET sets the preset for one integration, for example CB_SAPCC_PRESET=TOLERANT. Write the integration name in uppercase, with - replaced by _. The per-integration variable wins over CB_PRESET, which wins over circuitBreaker.preset in the integration config. With none of them set, the preset is BALANCED.

An invalid value logs a warning that names the variable and falls back to BALANCED. EXTREME_DEBUG stays blocked in production.

Importing the integration kit loaded two dev-only packages into every application at startup, even when you didn't use mocking.

nock and @mswjs/interceptors load only when you use defineMocker.

Generated scripts used shell-only syntax, such as inline VAR=value prefixes and mkdir -p, so a developer on Windows couldn't start the project without WSL.

Generated package.json scripts set environment variables with cross-env. Shell-only constructs are now small Node scripts, and project generation no longer uses mkdir -p.

Store composition no longer creates broken .bin shims. yarn alokai ai sync repairs skill symlinks that git checked out as text files.

The CMS mini-cart button, the rotating-images pagination dots, and the Compass add-use-case button have translated aria-labels. The mini-cart label includes the item count.

Review ran only as a local command that needed an API key and a set of flags. It raised findings you couldn't always trust, and you applied its fixes by hand.

Review now runs in CI and posts its findings on your pull requests. Each run reviews only the commits pushed since the last review. Pass --full to review the whole pull request.

Each finding quotes the code it's about, and a finding you already replied to isn't raised again. @alokai/ai-toolkit adds the autofix skill, which applies the findings you accept. The review skill is renamed from code-reviewer to alokai-review.

A deployed storefront could crash on its first request with "Cannot find module". Packaging reinstalled a minimal dependency set, so a server-external package hoisted outside the app directory, such as pino, was missing at runtime.

yarn alokai store deploy ships the complete Next.js standalone output, including the traced node_modules. Packaging fails with an actionable error on dangling symlinks. When a registry install is rejected, the error names the package.

When yarn alokai version upgrade crosses a major version, it asks you to confirm before it installs dependencies. When it finishes, it prints the migration guide URL.

When a package fails to install from the registry, for example during yarn alokai store deploy, the error names that package. It no longer reports only a generic "Authorization required".

yarn alokai store lint no longer reports a store as failed when it has no override files, such as a template store or a store that fully inherits an app.

@alokai/cli resolves plugins from https://npm.alokai.cloud directly. The alokai-cli plugins install @alokai/cli-plugin-compass postinstall step no longer needs an @alokai:registry mapping in your user-level ~/.npmrc.

A user-level scope mapping or the ALOKAI_CLI_NPM_REGISTRY variable still takes precedence when you set one.

Installing a CMS module removes the base mock CMS from middleware.config.ts whatever name its import uses.

The generated AGENTS.md links to the theming and perf-review skills instead of repeating their instructions.

The review plugin worked only with GitHub. It rejected any other git remote before the review started, so if you host on GitLab, you couldn't run ai review or ai fix at all:

Git remote host "gitlab.com" is not supported - only GitHub today.

@alokai/cli-plugin-review 0.3.0 supports GitLab as well as GitHub, and detects which one to use from your git remote's host. On a merge request, ai review posts inline findings and a sticky summary comment. ai fix applies fixes from a /fix note and replies in that discussion thread.

--provider takes github or gitlab, and AI_REVIEW_PROVIDER sets it too. --host overrides the host taken from the git remote. --repo accepts a nested project path such as group/subgroup/store, not only owner/name.

The upgrade command and a dependency install don't update the review plugin, because it lives in the CLI's own plugin store, not in package.json. A project keeps the plugin version it installed, whichever release it upgrades to.

2.4.1 ships @alokai/cli-plugin-review 0.3.0. It includes every earlier plugin change, 2.4.0's incremental review among them, and adds this release's GitLab support.

The CLI doesn't read a release number from your project. It works the release out from the installed versions of @alokai/connect, @alokai/cli, @vue-storefront/next, and @vue-storefront/nuxt, and picks the newest release that pins those versions. When two releases pin the same four versions, the CLI reads a project on either one as the newer release.

This release changes no core package. @alokai/connect stays at 2.5.0, @alokai/cli at 2.8.0, @vue-storefront/next at 10.0.0, and @vue-storefront/nuxt at 13.0.0, as in 2.4.0.

The only package with a change of its own is the review plugin, and the CLI doesn't use it to work out your release. Two other packages move with a version bump only.

Since 2.0.0, store deploy ran patch-package against your local node_modules instead of the dependency tree it packages into the image. The deployed middleware shipped your dependencies unpatched, and the command still reported success.

store deploy in @alokai/cli 2.8.1 applies your patches/ directory to the dependency tree each image is built from. A patch whose package isn't in that tree is skipped and named in a warning, and a patch that fails to apply stops the deploy.

Mount ExperimentsProvider with an experiment registry. On page load, each visitor gets one variant per experiment, picked at random by weight. A cookie per experiment keeps that variant the same across reloads.

useExperiments() returns the assigned variants, serialized payloads to attach to analytics events, and an override for development and QA. An onAssignment callback on each experiment sends the assignment to any analytics provider. NEXT_PUBLIC_COMPASS_AB_<EXPERIMENT>_<VARIANT> overrides a split from the environment.

Variants are assigned in the browser only, not during SSR, so CDN caching keeps working.

Installing Compass seeds .env.example with an active ALOKAI_COMPASS_API_URL that points at the Alokai LLM gateway, and an active ALOKAI_COMPASS_NO_CREDENTIALS_MANAGER=true. It also adds a commented-out, empty ALOKAI_COMPASS_API_KEY= for you to fill in.

Before, the install seeded an active dummy API key and a commented-out URL, so Compass used the hosted credentials manager.

Adding products from an uploaded CSV no longer ends with "no products found". The assistant answers price questions on a product page in the product's own currency. It doesn't assume or convert the currency symbol.

In guided selling, the assistant no longer sets a facet to a value that no catalog option matches. It retries with a valid option instead. Guided-selling UI updates also apply reliably while the answer streams.

Clearing the AI assistant session also clears the product, title, and search context the assistant stored in the browser. The product and category pages read that context fresh each time they render.

Installing the Compass module raises the middleware's JSON body limit for the devToolsImport endpoint to 2mb. The default is 100kb.

The dev tools page at /compass/devTools loads its stylesheet, script, and trace data relative to the page URL. Before, it loaded them from the domain root, where they returned 404.

Only the Cancel button clears the search query. Submitting the search form keeps the query, so a results-slot module such as Coveo instant results can still read it.

Chat product results show the search engine's display name from the result's $custom.source field. The search engine behind the unified method sets that field. The badge shows the name as is, and no badge shows when the field is absent.

Absolute image URLs are used as they are. mediaHost is added only in front of relative paths.

After the assistant adds, removes, or updates cart items, or clears the cart, the "Open in Store" button opens /cart.

The widget escapes every HTML tag the search backend might emit except the <em> highlight, so only the highlight renders as styled output.

2.4.2 ships @alokai/cli-plugin-compass 1.1.11. It's rebuilt against this release's CLI internals and behaves exactly like 1.1.10.

Changing how a feature behaves meant a code change and a deploy. The only editor was inside Compass, and many projects never install Compass.

The feature editor is now its own package, @alokai/connect-admin. Install it with yarn alokai add-module connect-admin, and the middleware serves it at /connect-admin. You register features, each grouping form or list-panel views, and read the values back with sdk.connectAdmin.getFormValues().

@alokai/compass no longer has the matching endpoints, defineFeatureEditor, the featureEditors config field, or sdk.compass.getFeatureEditorData.

CONNECT_ADMIN_FEATURE_EDITOR turns on the feature editor. It's separate from COMPASS_DEV_TOOLS, which turns on the dev tools. Local development and tests turn the editor on automatically when NODE_ENV !== "production". A production build turns it on only when you set CONNECT_ADMIN_FEATURE_EDITOR.

The editor requests its stylesheet, script, and API endpoints relative to the page URL, not from the domain root.

Save and Remove on a list-panel row no longer send the whole row to the server. The server looks the row up itself.

The per-row action menu opens above its button when there's no room below it. The list card no longer cuts it off.

The editor compares your draft with the saved version as JSON. After a successful save, the draft takes the value the server sends back.

A new entry in a multi-entry configuration starts from each field's defaultValue, including fields inside nested objects. It no longer starts as a blank row.

Download and Copy export the entries array for a multi-entry form and the settings object for a single-entry form. They no longer export {}.

Products with two or more variant axes came back with an empty variants array.

getProductDetails and getProductCatalogItem read variant options from SAP's variantMatrix when baseOptions is absent. Products with two or more variant axes, such as Size and Color, return their variants.

deleteCart ignored the commercetools Store and always deleted in project scope, while createCart, updateCart and createMyOrderFromCart already worked within the Store.

deleteCart in @vsf-enterprise/commercetools-api 11.0.1 sends the Store key resolved from the vsf-store cookie, or from the store configuration property when the cookie is absent. Without a resolved Store, it deletes in project scope, as before. A custom query that sets storeKey itself still overrides the resolved key.

@vsf-enterprise/bigcommerce-types ships its TypeScript declaration files again.

A version tag can be moved to different code after you adopt it. GitHub recommends pinning third-party actions to a commit SHA.

The workflow templates pin actions/checkout, actions/setup-node, and actions/cache to commit SHAs, which can't change.