pr-vcptcore-qa-07-04-2026-a66d

[vc-ci]

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

---

Note

Low Risk
Low risk manifest change that only alters which CatalogPublishing package artifact is pulled; main risk is deploying an unintended module version if the new blob name is incorrect.

Overview
Updates backend/packages.json to pull VirtoCommerce.CatalogPublishing from VirtoCommerce.CatalogPublishing_3.1002.0.zip instead of the previous PR build (3.1001.0-pr-72-48ca.zip).

Also applies minor JSON whitespace/formatting cleanup (including file ending newline change).

^{Reviewed by Cursor Bugbot for commit 2af9bd0. Bugbot is set up for automated code reviews on this repo. 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.}

^{Reviewed by Cursor Bugbot for commit 2af9bd0. Configure here.}

[cursor]

Release artifact referenced in pre-release blob container

Medium Severity

The CatalogPublishing BlobName changed from a PR build (_3.1001.0-pr-72-48ca.zip) to a release-style version (_3.1002.0.zip) within the vc3prerelease AzureBlob source. Every other module in this source uses a -pr- suffixed artifact. The PR description confirms the automation broke: "from PR undefined undefined" — the CI script failed to resolve the source PR, likely producing an incorrect artifact reference that may not exist in the pre-release container.

 

^{Reviewed by Cursor Bugbot for commit 2af9bd0. 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.}