pr-vcptcore-qa-07-04-2026-2b50

[vc-ci]

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

---

Note

Low Risk
Low risk: this only updates the module manifest entry for VirtoCommerce.Customer (and minor formatting), affecting which artifact is pulled at build/deploy time.

Overview
Updates backend/packages.json to pull VirtoCommerce.Customer from the Azure blob feed as VirtoCommerce.Customer_3.1004.0.zip (replacing the prior PR-specific artifact) and reorders the entry within the Modules list.

Also applies minor JSON formatting/whitespace cleanup and removes the trailing newline.

^{Reviewed by Cursor Bugbot for commit d4033b3. 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 d4033b3. Configure here.}

[cursor]

Automation failure likely produced incorrect Customer module blob reference

High Severity

The VirtoCommerce.Customer BlobName changed from a PR-specific prerelease build (3.1003.0-pr-295-0f8e) to VirtoCommerce.Customer_3.1004.0.zip, which lacks the -pr-NUMBER-HASH suffix used by nearly all other modules in this prerelease blob source. The PR description itself reads "from PR undefined undefined", confirming the automation failed to resolve the source PR metadata. This strongly suggests the generated blob name is incorrect and may reference a non-existent artifact in the vc3prerelease blob storage, which would cause a deployment failure.

 

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