pr-vcptcore-qa-17-02-2026-51df

[vc-ci]

ci: Automated update vc-module-azureblob-assets from PR undefined undefined

---

Note

Low Risk
Only changes module sourcing/pinning in a manifest; low code risk but may affect deployment if the referenced blob package is missing or incompatible.

Overview
Updates backend/packages.json to source VirtoCommerce.AzureBlobAssets from the AzureBlob package feed (pinning it to VirtoCommerce.AzureBlobAssets_3.1000.0.zip) instead of pulling it from GithubReleases.

Also includes minor JSON formatting/whitespace cleanup (and removes the trailing newline).

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

Blob name missing prerelease suffix from automation failure

High Severity

The new VirtoCommerce.AzureBlobAssets entry uses BlobName VirtoCommerce.AzureBlobAssets_3.1000.0.zip, which lacks the -pr-NUMBER-HASH prerelease suffix that every other entry in the AzureBlob source has. The PR description containing "from PR undefined undefined" confirms the automation failed to resolve the PR metadata. This blob likely doesn't exist in the vc3prerelease container, which would cause a deployment failure, or it references the wrong artifact.