pr-vcptcore-qa-02-04-2026-74e0

[vc-ci]

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

---

Note

Low Risk
Low-risk manifest/config change, but it alters which VirtoCommerce.CatalogPublishing build is pulled (switching from a PR artifact to the released 3.1001.0 zip), which could change runtime behavior if the artifacts differ.

Overview
Updates backend/packages.json to use the released VirtoCommerce.CatalogPublishing_3.1001.0.zip artifact instead of the previous PR-specific package, keeping it sourced from AzureBlob.

Also includes minor JSON formatting/whitespace adjustments (e.g., array formatting and end-of-file newline).

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

Automation failure produced non-PR blob name for CatalogPublishing

High Severity

The BlobName for VirtoCommerce.CatalogPublishing was changed from a PR-specific build (VirtoCommerce.CatalogPublishing_3.1001.0-pr-72-48ca.zip) to a plain release build (VirtoCommerce.CatalogPublishing_3.1001.0.zip). The PR description explicitly states "from PR undefined undefined", indicating the automation script failed to resolve the source PR reference. Nearly all other modules in the AzureBlob source use PR-specific blob names with the -pr-XX-XXXX suffix. This release-style blob may not exist in the vc3prerelease blob storage, potentially causing a deployment failure, or it references an unintended build version for QA testing.