Alokai

Alokai versions

Showing every integration. Set your stack in Preferences and this page hides what isn't yours.

The legacy version refers to all releases prior to the introduction of the new versioning model (before version v0).

You can upgrade your Alokai project to the next compatible version by running yarn alokai version upgrade.

Looking for what changed in a package before Alokai ecosystem 1.0.0? The per-package history is archived in the legacy package changelogs.

Pick where the project is and where it is going. The table shows every package version in between for your stack, and the upgrade guide beneath it lists every step in that range.

Dependencies (54)
2.5.62.6.0
@alokai/connect2.5.22.5.2
@alokai/cli(upgrade required)2.9.12.10.0
@alokai/cli-plugin-review(upgrade required)0.3.10.3.2
@alokai/compass7.1.27.1.2
@alokai/cli-plugin-compass(upgrade required)1.2.21.2.3
@vue-storefront/nuxt(upgrade required)13.0.213.0.3
@vue-storefront/next10.1.210.1.2
@vsf-enterprise/sapcc-api14.1.114.1.1
@vsf-enterprise/unified-api-sapcc10.0.110.0.1
@vsf-enterprise/sapcc-types4.2.04.2.0
@vsf-enterprise/sapcc-sdk10.0.210.0.2
@vsf-enterprise/commercetools-api(upgrade required)11.0.311.1.0
@vsf-enterprise/unified-api-commercetools(upgrade required)8.0.39.0.0
@vsf-enterprise/commercetools-types3.0.53.0.5
@vsf-enterprise/commercetools-sdk9.0.29.0.2
@vsf-enterprise/sfcc-api3.1.03.1.0
@vsf-enterprise/unified-api-sfcc8.0.28.0.2
@vsf-enterprise/bigcommerce-api12.0.212.0.2
@vsf-enterprise/unified-api-bigcommerce8.0.28.0.2
@vsf-enterprise/magento-api12.0.312.0.3
@vsf-enterprise/unified-api-magento9.0.39.0.3
@vsf-enterprise/magento-types4.0.74.0.7
@vsf-enterprise/amplience-api10.0.210.0.2
@vsf-enterprise/amplience-sdk8.0.28.0.2
@vsf-enterprise/bloomreach-content-api7.0.27.0.2
@vsf-enterprise/bloomreach-content-manager6.0.26.0.2
@vsf-enterprise/bloomreach-content-sdk9.0.29.0.2
@vsf-enterprise/builderio-api8.0.28.0.2
@vsf-enterprise/builderio-sdk8.0.28.0.2
@vsf-enterprise/contentful-api10.0.210.0.2
@vsf-enterprise/contentful-sdk10.0.210.0.2
@vsf-enterprise/contentstack-api10.0.310.0.3
@vsf-enterprise/contentstack-sdk10.0.210.0.2
@vsf-enterprise/smartedit-api10.0.110.0.1
@vsf-enterprise/smartedit-sdk6.1.16.1.1
@vsf-enterprise/storyblok-api7.0.27.0.2
@vsf-enterprise/storyblok-sdk6.0.26.0.2
@vsf-enterprise/cms-components-utils3.2.23.2.2
@vsf-enterprise/cms-mock-api7.0.27.0.2
@vsf-enterprise/coveo-api7.0.27.0.2
@vsf-enterprise/algolia-api10.0.210.0.2
@vsf-enterprise/storefront-cli(upgrade required)3.3.83.4.0
@vue-storefront/eslint-config5.1.45.1.4
@vsf-enterprise/redis-sdk6.0.26.0.2
@vue-storefront/middleware5.4.15.4.1
@vsf-enterprise/middleware-headers7.0.27.0.2
@alokai/middleware-axios-error-adapter4.0.24.0.2
@alokai/middleware-fetch-error-adapter4.0.24.0.2
@vue-storefront/multistoreN/AN/A
@vue-storefront/unified-data-modelN/AN/A
@alokai/ai-toolkit(upgrade required)1.2.01.2.1
@alokai/cookies-bridge1.0.41.0.4
@vue-storefront/magento-apiN/AN/A
Node(upgrade required)v22.23.4v24.22.3

