pr-vcptcore-qa-02-04-2026-0a3d

[vc-ci]

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

---

Note

Medium Risk
Updates the pinned VirtoCommerce.Customer package from a PR build to the 3.1003.0 release artifact, which can change runtime behavior of customer-related features. Remaining changes are formatting-only in backend/packages.json.

Overview
Switches the VirtoCommerce.Customer entry in backend/packages.json from a prerelease blob (3.1003.0-pr-295-0f8e) to the released VirtoCommerce.Customer_3.1003.0.zip artifact.

Also applies minor JSON formatting/whitespace cleanup (including ensuring module lists are consistently formatted).

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

Customer module blob name missing PR-specific suffix

High Severity

The BlobName for VirtoCommerce.Customer was changed from VirtoCommerce.Customer_3.1003.0-pr-295-0f8e.zip to VirtoCommerce.Customer_3.1003.0.zip, losing its -pr-{number}-{hash} suffix. Every other module in the AzureBlob prerelease source uses this suffix convention. The PR description confirms the CI automation failed to resolve the source PR details ("from PR undefined undefined"). This artifact likely doesn't exist on the prerelease blob storage at vc3prerelease.blob.core.windows.net, which would cause a deployment failure or result in loading the wrong module version.