Merge branch 'master' into feature/cc-26550-service-types-integration

spryker · Jun 8, 2023 · 8dedbcc · 8dedbcc
2 parents 50da329 + 6960409
commit 8dedbcc
Show file tree

Hide file tree

Showing 4 changed files with 21 additions and 11 deletions.
diff --git a/_data/sidebars/scos_dev_sidebar.yml b/_data/sidebars/scos_dev_sidebar.yml
@@ -3900,6 +3900,10 @@ entries:
       url: /docs/scos/dev/front-end-development/migration-guide-upgrade-to-webpack-v5.html
     - title: Migration guide - Switch from TSLint to ESLint
       url: /docs/scos/dev/front-end-development/migration-guide-switch-from-tslint-to-eslint.html
+    - title: Migration guide - Upgrade Node.js to v18 and npm to v9
+      url: /docs/scos/dev/front-end-development/migration-guide-upgrade-nodejs-to-v18-and-npm-to-v9.html
+      include_versions:
+      - "202212.0"
   - title: Migration concepts
     url: /docs/scos/dev/migration-concepts/migration-concepts.html
     nested:

diff --git a/...ud/dev/spryker-cloud-commerce-os/multi-store-setups/multistore-setup-options.md b/...ud/dev/spryker-cloud-commerce-os/multi-store-setups/multistore-setup-options.md
@@ -82,7 +82,7 @@ The following table provides details on infrastructure for this setup:
 | What | How |
 |------|-----|
 | DB     | Shared    |
-| Key-value storage (Redis) and Search (OpenSearch/ElasticCache) services     | Shared    |
+| Key-value storage (Redis) and Elasticsearch (OpenSearch/ElasticCache) services     | Shared    |
 | Spryker Storefront Yves     |Shared     |
 | Spryker Commerce OS (Backend Gateway Zed + Glue Backend API + Back Office)     | Shared   |
 | Complexity of rollout     | Low   |
@@ -119,7 +119,7 @@ The following table provides details on the infrastructure for this setup:
 | What | How |
 |------|-----|
 | DB     | Separate    |
-| Key-value storage (Redis) and search (OpenSearch/ElasticCache) services     | Shared    |
+| Key-value storage (Redis) and Elasticsearch (OpenSearch/ElasticCache) services     | Shared    |
 | Spryker Storefront Yves     |Shared     |
 | Spryker Commerce OS (Backend Gateway Zed + Glue Backend API + Back Office)     | Shared   |
 | Complexity of rollout     | Medium   |
@@ -138,7 +138,7 @@ You can apply the virtually isolated database to setup one and setup three too.
 This setup has the following characteristics:
 
 - Multiple stores. 
-- Each store has dedicated search and key-value storage services. 
+- Each store has dedicated key-value storage (Redis) and Elasticsearch (OpenSearch/ElasticCache) services. 
 - Separate database per account.
 - Allows for different regions.
 - Lets you use themes for a different visual look and feel.
@@ -173,7 +173,7 @@ The following table provides details on the infrastructure for this setup:
 | What | How |
 |------|-----|
 | DB     | Separate    |
-| Key-value storage (Redis) and search (OpenSearch/ElasticCache) services     | Separate    |
+| Key-value storage (Redis) and Elasticsearch (OpenSearch/ElasticCache) services     | Separate    |
 | Spryker Storefront Yves     |Separate     |
 | Spryker Commerce OS (Backend Gateway Zed + Glue Backend API + Back Office)     | Separate   |
 | Complexity of rollout     | High   |
@@ -189,7 +189,7 @@ The following tables contain high-level criteria that sum up the setups describe
 | What                                                                   | Setup 1 | Setup 2  | Setup 2  |
 |------------------------------------------------------------------------|---------|----------|----------|
 | DB                                                                     | Shared  | Separate | Separate |
