pr-vcptcore-qa-02-04-2026-af3c

[vc-ci]

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

---

Note

Low Risk
Low risk config-only change, but it changes which VirtoCommerce.Catalog package is deployed (PR build -> released artifact), which could affect runtime behavior if versions differ.

Overview
Updates backend/packages.json to switch VirtoCommerce.Catalog in the AzureBlob source from a PR-specific package (3.1014.0-pr-875-18ba) to the released 3.1014.0 artifact.

Also includes minor JSON formatting/whitespace normalization (e.g., array bracket spacing and file newline).

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

[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 module blob name likely wrong from CI failure

High Severity

The VirtoCommerce.Catalog BlobName changed from a PR-specific build (VirtoCommerce.Catalog_3.1014.0-pr-875-18ba.zip) to a plain release name (VirtoCommerce.Catalog_3.1014.0.zip). The PR description explicitly shows "from PR undefined undefined", indicating the CI automation failed to resolve the source PR number and commit hash. Nearly every other module in the AzureBlob prerelease source uses a -pr-{number}-{hash} suffix. This blob likely does not exist in the vc3prerelease storage container, which would cause a deployment failure.