pr-vcptcore-qa-02-04-2026-1c55

[vc-ci]

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

---

Note

Medium Risk
Changes how VirtoCommerce.Contracts is resolved (moves it from GitHub releases to an AzureBlob package and bumps to 3.1001.0), which can affect build/deployment if the blob artifact is missing or incompatible.

Overview
Updates backend/packages.json to pull VirtoCommerce.Contracts from the AzureBlob source (VirtoCommerce.Contracts_3.1001.0.zip) instead of GithubReleases (removing the previous 3.1000.0 release entry).

Also includes minor JSON formatting/whitespace tweaks and ensures the manifest ends without an extra trailing newline.

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

Contracts blob name likely incorrect due to automation failure

High Severity

The PR description says "from PR undefined undefined", indicating the automation script failed to resolve the source PR details. The BlobName VirtoCommerce.Contracts_3.1001.0.zip is missing the -pr-{number}-{hash} suffix that nearly all other AzureBlob entries use. This strongly suggests the automation generated an incorrect artifact reference because it couldn't resolve the PR metadata. If the blob doesn't exist under this name in Azure storage, the Contracts module will fail to install during deployment.