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.1
2.5.2
@alokai/connect
2.5.2
2.5.2
@alokai/cli
2.9.1
2.9.1
@alokai/cli-plugin-review
0.3.1
0.3.1
@alokai/compass
7.1.1
7.1.1
@alokai/cli-plugin-compass
1.2.1
1.2.1
@vue-storefront/nuxt
13.0.2
13.0.2
@vue-storefront/next
10.1.1
10.1.1
@vsf-enterprise/sapcc-api
14.1.1
14.1.1
@vsf-enterprise/unified-api-sapcc
10.0.1
10.0.1
@vsf-enterprise/sapcc-types
4.2.0
4.2.0
@vsf-enterprise/sapcc-sdk
10.0.2
10.0.2
@vsf-enterprise/commercetools-api
11.0.3
11.0.3
@vsf-enterprise/unified-api-commercetools
8.0.3
8.0.3
@vsf-enterprise/commercetools-types
3.0.5
3.0.5
@vsf-enterprise/commercetools-sdk
9.0.2
9.0.2
@vsf-enterprise/sfcc-api
3.1.0
3.1.0
@vsf-enterprise/unified-api-sfcc
8.0.2
8.0.2
@vsf-enterprise/bigcommerce-api
12.0.2
12.0.2
@vsf-enterprise/unified-api-bigcommerce
8.0.2
8.0.2
@vsf-enterprise/magento-api
12.0.2
12.0.2
@vsf-enterprise/unified-api-magento
9.0.2
9.0.2
@vsf-enterprise/magento-types
4.0.6
4.0.6
@vsf-enterprise/amplience-api
10.0.2
10.0.2
@vsf-enterprise/amplience-sdk
8.0.2
8.0.2
@vsf-enterprise/bloomreach-content-api
7.0.2
7.0.2
@vsf-enterprise/bloomreach-content-manager
6.0.2
6.0.2
@vsf-enterprise/bloomreach-content-sdk
9.0.2
9.0.2
@vsf-enterprise/builderio-api
8.0.2
8.0.2
@vsf-enterprise/builderio-sdk
8.0.2
8.0.2
@vsf-enterprise/contentful-api
10.0.2
10.0.2
@vsf-enterprise/contentful-sdk
10.0.2
10.0.2
@vsf-enterprise/contentstack-api
10.0.2
10.0.2
@vsf-enterprise/contentstack-sdk
10.0.2
10.0.2
@vsf-enterprise/smartedit-api
10.0.1
10.0.1
@vsf-enterprise/smartedit-sdk
6.1.1
6.1.1
@vsf-enterprise/storyblok-api
7.0.2
7.0.2
@vsf-enterprise/storyblok-sdk
6.0.2
6.0.2
@vsf-enterprise/cms-components-utils
3.2.2
3.2.2
@vsf-enterprise/cms-mock-api
7.0.2
7.0.2
@vsf-enterprise/coveo-api
7.0.2
7.0.2
@vsf-enterprise/algolia-api
10.0.2
10.0.2
@vsf-enterprise/storefront-cli
3.3.8
3.3.8
@vue-storefront/eslint-config
5.1.4
5.1.4
@vsf-enterprise/redis-sdk
6.0.2
6.0.2
@vue-storefront/middleware
5.4.1
5.4.1
@vsf-enterprise/middleware-headers
7.0.2
7.0.2
@alokai/middleware-axios-error-adapter
4.0.2
4.0.2
@alokai/middleware-fetch-error-adapter
4.0.2
4.0.2
@vue-storefront/multistore
N/A
N/A
@vue-storefront/unified-data-model
N/A
N/A
@alokai/ai-toolkit
1.2.0
1.2.0
@alokai/cookies-bridge
1.0.4
1.0.4
@vue-storefront/magento-api
N/A
N/A
Node
v22.23.4
v22.23.4
Upgrade guide
2.5.1 → 2.5.2· covers2.5.2·1 step
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
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.5.
