pr-vcptcore-qa-24-02-2026-f3cb

[vc-ci]

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

---

Note

Low Risk
Only updates backend/packages.json module manifest entries; main risk is pulling the wrong XRecommend artifact/version at deploy time.

Overview
Moves VirtoCommerce.XRecommend to be sourced from the AzureBlob packages feed (pinning BlobName to VirtoCommerce.XRecommend_3.1000.0.zip) and removes the previous GithubReleases version pin (3.904.0).

Also includes minor JSON formatting/whitespace cleanup in backend/packages.json (no behavioral change beyond the module source/version update).

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

XRecommend blob name missing PR suffix from broken automation

High Severity

The VirtoCommerce.XRecommend module was moved from GithubReleases (version 3.904.0) to the AzureBlob prerelease source, but the BlobName (VirtoCommerce.XRecommend_3.1000.0.zip) lacks the -pr-{number}-{hash} suffix that every other AzureBlob entry has. The PR description confirms the automation malfunctioned: "from PR undefined undefined" — the PR number and hash resolved to undefined, so the expected suffix was never appended. This likely means the referenced blob doesn't exist in the prerelease storage, which would cause a deployment failure.