pr-vcptcore-qa-29-01-2026-d36c

[vc-ci]

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

---

Note

Medium Risk
Medium risk because it changes where VirtoCommerce.Xapi is sourced from (blob vs GitHub releases), which can alter deployed module bits and compatibility at runtime despite being a config-only change.

Overview
Updates backend/packages.json to pull VirtoCommerce.Xapi from the Azure Blob package source at version 3.1001.0 (zip), removing the prior 3.1000.0 GitHub releases module entry.

Also includes minor JSON formatting/whitespace adjustments and leaves the file without a trailing newline.

^{Written by Cursor Bugbot for commit 7c225ee. 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]

Blob name missing PR suffix suggests automation failure

Medium Severity

The BlobName for VirtoCommerce.Xapi is VirtoCommerce.Xapi_3.1001.0.zip, which lacks the -pr-XX-XXXX suffix present in all other AzureBlob entries. Combined with the PR description showing "from PR undefined undefined", this suggests the automation failed to capture source PR information. The blob artifact may not exist in the prerelease container, or the name may be incorrect, potentially causing module loading failures at deployment time.