Alokai versions

Redeploy each store you've deployed, once @alokai/cli is at 2.8.1. The middleware images you're running were built without your patches, and upgrading the CLI fixes only the next deploy:

./node_modules/.bin/alokai-cli store deploy

This one redeploy also covers the redeploy 1.3.2 asked for, so you don't need both.

Read the deploy output for a warning ending in - the patched package is not part of this dependency tree.. It names each patch the deploy skipped because the image doesn't contain the patched package. That's expected for a patched devDependency.

If the deploy stops because a patch fails to apply, update the patch so it applies to the version of the package your lockfile resolves, then deploy again. Before this release, the same failure passed silently and left the package unpatched.

To apply patches with a pinned tool rather than whatever npx resolves that day, declare patch-package in your root devDependencies. store deploy runs the version you declare.

Check which version of @alokai/cli-plugin-compass you have. The upgrade command doesn't move it, and it lives in the CLI's own plugin store, so grepping node_modules or yarn.lock shows nothing:

./node_modules/.bin/alokai-cli plugins

If it isn't listed, you have nothing to do. Above 1.1.11, leave it - the install below would downgrade it. Otherwise, install 1.1.11:

./node_modules/.bin/alokai-cli plugins install @alokai/cli-plugin-compass@1.1.11

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

Find your deleteCart calls. Keep the ones that reach the commercetools integration, through its SDK module or context.api in a middleware extension - other integrations use the same method name:

grep -rln 'deleteCart' apps --include='*.ts' --include='*.tsx' --include='*.vue' --exclude-dir=node_modules --exclude-dir=.out || true

For each call, make sure the Store resolved when it runs is the Store the cart was created in. deleteCart now deletes within that Store, so with a different Store resolved, commercetools doesn't find the cart and the call fails instead of deleting it.

Where the call can't run with the cart's Store resolved, set the Store key in a custom query. A key you set there overrides the resolved one:

export const integrations = {
  ct: {
    // ...
    customQueries: {
      'delete-cart-custom-query': ({ variables, metadata }) => {
        variables.storeKey = metadata.storeKey;

        return {
          variables,
          query: `
            mutation deleteCart($id: String!, $version: Long!, $storeKey: KeyReferenceInput) {
              cart: deleteMyCart(id: $id, version: $version, storeKey: $storeKey) {
                ${metadata.fields}
              }
            }
          `,
        };
      },
    },
  },
};

Then pass the cart's Store key with the call:

await sdk.commerce.deleteCart({ id, version }, {
  deleteCart: 'delete-cart-custom-query',
  metadata: { storeKey: 'store-fr', fields: 'id,version' },
});