pr-vcptcore-qa-23-02-2026-13a4

[vc-ci]

ci: Automated update vc-module-x-api from PR undefined undefined

---

Note

Low Risk
Manifest-only change that updates a single module artifact/version; risk is limited to potential runtime incompatibility if Xapi 3.1003.0 differs from the previously pinned PR build.

Overview
Updates the backend package manifest backend/packages.json to use VirtoCommerce.Xapi_3.1003.0.zip from the Azure blob source (replacing the previous PR-specific 3.1002.0-pr-63-f348 artifact and reordering the entry).

Also includes minor JSON formatting/whitespace cleanup in the GithubReleases source section (no functional module/version changes there).

^{Written by Cursor Bugbot for commit f45071f. This will update automatically on new commits. Configure here.}

[CLAassistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
_{You have signed the CLA already but the status is still pending? Let us recheck it.}

[cursor]

Cursor Bugbot has reviewed your changes and found 1 potential issue.

^{Bugbot Autofix is OFF. To automatically fix reported issues with Cloud Agents, enable Autofix in the Cursor dashboard.}

[cursor]

Module installation order violates dependency requirements

High Severity

The VirtoCommerce.XCatalog module is listed before VirtoCommerce.Xapi in the Modules array, but XCatalog depends on Xapi. Since the deployment workflow uses -SkipDependencySolving, modules are installed in the exact order they appear in this file without dependency resolution. This means XCatalog will be installed before its dependency Xapi, which could cause installation failures during deployment.