Skip to content

Commit

Permalink
Adjusing the files
Browse files Browse the repository at this point in the history
  • Loading branch information
lenadoc committed Oct 11, 2023
1 parent 9eaa1d4 commit 1ff9931
Show file tree
Hide file tree
Showing 3 changed files with 14 additions and 13 deletions.
18 changes: 8 additions & 10 deletions _includes/pbc/all/upgrade-modules/upgrade-the-chart-module.md
Original file line number Diff line number Diff line change
@@ -1,24 +1,22 @@
## Upgrading from version 1.4.0 to version 1.5.0

In version 1.5.0 of the Chart module, we've updated the `plotly.js` dependency from version 1.54.5 to 2.26.0. For more details about the changes, see the [Chart module release page](https://github.com/spryker/chart/releases).

## Upgrading from version 1.4.0 to 1.5.0

In the version `1.5.0` of the `Chart` module, we have updated `plotly.js` dependency from version `1.54.5` to `2.26.0`.
We need to upgrade to the latest major to get the latest improvements, as well as performance in runtime and tooling.
You can find more details about the changes on the [Chart module release](https://github.com/spryker/chart/releases) page.
Upgrade to the latest major version to incorporate the latest improvements and optimize both runtime and processing performance.


*Estimated migration time: 15 min*

To upgrade to the new version of the module, do the following:

1. Upgrade the `Chart` module to the new version:
1. Upgrade the Chart module to the new version:

```bash
composer update spryker/chart:"^1.5.0" --update-with-dependencies
```

2. `1.5.0` module version requires update `@spryker/oryx-for-zed` dependency to the `3.1`+ version and `webpack` dependency to the `5.88`+ version at the project level.
In the root `package.json` file, update dependencies to the following versions or higher:
2. The 1.5.0 module version requires an update of the `@spryker/oryx-for-zed` dependency to version 3.1 or later, as well as an update of the `webpack` dependency to version 5.88 or later at the project level.
To perform the updates, in the root `package.json` file, update the dependencies to the following versions or newer:

```json
{
Expand All @@ -27,14 +25,14 @@ In the root `package.json` file, update dependencies to the following versions o
}
```

3. Run and build the Backoffice frontend:
3. Run and build the Back Office frontend:

```bash
docker/sdk cli npm install
docker/sdk up --assets
```

Or
or

```bash
npm install && npm run zed
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -3,5 +3,6 @@ title: Upgrade the Chart module
description: Use the guide to learn how to update the Chart module to a newer version.
last_updated: Sep 18, 2023
template: module-migration-guide-template
---

{% include pbc/all/upgrade-modules/upgrade-the-chart-module.md %} <!-- To edit, see /_includes/pbc/all/upgrade-modules/upgrade-the-chart-module.md -->
8 changes: 5 additions & 3 deletions docs/scos/dev/migration-concepts/upgrade-to-angular-15.md
Original file line number Diff line number Diff line change
Expand Up @@ -15,9 +15,11 @@ Our current version of Angular is v12 with v9 compatibility.
Angular v12 was deprecated on 2022-11-12, according to the [policy](https://angular.io/guide/releases#support-policy-and-schedule).
The current stable version of Angular is v15.

We need to upgrade to the latest major to get the latest bug fixes and security fixes, as well as performance in runtime and tooling.
We can't maintain compatibility with older versions of Angular when updating Angular v15.
So the update requires a major release for these modules:

Upgrade to the latest major version of Angular to get the most recent bug fixes and security updates. Additionally, this will lead to optimization in both runtime performance and tooling.

Keep in mind that updating to Angular v15 results in incompatibility with older versions of Angular. Therefore, a major release is necessary for these modules:

- `ZedUi`
- `DashboardMerchantPortalGui`
- `GuiTable`
Expand Down

0 comments on commit 1ff9931

Please sign in to comment.