-| Ke-value storage (Redis) and search (OpenSearch/ElasticCache) services | Shared  | Shared   | Separate |
+| Ke-value storage (Redis) and Elasticsearch (OpenSearch/ElasticCache) services | Shared  | Shared   | Separate |
 | Spryker Storefront Yves                                                | Shared  | Shared   | Separate |
 | Spryker Commerce OS                                                    | Shared  | Shared   | Separate |
 | Complexity of rollout                                                  | Low     | Medium   | High     |

diff --git a/...de-upgrade-nodejs-to-v18-and-npm-to-v9.md → ...de-upgrade-nodejs-to-v18-and-npm-to-v9.md b/...de-upgrade-nodejs-to-v18-and-npm-to-v9.md → ...de-upgrade-nodejs-to-v18-and-npm-to-v9.md
@@ -3,6 +3,8 @@ title: Migration guide - Upgrade Node.js to v18 and npm to v9
 last_updated: May 16, 2023
 description: Use this guide to upgrade Node.js to v18 and npm to v9.
 template: concept-topic-template
+redirect_from:
+  - /docs/scos/dev/front-end-development/202304.0/migration-guide-upgrade-nodejs-to-v18-and-npm-to-v9.html
 ---
 
 This document provides instructions for upgrading Node.js to v18 and npm to v9.
@@ -37,7 +39,7 @@ To ensure the CI jobs run successfully, add the same config part to all `deploy.
 18.16.0
 ```
 
-3. In the `package.json`, update or add dependencies and engines:
+3. In `package.json`, update or add dependencies and engines:
 
 ```json
 {
@@ -61,7 +63,7 @@ To ensure the CI jobs run successfully, add the same config part to all `deploy.
 }
 ```
 
-4. In the `package.json`, remove the dependency :
+4. In `package.json`, remove the dependency:
 
 ```json
     "@spryker/sass-resources-loader": "x.x.x"
@@ -110,7 +112,7 @@ docker/sdk cli npm install
 
 {% info_block infoBox "Note" %}
 
-Ensure that the `package-lock.json` file has `"lockfileVersion": 2` or later; otherwise, remove `node_modules` and `package-lock.json` and regenerate the file again.
+Ensure that the `package-lock.json` file has `"lockfileVersion": 2` or later; otherwise, remove `node_modules` and `package-lock.json` and regenerate the file again:
 
 ```bash
 rm -rf node_modules && docker/sdk cli rm -rf node_modules && rm -rf package-lock.json

diff --git a/...onboard-to-spryker-code-upgrader/prepare-a-project-for-spryker-code-upgrader.md b/...onboard-to-spryker-code-upgrader/prepare-a-project-for-spryker-code-upgrader.md
@@ -36,11 +36,15 @@ To ensure the successful delivery of Spryker updates, we recommend using the ext
 
 ## Migrate to Spryker Cloud Commerce OS
 
-The upgrader supports only the projects that run on [Spryker Cloud Commerce OS (SCCOS)](/docs/cloud/dev/spryker-cloud-commerce-os/getting-started-with-the-spryker-cloud-commerce-os.html). If you are running Spryker on premises, migrate to SCCOS.
+The Upgrader supports only projects that run on [Spryker Cloud Commerce OS (SCCOS)](/docs/cloud/dev/spryker-cloud-commerce-os/getting-started-with-the-spryker-cloud-commerce-os.html). If you are running Spryker on premises, migrate to SCCOS.
 
-## Update PHP to version 7.4 or higher
+## Minimum technical requirements
 
-The Upgrader still supports PHP 7.4 to help you upgrade your project. However, make sure to update PHP to the recommended version based on [Supported versions of PHP](/docs/scos/user/intro-to-spryker/whats-new/supported-versions-of-php.html).
+To ensure a smooth experience, please make sure that your environments meet the minimum technical requirements outlined below:
+
+* PHP 7.4+. The Upgrader still supports PHP 7.4 to help you upgrade your project. However, make sure to update PHP to the recommended version based on [Supported versions of PHP](/docs/scos/user/intro-to-spryker/whats-new/supported-versions-of-php.html).
+* Composer 2.1+
+* Git 2.24+
 
 ## Optional: Implement headless design