Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

How the Spryker Code Upgrader works #2111

Merged
Prev Previous commit
Next Next commit
Apply suggestions from code review
  • Loading branch information
Vadym Sachenko authored Aug 22, 2023
commit eed4c7e46adb7df17c3fe29b42a9d670911f4cd6
4 changes: 2 additions & 2 deletions docs/scu/dev/how-the-spryker-code-upgrader-works.md
Original file line number Diff line number Diff line change
Expand Up @@ -40,12 +40,12 @@ Please follow the link below to find all documentation needed to help you upgrad
https://api.release.spryker.com/release-group/XXXX
```

To continue running the Upgrader tool, install the major version manually, and re-run the Upgrader tool.
To continue running the Upgrader tool, install the major version manually, and rerun the Upgrader tool.

{% info_block infoBox "Composer dependency conflict" %}

Spryker Code Upgrader uses the [composer](https://getcomposer.org/) for updating modules and libraries.
If the composer detects a conflict, it stops the update process and generates an error message. To resolve the conflict, you must manually update the conflicting module and then re-run the Upgrader pipeline.
If the composer detects a conflict, it stops the update process and generates an error message. To resolve the conflict, you must manually update the conflicting module and rerun the Upgrader pipeline.

{% endinfo_block %}

Expand Down