Update¶
New releases are published every two weeks on the GitHub repository releases page.
Note
It is strongly recommended to update with every release to reduce the risk of merge conflicts and integration issues.
Update from original repository (upstream)¶
To fetch and merge changes from the original repository into your current project:
-
Create a new branch for the update. Replace 1_18 from our example with the target version or tag you are syncing to:
-
Add the upstream remote. Replace the URL with the actual upstream repository:
-
Fetch upstream changes. This will download all branches and commits from upstream, without merging:
-
Merge changes from the dev branch of the upstream into your current branch:
Note
Resolve any merge conflicts if prompted.
-
(Optional) Remove the upstream remote if you don’t need to keep the upstream reference:
Note
Use git remote -v
to list current remotes.
If you plan to pull updates frequently, you can skip removing upstream.
Always test merged code before pushing to production.
Merge specific release from upstream (recommended)¶
If you need a specific version instead of a branch:
-
Select the desired release from https://github.com/VirtoCommerce/vc-frontend/releases
-
Add the upstream remote:
-
Fetch all tags:
-
Merge the specific release tag (e.g. 2.22.0):