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
7 changes: 7 additions & 0 deletions docs/scu/dev/how-the-spryker-code-upgrader-works.md
Original file line number Diff line number Diff line change
Expand Up @@ -42,6 +42,13 @@ 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.
VadymSachenko marked this conversation as resolved.
Show resolved Hide resolved

{% 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.
VadymSachenko marked this conversation as resolved.
Show resolved Hide resolved

{% endinfo_block %}

### 3. Creates a Git branch

The Upgrader tool creates a separate Git branch to commit the changes to. The branch name follows the pattern: `upgradebot/upgrade-for-{base-branch-name}-{last-commit-hash-in-the-base-branch}`.
Expand Down