pr-vcptcore-qa-24-02-2026-3a8a

[vc-ci]

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

---

Note

Low Risk
Only adjusts module package sourcing/version pinning in packages.json; risk is limited to potential runtime incompatibility if XCMS_3.1000.0.zip differs from the previously referenced release.

Overview
Updates backend/packages.json to source VirtoCommerce.XCMS from the AzureBlob feed (BlobName: VirtoCommerce.XCMS_3.1000.0.zip) instead of GithubReleases (removing the Version: 3.908.0 entry), and cleans up JSON formatting/newline.

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

XCMS blob name missing PR build identifier

High Severity

The VirtoCommerce.XCMS module's BlobName is VirtoCommerce.XCMS_3.1000.0.zip, which lacks the -pr-XX-XXXX suffix that every other module in the AzureBlob source has. The PR description confirms the automation failed: "from PR undefined undefined". This likely means the referenced blob artifact doesn't exist in the prerelease container, or the wrong (non-PR) build is being used, which could cause deployment failures or pull in an unintended version.