Upgrade guide

2.5.6 → 2.6.0· covers2.6.0·5 steps

1Apply the versions from the tableAll projects

Applies to: All projects · Only if: always

Run the upgrade command first; it moves the core packages to the target column. Then set every remaining highlighted row to its target version in `package.json` and reinstall. The table above is already filtered to your stack, so every row in it is yours to move; nothing else in the release asks for a version change.

Command
yarn alokai version upgrade
# then bump the remaining rows in package.json and run yarn install
2Move your project to Node.js 242.6.0All projects

Applies to: All projects · Only if: you are moving the project to Node.js 24

Apply this together with the upgrade, not before it. An @alokai/cli version older than 2.10.0 fails on Node.js 24 with TypeError: Cannot read properties of undefined (reading 'replace') when it composes a store (store build, store dev).

Set the version in .nvmrc:

# .nvmrc
-v22.23.4
+v24.22.3

Update every other place that pins Node.js. List the workflow files that set a version explicitly:

find .github -type f \( -name '*.yml' -o -name '*.yaml' \) -exec grep -ln 'node-version:' {} + || true

Change each hit to node-version-file: ".nvmrc" or to a Node.js 24 version. Update the base image of any container you build yourself to node:24-alpine. Stores you deploy with store deploy already switch to Node.js 24 on their next deployment.

Then move the Node.js type definitions to match. List the manifests that declare them:

find apps -maxdepth 6 -type f -name package.json -not -path '*/node_modules/*' -exec grep -lF '"@types/node"' {} + || true

In each one, replace the range with ^24.19.2. Run yarn install. If a composed .out directory exists, also run yarn store build --all --compose-only and yarn install again.

3Install the Node.js 24 builds of the CLI plugins you use2.6.0All projects

Applies to: All projects · Only if: you run Node.js 24 and the CLI lists @alokai/cli-plugin-review below 0.3.2 or @alokai/cli-plugin-compass below 1.2.3

Check which plugins you have and at which version. Grepping node_modules or yarn.lock shows nothing:

yarn alokai plugins

A plugin that isn't listed isn't yours, so skip it. A plugin already at its target version or above stays as it is, because the install below would downgrade a newer one. For each plugin below its target, install the target:

yarn alokai plugins install @alokai/cli-plugin-review@0.3.2
yarn alokai plugins install @alokai/cli-plugin-compass@1.2.3

If you adopted the Compass module, check the postinstall script in your root package.json. The installer appends an unpinned plugins install @alokai/cli-plugin-compass to it. That line reinstalls the newest plugin on every yarn install and undoes your pin.

4Pin the commercetools API and Unified API packages together2.6.0commercetools

Applies to: commercetools · Only if: a package.json under apps declares @vsf-enterprise/commercetools-api or @vsf-enterprise/unified-api-commercetools

Set both packages in every manifest that declares either. List them:

find apps -maxdepth 6 -type f -name package.json -not -path '*/node_modules/*' -exec grep -lE '"@vsf-enterprise/(commercetools-api|unified-api-commercetools)"' {} + || true

In each one, replace the range with exactly the version below, without a caret:

-    "@vsf-enterprise/commercetools-api": "11.0.3",
+    "@vsf-enterprise/commercetools-api": "11.1.0",
-    "@vsf-enterprise/unified-api-commercetools": "8.0.3",
+    "@vsf-enterprise/unified-api-commercetools": "9.0.0",

Then run yarn install. If a composed .out directory exists, run yarn store build --all --compose-only and yarn install again.

A manifest that lists only one of the two still needs the other at the matching version.

Steps carry the release that introduced them. When a later release supersedes an earlier step, the guide shows only the final state. Each step's release note is one click away: Alokai 2.6.