pr-vcptcore-qa-12-02-2026-52e5

[vc-ci]

ci: Automated update vc-module-catalog from PR undefined undefined

---

Note

Low Risk
Manifest-only change that alters which VirtoCommerce.Catalog build is pulled; low code risk but could affect deployments if the referenced package is missing or incompatible.

Overview
Updates backend/packages.json to source VirtoCommerce.Catalog version 3.1000.0 from the AzureBlob feed (via BlobName) instead of GithubReleases (previously Version: 3.914.0).

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

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

Catalog blob name missing prerelease PR suffix

High Severity

The VirtoCommerce.Catalog entry's BlobName is VirtoCommerce.Catalog_3.1000.0.zip, which lacks the -pr-NUMBER-HASH suffix that every other module in the AzureBlob source has. The PR description confirms the automation failed: "from PR undefined undefined" — the source PR metadata wasn't resolved. This blob likely doesn't exist in the vc3prerelease blob store, meaning the Catalog module will fail to install. Additionally, the module was removed from GithubReleases (where it was at version 3.914.0), so it has no valid source at all.

 

[vc-ci]

Closed by stale branch cleanup workflow